DSPACE Catalog2015 E Web

www.dspace.
com
www.dspace.com
Catalog 2015
Company Headquarters
in Germany
United Kingdom
France
dSPACE GmbH
Rathenaustrae 26
33102 Paderborn
Tel.: +49 5251 1638-0
Fax: +49 5251 16198-0
info@dspace.de
dSPACE Ltd.
Unit B7 . Beech House
Melbourn Science Park
Melbourn
Hertfordshire . SG8 6HB
Tel.: +44 1763 269 020
Fax: +44 1763 269 021
info@dspace.co.uk
dSPACE SARL
7 Parc Burospace
Route de Gisy
91573 Bivres Cedex
Tel.: +33 169 355 060
Fax: +33 169 355 061
info@dspace.fr
China
Japan
USA and Canada
dSPACE Mechatronic Control

Technology (Shanghai) Co., Ltd.
Unit 1101-1105, 11F/L
Middle Xizang Rd. 18
Harbour Ring Plaza
200001 Shanghai
Tel.: +86 21 6391 7666
Fax: +86 21 6391 7445
infochina@dspace.com
dSPACE Japan K.K.

10F Gotenyama Trust Tower
4-7-35 Kitashinagawa
Shinagawa-ku
Tokyo 140-0001
Tel.: +81 3 5798 5460
Fax: +81 3 5798 5464
info@dspace.jp
dSPACE Inc.
50131 Pontiac Trail
Wixom . MI 48393-2020
Tel.: +1 248 295 4700
Fax: +1 248 295 2950
info@dspaceinc.com
Catalog 2015
01/2015
dSPACE GmbH Rathenaustrae 26 33102 Paderborn Germany info@dspace.de www.dspace.com
We Are Where You Are
Headquarters
Subsidiaries
Germany:
dSPACE GmbH, Paderborn
Project centers:
Stuttgart, Munich , Wolfsburg
USA:
France:
United Kingdom:
Japan:
China:
Distributors
dSPACE Inc., Detroit

dSPACE SARL, Paris
dSPACE Ltd., Cambridge
dSPACE Japan K.K.,
Tokyo, Nagoya,
Utsunomiya
dSPACE Mechatronic
Control Technology
(Shanghai) Co., Ltd.,
Shanghai
Australia:
Brazil:
Czech Republic
and Slovakia:
India:
Korea:
Netherlands:
Poland:
Sweden:
Sydney
So Paulo
Prague
Bengaluru
Seoul
Rotterdam
Krakow
Stockholm
Copyright 2015 by dSPACE GmbH.

All rights reserved. Written permission is required for reproduction of all or parts of this publication. The source must be stated in any such
reproduction. dSPACE is continually improving its products and reserves the right to alter the specifications of the products at any time without
notice. "AutomationDesk", "CalDesk", "ConfigurationDesk", "ControlDesk", "dSPACE", "Embedded Success dSPACE", "Green Success",
"MicroAutoBox","ProMINT", "SCALEXIO", "SYNECT", "SystemDesk", "TargetLink", and "VEOS" are trademarks or registered trademarks
of dSPACE GmbH in the United States of America or in other countries or both. Other brand names or product names are trademarks or registered trademarks of their respective companies or organizations.
Please note: To ensure that your application scenario is optimally supported by a specific dSPACE product or product combination,
please contact dSPACE for the latest information on product versions, compatibilities, and suitable use scenarios.
Introduction
Contents
Contents
Introduction
dSPACE Systems ___________________________________________________ 10
Application Fields
Application Fields
Product Overview __________________________________________________ 14
20
Automotive Industry ________________________________________________ 22

Aerospace Industry _________________________________________________ 26
Commercial & Off-Highway Vehicles __________________________________ 28
Electric Drives _____________________________________________________ 30
Medical Engineering ________________________________________________ 32
Research and Education _____________________________________________ 34
Other Fields _______________________________________________________ 36
38
Software
Software
System Architecture Software ________________________________________ 40

SystemDesk _______________________________________________ 40
Implementation Software ___________________________________________ 48

Real-Time Interface (RTI) ______________________________________ 54
Real-Time Interface for Multiprocessor Systems (RTI-MP) ___________ 60
Real-Time Interface Bypass Blockset ____________________________ 62
Real-Time Interface CAN Blockset ______________________________ 68
Real-Time Interface CAN MultiMessage Blockset _________________ 70
Real-Time Interface LIN MultiMessage Blockset ___________________ 73
dSPACE FlexRay Configuration Package _________________________ 76
Hardware
ConfigurationDesk __________________________________________ 48
RTI FPGA Programming Blockset _______________________________ 86
Ethernet Blocksets ___________________________________________ 88
ADASIS v2 Horizon Reconstructor Blockset ______________________ 92
XSG Utils Library ____________________________________________ 94
XSG AC Motor Control Library ________________________________ 96
NEW: Power RealTime Library _________________________________ 97
Engineering
NEW: RTI AUTOSAR Blockset __________________________________ 82
Compilers __________________________________________________ 98
Simulation Software _______________________________________________ 100
VEOS ___________________________________________________ 100
Experiment and Visualization Software _______________________________ 106

ControlDesk Next Generation _______________________________ 106
Test Automation Software __________________________________________ 156

AutomationDesk ___________________________________________ 156
Real-Time Testing __________________________________________ 170
Platform API Package _______________________________________ 176
Failure Simulation API Package _______________________________ 178
2015
Support and Maintenance
MotionDesk _______________________________________________ 140
Contents
Software
Production Code Generation Software _______________________________ 180
TargetLink ________________________________________________ 180

TargetLink Data Dictionary ___________________________________ 213
TargetLink Partner Program __________________________________ 220
Model Compare1) ___________________________________________ 222
ECU Interface Software ____________________________________________ 226

ECU Interface Manager______________________________________ 226
dSPACE Calibration and Bypassing Service ______________________ 230
dSPACE Internal Bypassing Service ____________________________ 231
dSPACE XCP Service ________________________________________ 232
Variable Editor _____________________________________________ 233
dSPACE ECU Flash Programming Tool __________________________ 235
Automotive Simulation Models (ASM) ________________________________ 236

Combustion Engine Simulation _______________________________ 240
ASM Gasoline Engine Basic ___________________________ 241
ASM Diesel/Gasoline Engine ___________________________ 242
ASM Diesel/Gasoline Engine In-Cylinder _________________ 243
ASM Turbocharger ___________________________________ 244

ASM Diesel Exhaust System ___________________________ 245
Electric Components Simulation ______________________________ 246
ASM Electric Components ____________________________ 247
XSG Electric Components ____________________________ 249
Vehicle Dynamics Simulation _________________________________ 250
ASM Vehicle Dynamics _______________________________ 251
ASM Truck _________________________________________ 253

ASM Trailer _________________________________________ 254
ASM Pneumatics ____________________________________ 256

ASM Brake Hydraulics ________________________________ 256
Traffic Simulation ___________________________________________ 257
ASM Traffic _________________________________________ 258

ModelDesk ________________________________________________ 261

ASM Versions and License Concept ___________________________ 269
Data Management Software ________________________________________ 270

SYNECT Test Management ____________________________ 272
SYNECT Signal & Parameter Management _______________ 277
SYNECT Model Management __________________________ 280
SYNECT Variant Management _________________________ 284
General SYNECT Functionalities ________________________ 287
2015
SYNECT _________________________________________________ 270
Variant-Based Workflow Management _________________________ 290
Limited availability outside of Europe and Asia, please contact dSPACE.
1)
Introduction
Contents
Hardware
294
SCALEXIO Hardware Introduction _____________________________ 296
SCALEXIO Processing Unit ___________________________________ 304
DS2680 I/O Unit ___________________________________________ 306
DS2690 Digital I/O Board ____________________________________ 309
DS2655 FPGA Base Board ___________________________________ 311
NEW: DS6101 Multi-I/O Board ________________________________ 314
NEW: DS6201 Digital I/O Board_______________________________ 316
DS2601 Signal Measurement Board ___________________________ 318
DS2621 Signal Generation Board _____________________________ 320
DS2642 FIU & Power Switch Board ____________________________ 322
DS2671 Bus Board _________________________________________ 324
DS2907 Battery Simulation Controller__________________________ 326
Additional Solutions ________________________________________ 327
Software
Application Fields
SCALEXIO Hardware ______________________________________________ 296
Single-Board Hardware ____________________________________________ 332

Single-Board Hardware Introduction ___________________________ 332
DS1103 PPC Controller Board ________________________________ 334
DS1104 R&D Controller Board ________________________________ 340
Connector and LED Panels ___________________________________ 346
Demo Equipment __________________________________________ 347
I/O Boards Overview ________________________________________ 350
DS1005 PPC Board _________________________________________ 352
DS1006 Processor Board ____________________________________ 356
NEW: DS1007 PPC Processor Board ___________________________ 362
DS2002/DS2003 A/D Boards _________________________________ 366
DS2004 High-Speed A/D Board _______________________________ 372
DS2101/DS2102/DS2103 D/A Boards __________________________ 375
DS2202 HIL I/O Board _______________________________________ 382
DS2211 HIL I/O Board _______________________________________ 386
DS2302 Direct Digital Synthesis Board _________________________ 392
DS2401 Resistive Sensor Simulation Board ______________________ 398
DS3001/DS3002 Incremental Encoder Interface Board ____________ 400
DS4002 Timing and Digital I/O Board __________________________ 404
DS4003 Digital I/O Board ____________________________________ 409
DS4004 HIL Digital I/O Board _________________________________ 410
DS4121 ECU Interface Board _________________________________ 412
DS4201 Prototyping Board ___________________________________ 416
DS4201-S Serial Interface Board ______________________________ 417
DS4302 CAN Interface Board ________________________________ 418
DS4330 LIN Interface Board __________________________________ 421
DS4505 Interface Board (FlexRay, NEW: CAN FD) ________________ 424
Engineering
Modular Hardware Introduction ______________________________ 348
2015
Hardware
Modular Hardware ________________________________________________ 348
Contents
Hardware

DS5001 Digital Waveform Capture Board ______________________ 428
DS5101 Digital Waveform Output Board _______________________ 432
DS5203 FPGA Board ________________________________________ 438
SCRAMNet+ Interface _______________________________________ 442
PROFIBUS Interface _________________________________________ 444
Interface to MIL-STD-1553 ___________________________________ 446
ARINC 429 Interface ________________________________________ 448
ARINC 717 Interface ________________________________________ 450
FPGA Base Board ___________________________________________ 452
PWM Measurement Solution _________________________________ 454
Position Sensor Simulation Solution ___________________________ 456

AC Motor Control Solution __________________________________ 460
EMH Solution ______________________________________________ 464
EtherCAT Slave Interface ____________________________________ 470
100 Mbit/s Ethernet Interface (UDP/IP, TCP/IP) ___________________ 472
Additional I/O Solutions _____________________________________ 474
Accessories ______________________________________________________ 480

Connector and LED Panels ___________________________________ 480
PX4/PX10/PX20 Expansion Boxes for Modular Hardware __________ 484
AutoBox/Tandem-AutoBox ___________________________________ 488

Link Boards ________________________________________________ 492
DS830 MultiLink Panel ______________________________________ 494
Simulator Hardware _______________________________________________ 496

dSPACE Simulator Mid-Size __________________________________ 496
dSPACE Simulator Full-Size ___________________________________ 500
Simulator Extensions ________________________________________ 505
NEW: MicroLabBox Hardware _______________________________________ 516

MicroLabBox ______________________________________________ 516
MicroAutoBox Hardware __________________________________________ 522

MicroAutoBox II ____________________________________________ 522
MicroAutoBox Break-Out Box ________________________________ 540
RapidPro Hardware ________________________________________________ 542

RapidPro Hardware Introduction ______________________________ 542
RapidPro SC Unit ___________________________________________ 551
RapidPro Power Unit ________________________________________ 553
RapidPro Control Unit with MPC565 __________________________ 556
RapidPro SC/PS Modules ____________________________________ 559
RapidPro Break-Out Boxes ___________________________________ 564
ECU Interface Hardware ___________________________________________ 566
USB to CAN Converter DCI-CAN1 ____________________________ 566
USB to K-Line Interface DCI-Kline1 ____________________________ 568
Generic Serial Interfaces _____________________________________ 570
Additional Bypass Interface Solutions __________________________ 576
2015
Introduction
Contents
Engineering 578
dSPACE Engineering Services _______________________________________ 580
586
Application Fields
Support: An Integral Part of the Product ______________________________ 588
589
Important Information on Third-Party Brand Names

and Product Names
589
Index
590
Engineering
Hardware
Safe Use of dSPACE Products
Software
Software Maintenance Service (SMS) _________________________________ 588
2015
Introduction
dSPACE Systems _______________________ 10
Product Overview ______________________ 14
Introduction / dSPACE Systems
dSPACE Systems
Solutions for embedded software development in automotive, aerospace, and industrial control
Highlights
n dSPACE products help you manage the complexity
of todays embedded software engineering
n High software quality, accelerated processes, high
productivity
n Mature and reliable tools based on leading-edge
technology and 25+ years of experience
n Dedicated support and engineering services available
worldwide
Embedded Control Development

with dSPACE Tools
dSPACE offers you a complete and integrated development environment for embedded control software and
systems. Our tools and systems are convenient to use
and will save you valuable development time and money,
whether you apply them throughout the entire process
or just in individual project phases. dSPACE systems support established development processes, particularly for
embedded control unit development, also with respect
to functional safety requirements, and give you ways to
adapt your process chains to new challenging needs. With
constant innovations, key technologies and standards,
and dedicated service and support, dSPACE helps you
achieve long-term success and put your visions into action. Together with the MATLAB/Simulink/Stateflow
products from MathWorks, a single, highly integrated
tool chain for model-based development is available.
dSPACE systems let you perform demanding tasks.
10
These include, for example:

n System and software architecture design
n Rapid control prototyping of new, innovative functions
n Automatic production code generation optimized for
many different embedded targets
n Hardware-in-the-loop (HIL) testing of single and
networked embedded control units
n Virtual validation of functions and embedded software
with PC-based simulation, and
n Data management for handling the ever increasing
number of models, data, tests, dependencies etc.,
whether in small or large teams and departments.
The result: dSPACE systems help you create high-quality
embedded systems and products, and support you meeting your target dates. Our systems give you the competitive
edge you need to keep pace with strong market demands.
2015
Introduction
dSPACE Product Areas

System Architecture
SystemDesk VECU Generation Module (p. 46)

TargetLink (p. 180)
n VEOS (p. 100)
n
Software
Relevant products:
n SystemDesk (p. 40)
n SystemDesk Modeling Module (p. 43)
n SystemDesk RTE Generation Module (p. 41)
Application Fields
SystemDesk simplifies and speeds up the planning, implementation,

and integration of complex systems and software architectures. Working
with formal descriptions of the software architecture helps you handle
production projects and improves OEM/supplier processes. SystemDesk
supports the AUTOSAR standard and can generate the AUTOSAR
Runtime Environment (RTE). Easy roundtrip engineering with the
production code generator TargetLink helps get software designs into
production. You can also use SystemDesk to generate virtual ECUs,
including components of the application and basic software. VEOS
combined with SystemDesk can be used to verify the system behavior
and function interplay in an early PCbased simulation.
Rapid Control Prototyping
Implementation Software (p. 48)

ControlDesk Next Generation (p. 106)
n TargetLink (p. 180)
n ECU Interface Software (p. 226)
Engineering
n
n
2015
11
Relevant products and product groups:

n SingleBoard Hardware (p. 332)
n Modular Hardware (p. 348)
n NEW: MicroLabBox (p. 516)
n MicroAutoBox (p. 522)
n RapidPro Hardware (p. 542)
n ECU Interface Hardware (p. 566)
Hardware
dSPACE prototyping systems are flexible development platforms that

let you develop and optimize your control designs without manual
programming.
With comprehensive and reliable software support, including firstrate
MATLAB/Simulink integration, all our systems are readytouse and
easytorun. Design faults are found immediately and corrections can
be carried out on the spot. The product offering is completed by a full
range of signal conditioning and power stage modules to connect the
prototyping system to sensors and actuators.
ECU Autocoding
Automatic code generation for the production ECU is a key development
phase. The production code generator TargetLink generates highly efficient
C code straight from MATLAB/Simulink/Stateflow and allows early verifi
cation through built-in simulation and testing. This drastically reduces the
time needed for implementation, and results in systematic consistency
between your specification and your production code. Changes on the model
level are quickly transferred to code. TargetLink has been certified for use in
developing safety-related systems according to ISO 26262, IEC 61508, and
derivative standards, and offers comprehensive support for the AUTOSAR
standard. The data management software SYNECT provides support for
centrally managing models, ECU signals and parameters as well as MIL/SIL/
PIL tests and test data for all the different variants of your ECU software.
Relevant products:
n Third-Party Tools for TargetLink (p. 220)
n Model Compare1) (p. 222)
n VEOS (p. 100)

n SYNECT (p. 270)
HIL Testing
When your ECU has been programmed, you can test its functions quickly
and automatically by using dSPACE simulation systems. They replace the
real environment, and you can execute your tests in any conceivable test
scenario, systematically and reproducibly thanks to comprehensive test
automation. dSPACE products cover the whole range from early function
testing to large-scale ECU network tests. The comprehensive software
support includes proven-in-practice Automotive Simulation Models
and convenient test automation support for increased productivity in
test development and test execution. The data management software
SYNECT is ideal for centrally managing tests, test results, signals,
parameters, models, and variants.
Relevant products and product groups:

n SCALEXIO Hardware (p. 296)
n Simulator Hardware (p. 496)
n Modular Hardware (p. 348)
n Test and Experiment Software (p. 106)
n Automotive Simulation Models (p. 236)

n Implementation Software (p. 48)
n VEOS (p. 100)
n SYNECT (p. 270)
1)
12
Limited availability outside of Europe and Asia.
2015
Introduction
Virtual Validation

AutomationDesk (p. 156)
n Automotive Simulation Models (p. 236)
n
n
Software
Relevant products:
n VEOS (p. 100)
Application Fields
Virtual validation lets you shift verification and validation tasks to early
development stages. A wide range of use cases is opened up by running
models of controllers and ECUs, and parts of a vehicle, such as the
engine, sensors and actuators, on a PC. VEOS is the dSPACE platform
for PCbased simulation. You can simulate and test ECU functions and
software before a real ECU prototype is available. VEOS even helps
to prepare simulation models and test libraries on a development PC
and reuse them on a hardwareintheloop system. VEOS is integrated
in the dSPACE tool chain working together with the established
dSPACE tools for system architecture, rapid control prototyping, ECU
autocoding, and hardwareintheloop simulation.
Data Management
Hardware
While electronics and software continue to advance, the amount of data

that is produced especially in modelbased development is immense.
Managing this data is a growing challenge. The solution is dSPACE
SYNECT, a data management software with a special focus on model
based development and ECU testing. SYNECT helps engineers handle
models, signals, parameters, tests, test results, etc., their dependencies,
versions and variants, and the underlying requirements throughout the
entire development process. This gives you consistent data versions,
complete traceability, and reliable and efficient reuse of data in other
projects, by other users, or for new vehicle and ECU variants. SYNECT
closely integrates with engineering tools such as AutomationDesk,
TargetLink, and MATLAB/Simulink, and supports relevant standards.
Engineering
dSPACE systems are easy to get up and running. However, if a project
is more complex, if individual solutions are needed or if there is high
time pressure, customers can rely on dSPACEs fast and competent
engineering and consulting services. Our experienced engineers support
customers with smallscale project aid as well as with complete turnkey
solutions if required also with resident dSPACE engineers onsite.
Relevant products:
n dSPACE Engineering Services (p. 580)
2015
13
Engineering
Relevant product:
n SYNECT (p. 270)
Product Overview
Product Overview
Offtheshelf components for every development phase
System Architecture
Software
Implementation Software
SystemDesk
Modeling system architecture and
generating virtual ECUs
page 40
ConfigurationDesk
Configuration and implementation
software for dSPACE SCALEXIO
hardware
page 48
n
n
SystemDesk RTE Generation

Module
page 41
SystemDesk Modeling Module
page 43
SystemDesk V-ECU Generation
Module
page 46
Real-Time Interface (RTI)

Implementation software for running
models on dSPACE hardware
page 54
RTI for Multiprocessor Systems
For graphical setup of multiprocessor
structures
page 60
RTI Bypass Blockset
ECU interfacing for rapid control prototyping and intrusive testing of existing
ECU software
page 62
RTI CAN Blockset
For combining dSPACE systems with
CAN communication networks
page 68
RTI CAN MultiMessage Blockset
CAN communication networks
page 70
RTI LIN MultiMessage Blockset
LIN communication networks
page 73
dSPACE FlexRay Configuration
Package
Configuring dSPACE systems in
FlexRay networks
page 76
Simulation Software
RTI FPGA Programming Blockset

Integrating FPGA models in dSPACE
systems
page 86
VEOS
Platform for PC-based simulation
page 100
Ethernet Blocksets
Connection of dSPACE real-time systems
to Ethernet networks and devices
page 88
ADASIS v2 Horizon Reconstructor
Blockset
Developing and testing map-based
driver assistance systems using the
ADASIS v2 protocol
page 92
XSG Utils Library
Ready-to-use function blocks for faster
implementation of FPGA models
page 94
XSG AC Motor Control Library
FPGA-based control design for
MicroAutoBox II, SCALEXIO and PHSbased systems
page 96
NEW: Power RealTime Library
Easy real-time simulation of power
electronics circuits developed with
SimPowerSystems
page 97
Compilers
For translating C code into object code
page 98
NEW: RTI AUTOSAR Blockset

MATLAB/Simulink- and AUTOSARbased co-development, validation and
prototyping on MicroAutoBox II
page 82
14
2015
Introduction
Product Overview
Test Automation
Software
Production Code
Generation Software
ECU Interface Software
ControlDesk Next Generation

Universal experiment software for electronic control unit (ECU) development
page 106
AutomationDesk
Powerful test authoring and automation
tool (certified for IEC 61508 and ISO
26262)
page 156
TargetLink
Automatic production code generator
(certified for IEC 61508 and ISO 26262)
page 180
ECU Interface Manager

Bypassing without ECU source code
modifications
page 226
Third-Party Tools for TargetLink

Complementary products for a modelbased development process and tool
chain built around TargetLink
page 220
dSPACE Calibration and

Bypassing Service
ECU service for measurement, calibration, bypassing, and ECU flash programming
page 230
Real-Time Testing
Python-based real-time test automation
page 170
Platform API Package
Application programming interfaces for
connecting to dSPACE platforms
page 176
Failure Simulation API Package
Application programming interfaces for
accessing failure insertion units
page 178
Model Compare1)
Comparison of Simulink, Stateflow,
and TargetLink models
page 222
dSPACE Internal Bypassing Service

Using an existing ECU for function
development
page 231
dSPACE XCP Service
ECU service for measurement, calibration, bypassing, and ECU flash programming via XCP
page 232
Hardware
MotionDesk
3-D online animation of simulated
mechanical systems in real time
page 140
Software
Application Fields
Experiment and
Visualization Software
1)
2015
15
dSPACE ECU Flash Programming

Tool
ECU flash programming via measurement and calibration interfaces
page 235
Engineering
Variable Editor
Visualize, edit, and create ECU description files
page 233
Product Overview
Automotive Simulation
Models
Data Management
Software
SCALEXIO Hardware
Combustion Engine Simulation

Real-time models for diesel and gasoline
engine simulation
n ASM Gasoline Engine Basic
page 241
n ASM Diesel/Gasoline Engine
page 242
n ASM Diesel/Gasoline Engine
In-Cylinder
page 243
n ASM Turbocharger
page 244
n ASM Diesel Exhaust System
page 245
SYNECT
Data management software for modelbased development and ECU testing
page 270
SCALEXIO Processing Unit

x86 processor technology Intel XEON E3
page 304
Electric Components Simulation

Real-time models for vehicle electrics
and traction system simulation
n ASM Electric Components
page 247
n XSG Electric Component
page 249
n
n
n
n
n
SYNECT Test Management

page 272
SYNECT Signal & Parameter
Management
page 277
SYNECT Model Management
page 280
SYNECT Variant Management
page 284
General SYNECT Functionalities
page 287
Variant-Based Workflow
Management
Handling complex workflows including
variants
page 290
I/O
MultiCompact unit for powertrain
and vehicle dynamics scenarios
DS2680, page 306
AFDX1)
NEW: Interface Solution for AFDX
page 329
PROFIBUS and EtherCAT
Interface Solution for PROFIBUS and
EtherCAT
(SCALEXIO Field Bus Solution)
page 330
Multi-I/O
I/O hardware with signal conditioning
for automotive systems
NEW: DS6101, page 314
Traffic Simulation
Real-time models for traffic and environment simulation
n ASM Traffic
page 258
FIU & Power Switch

HighFlex board for power-switching
with Failure Insertion Unit
DS2642, page 322
2015
MIL-STD-1553
Interface Solution for MIL-STD-1553
page 328
FPGA
HighFlex board with user-programmable
FPGA
DS2655, page 311
Digital I/O
SCALEXIO I/O board with 96 bidirectional digital I/O channels
16
ARINC 429
Interface Solution for ARINC 429
page 327
Digital I/O
MultiCompact board for vehicle body
scenarios
DS2690, page 309
Vehicle Dynamics Simulation

Real-time models for ground vehicle
simulation
n ASM Vehicle Dynamics
page 251
n ASM Truck
page 253
n ASM Trailer
page 254
n ASM Pneumatics
page 256
n ASM Brake Hydraulics
page 256
ModelDesk
Graphical user interface for Automotive
Simulation Models (ASM)
page 261
Battery Simulation Controller

Power supply control for battery
simulation
DS2907, page 326
PSI5 Master/Slave Solution

page 331
Signal Measurement
HighFlex board for measuring ECU
output signals
DS2601, page 318
Signal Generation
HighFlex I/O board for simulating ECU
input signals
DS2621, page 320
Bus Interfaces
HighFlex board for interfacing to
different bus systems
DS2671, page 324
1)
AFDX is a registered trademark of Airbus
Introduction
Product Overview
Modular Hardware
Processor Boards
Modular Hardware I/O Boards (1)
PowerPC and I/O

PPC750GX, 20 x A/D, 8 x D/A,
digital I/O, CAN interface,
and more
DS1103, page 334
PowerPC
PPC750GX, 1 GHz
DS1005, page 352
Multi-Channel A/D
32 x 16 bit, MUX, 2 independent ADCs
DS2002, page 366
X86 Processor Technology

Quad-Core AMD OpteronTM
processor, 2.8 GHz
DS1006, page 356
Multi-Channel A/D
32 x 16 bit, MUX, 2 independent ADCs
DS2003, page 366
D/A
5 x 12 bit
DS2101, page 375
High-Resolution D/A
6 x 16 bit
DS2102, page 375
Multi-Channel D/A
32 x 14 bit
DS2103, page 375
HIL I/O
16 x 14 bit (A/D), 20 x 12 bit (D/A),
signal conditioning
DS2202, page 382
HIL I/O
16 x 14 bit (A/D), 20 x 12 bit (D/A),
sensor signal generation, anglesynchronous signals, and more
DS2211, page 386
Direct Digital Synthesis
6 x VC33 DSP and 16-bit DACs,
36 digital I/O
DS2302, page 392
Timing and Digital I/O

8 timing channels, 200 ns resolution,
32 dig. I/O
DS4002, page 404
Digital I/O
96 x dig. I/O
DS4003, page 409
Digital I/O
96 x dig. I/O with general signal conditioning up to 60 V
DS4004, page 410
Hardware
Demo Equipment
Hardware and software for demonstrating single-board hardware
page 347
High-Speed A/D
16 x 16 bit, 16 independent ADCs,
800 ns conversion time,
4 external trigger inputs
DS2004, page 372
ECU Interface
Interface to electronic control units
DS4121, page 412
Prototyping Board
Integration of customized circuits
DS4201, page 416
Serial Interface
4 channels for serial communication
DS4201-S, page 417
CAN Interface
Interface to CAN bus
DS4302, page 418
Engineering
Panels
Connector and LED panels
page 346
Dual-Core Real-Time Processor

Freescale QorlQ P5020, dual-core, 2 GHz
Incremental Encoder Interfaces

5 or 6 channels,
digital or sinusoidal signals
DS3001/2, page 400
LIN Interface
Interface to LIN bus
DS4330, page 421
FlexRay and CAN FD Interface
Interface to FlexRay or (NEW) CAN FD
DS4505, page 424
2015
17
PowerPC and I/O

PowerPC 603e, 8 x A/D, 8 x D/A,
digital I/O, and more
DS1104, page 340
Resistive Sensor Simulation

4 resistance output channels
(10 - 500 k)
DS2401, page 398
Software
Application Fields
Single-Board Hardware
Product Overview
Modular Hardware I/O Boards (2)
Digital Waveform Capture

16 channels, 25 ns resolution
DS5001, page 428
Digital Waveform Output
16 channels, 25 ns resolution
DS5101, page 432
FPGA Board
FPGA programmable per
application
DS5203, page 438
SCRAMNet+ Interface
Interface to SCRAMNet+ networks
page 442
PROFIBUS Interface
Interface to a PROFIBUS
communication bus
page 444
MIL-STD-1553
Interface to MIL-STD-1553 networks
page 446
Position Sensor Simulation

Solution
Simulation of position sensors
page 456
AC Motor Control Solution
Control of diverse AC motors
page 460
EMH Solution
Electric motor simulation
page 464
EtherCAT Slave Interface
Slave interface to an EtherCAT
communication bus
page 470
Ethernet Interface (100 Mbit/s)
Interface to an Ethernet network
page 472
Additional I/O Solutions
I/O to your specifications
page 474
Accessories
Simulator Hardware
Panels
Connector and LED panels
page 480
dSPACE Simulator Mid-Size

System for ECU/controller testing
page 496
Expansion Boxes
Space for 3, 9 or 19 dSPACE boards
PX4, PX10, PX20
page 484
dSPACE Simulator Full-Size

System for ECU/controller testing
page 500
AutoBox/Tandem-AutoBox
For in-vehicle experiments,
space for 3 or 13 dSPACE boards
page 488
Simulator Extensions
Power switch, CAN gateway, bus FIU,
electronic load modules, custom
adaptation, break-out boxes
page 505
Link Boards
Connecting a host PC with
dSPACE systems
page 492
MultiLink Panel
Connection of several systems
to one host PC
DS830, page 494
ARINC 429 Interface

Interface to the ARINC 429 avionics
data bus
page 448
ARINC 717 Interface
Interface to the ARINC 717 avionics
data bus
page 450
FPGA Base Board
For high-resolution signal
preprocessing
page 452
PWM Measurement Solution
High-precision digital capturing of
3-phase PWM signals
page 454
18
2015
Introduction
Product Overview
MicroAutoBox Hardware
RapidPro Hardware
ECU Interface Hardware
NEW: MicroLabBox
Compact prototyping unit for the
laboratory
page 516
MicroAutoBox II
2nd generation of dSPACEs robust
and compact stand-alone prototyping
unit
page 522
RapidPro SC Unit
Flexible signal
conditioning unit
page 551
DCI-CAN1
Robust and compact USB-to-CAN
gateway
page 566
RapidPro Power Unit

Flexible power stage unit
page 553
DCI-KLine1
Robust and compact USB-to-K-Line
interface
page 568
RapidPro Control Unit with

MPC565
Intelligent I/O subsystem for dSPACE
prototyping systems
page 556
RapidPro SC/PS Modules
Signal conditioning and power stage
modules for RapidPro units
page 559
Additional Bypass Interface

Solutions
Customer-specific DPMEM PODs and
on-chip debugging interfaces
page 576
2015
19
Engineering
RapidPro Break-Out Boxes

Desktop connection panels for
RapidPro systems
page 564
Generic Serial Interfaces

Function bypassing, measurement, ECU
calibration and flash programming
page 570
Hardware
MicroAutoBox Break-Out Box

Desktop connection panel for
MicroAutoBox II
page 540
Software
Application Fields
NEW: MicroLabBox
Hardware
Application Fields
Automotive Industry ___________________ 22
Aerospace Industry ____________________ 26
Commercial & Off-Highway Vehicles _______ 28
Electric Drives ________________________ 30
Medical Engineering ___________________ 32
Research and Education _________________ 34
Other Fields __________________________ 36
Application Fields / Automotive Industry
Automotive Industry
The challenge of ECU development
22
Well-Proven, Integrated Development Systems

In todays fast moving, competitive automobile electronics
world, efficiency, productivity and innovation are key.
Product life cycles are getting shorter. Higher expectations
regarding safety, comfort, and environmental compatibility are rapidly pushing up the complexity of electronic
systems. Many automotive manufacturers and suppliers
have realized that well-proven, integrated development
systems which support industry standards, and a modern
model-based development process can improve hand-off
between the development phases and shorten them. By
this means, enormous manual workloads can be reduced
and expensive mistakes avoided. As an independent system
partner, dSPACE has done pioneering work on tools for

electronic control unit (ECU) development, and cooperates
closely with the automotive industry. dSPACE supports all
the development phases with its products, from architecture-based system design and block-diagram-based function prototyping to ECU autocoding, virtual validation, and
HIL testing, and also offers powerful data management
software. The advantages for automotive customers: considerable savings in time and cost, greatly enhanced software quality, and more efficient cooperation between
manufacturer and supplier.
A Diversity of Application Fields

dSPACE systems are being used successfully at international automotive customers for developing and testing
embedded electronics in fields such as engine control,
powertrain control (including hybrid drive technologies and
electric drives), vehicle dynamics (e.g., ESP, damping control),
driver assistance systems (e.g., adaptive cruise control, automatic emergency braking, and lane departure warning),
autonomous driving, comfort electronics, interior systems,

infotainment, noise cancelation, ECU diagnostics, etc. Our
customers use controllers developed with dSPACE tools in
vehicles such as passenger cars, motorbikes, racing cars,
and commercial vehicles (p. 28) like trucks, buses, and offhighway vehicles.
2015
Introduction
Application Examples1) (1)

Examples
Application
Details
Hybrid Drive (I)
n HIL simulation for a hybridized
n High complexity of networked electronic systems

n dSPACE Simulators for functionality verification and quality assurance
n Automotive Simulation Models (ASM) for simulating the electric
powertrain
Hybrid Drive (II)
n Rapid control prototyping and
production code generation for a

hybrid SUV
Drivetrain ECUs/
AUTOSAR
n AUTOSAR-compliant production
software
Application Fields
components
n Hybrid demo vehicle with dSPACE prototyping system
n MicroAutoBox and RapidPro control hybrid components
n TargetLink for production code generation
n Engine ECUs supporting functions for combustion engines, hybrid
controllers, and transmission applications

n AUTOSAR tool chain using SystemDesk and Targetlink
Electric Vehicle
n Developing a new electric vehicle
n Ensuring the quality of the control software using dSPACE Simulator
for rigorous testing, while cutting the time-to-market

n Test automation with AutomationDesk
n Testing Li-ion battery
Battery
Management
System (II)
n Developing an efficient battery
Active Seat Belts
n Pre-pretensioner for seat belts
management systems
Simulator
n Optimizing the steering feel
n Battery ECU: focus on electric and thermal protection

n TargetLink used to generate the ECU software
n Controllers use AUTOSAR-compliant software

n Seat belt tightened electrically
n SystemDesk and TargetLink used
n dSPACE Simulator to analyze the system behavior of steering systems
n Automotive Simulation Models (ASM) to simulate the vehicle and
Hardware
management system for a hybrid

vehicle
for optimizing belt impact
Steering Systems
n BMS requirements according to ISO 26262

n Precise simulation of Li-Ion battery cells in real-time with dSPACE
Software
Battery
Management
System (I)
the road
n ModelDesk to create individual road sections with special surface
1)
Short selection of examples. Numerous application examples from customers, including detailed descriptions and pictures,
can be found on www.dspace.com and in the printed issues of dSPACE Magazine (formerly dSPACE NEWS).
2015
23
Engineering
characteristics
Application Examples1) (2)

Examples
Application
Details
Video-based Driver
Assistance Systems
n Developing and testing lane
n Communication between dSPACE platforms and EB Assist ADTF via
Smart Adaptive
Cruise Control
departure warning systems,

emergency steer and brake
assistants that use video data
and sensor fusion
n Developing predictive control
strategies in a simulation
environment for Adaptive Cruise
Control (ACC)
ADTF Message Bus (UDP/IP) and dSPACE ADTF Blockset

n Validation of camera-based applications in a virtual traffic
environment using ASM, ModelDesk, and MotionDesk in connection

with VEOS and dSPACE HIL simulators
n ASM for 3-D traffic simulation with MATLAB/Simulink
n ModelDesk for creating 3-D roads and traffic scenarios, and
MotionDesk for visualizing driving maneuvers

n Interface to the electronic horizon via ADASIS v2 Horizon
Reconstructor Blockset
AUTOSAR Software
Development
n Developing AUTOSAR software
by using the dSPACE tool chain
n TargetLink for generating the production code for AUTOSAR software
components
n SystemDesk for generating virtual ECUs
n VEOS for validating virtual ECUs
Window Control
n Developing new power window
control algorithms
Lighting
n Developing automatic vertical
aim control systems and

advanced frontlighting systems
Motorcycle
Development/
On-Target
Prototyping
n Developing and testing vehicle
dynamics controllers on
motorcycles
n Goal: maximum protection against power window injuries

n dSPACE prototyping system and TargetLink used
n Functional tests of ECU and stepper motors via HIL simulation with
dSPACE real-time hardware

n Rapid control prototyping for vehicle dynamics functions on
production ECUs
n On-target prototyping based on the dSPACE ECU Interface Manager
and the RTI Bypass Blockset

n Reduced verification effort and a shorter verification phase
24
1)
2015
Introduction
Standards
Standard
dSPACE Products Supporting the Standard
ADASIS
n www.ertico.com/
n ADASIS v2 Horizon Reconstructor Blockset (p. 92)
AUTOSAR
n www.autosar.org

n VEOS (p. 100)
n NEW: RTI AUTOSAR Blockset (p. 82)
FlexRay
n www.iso.org
n RTI Bypass Blockset (p. 62)

n ControlDesk Next Generation (p. 106)
n DS2671 Bus Board (SCALEXIO) (p. 324)
n DS4505 Interface Board (p. 424)
n MicroAutoBox II (p. 522)
n DS1450 Bus FIU Board (p. 508)
FMI
(Functional
Mockup Interface)
n www.fmi-standard.org
n VEOS (p. 100)

n SYNECT (p. 270, 280)
n SCALEXIO (p. 296)
ISO 26262
n www.iso.org
n AutomationDesk (p. 156)

n SCALEXIO (p. 296)
n dSPACE Simulator (p. 496)
Software

n dSPACE FlexRayConfiguration Package (p. 76)
n dSPACE Ethernet Configuration Package (p. 89)
n Platform API Package (p. 176)
n Variable Editor (p. 233)
n dSPACE ECU Flash Programming Tool (p. 235)
n dSPACE XCP Service (p. 232)
Hardware
n www.asam.net
2015
25
Engineering
ASAM
Application Fields
adasisforum
Application Fields / Aerospace Industry
Aerospace Industry
The challenge of control system development
Efficiency and Reliability

The aerospace industry has some of the most rigorous
standards and regulations of any field including the design
of electronic control systems. Developing such systems is a
high percentage of the overall cost. So efficiency is key. This
is why dSPACE prototyping systems, automatic code generation, and hardware-in-the-loop systems are used in
numerous applications throughout the aerospace industry.
dSPACE systems speed up the individual development
phases and improve hand-off between them. Whether you
use dSPACE systems throughout the entire development
or at individual stages, you can rely on them to make a real
impact on the efficiency of your development cycle.
n NEW: DO-178C workflow document for TargetLink
available (p. 219)
Aerospace-Specific Bus Interfaces

dSPACE offers special interface boards and software support
(via RTI blocksets and ConfigurationDesk) for connecting
modular dSPACE real-time systems and SCALEXIO to aerospace bus systems:
n MIL-STD-1553 (p. 328, p. 446)
n ARINC 429 (p. 327, p. 448)
n ARINC 717 (p. 450)
n AFDX1) (p. 329)
26
2015
Suitable for Numerous Application Scenarios

The bandwidth of possible application scenarios for dSPACE
products for the aerospace industry is very broad. You can
use dSPACE products for applications such as aircraft controller design (FADECs, thrust reverser, cabin pressure control,
etc.), for integration and test facilities (ITF), for helicopter
applications, for civil or for defence aviation, for commercial
or scientific puposes: dSPACE products can accelerate your
development process and help you improve the quality of
your control software.
Satellite Simulation Models
ASM Satellite provides ECSS-compliant satellite models
based on Simulink for simulating the attitudes and orbits
of LEO, MEO and GEO satellites with high precision.
The MicroAutoBox II can be equipped with an ARINC interface on its IP module slot by dSPACE Engineering Services.
Extended Visualization
For additional visualization (out-the-window view) during the real-time simulation, dSPACE offers integration
with the X-Plane flight simulator.
AFDX is a registered trademark of Airbus.
1)
Introduction
Application Fields / Aerospace Industry
Application Examples1)
Examples
Application
Details
Emergency Power
System
n Developing a fuel-cell-based
n Fuel-cell-based electricity independent of flight situation

n Developed with dSPACE prototyping system
Cabin Pressure
Control
n Developing cabin pressure
controls for a wide range of

aircraft types
n Autocoded software fulfils the strict requirements of aircraft
manufacturers and aviation authorities

Application Fields
aircraft emergency power system
n Automatic code generation with TargetLink according to safety
standard DO-178B level A

Simulating Satellite
Rendezvous
Unmanned Aerial
Vehicle (UAV)
n Simulating the relative
navigation of two satellites for

tasks such as capturing disused
satellites
n Subscale UAV for test flights
under extreme conditions
n Testing flight systems and studying the interaction of satellites and
robots
n dSPACE
system used as the core of the hardware-in-the-loop

simulation system
n Satellites real sensors used
n Study of extreme flight situations
n dSPACE system used as flight control computer (communication
via radio)
Electric Thrust
Reverser
n First fully electric thrust reverser
in commercial aviation
Software
n Complex real-time computations during test flights

n Thrust reverser integrated into major wide-body aircraft type
n Controller developed using a dSPACE prototyping system according
to safety standard DO-178B level A

for a business aircraft with an
advanced integration and test
facility, also using dSPACE tools
n Testing landing aid algorithms for
enhanced safety of helicopter

missions under poor vision
conditions (dust, sand, snow)
n Aircraft systems hardware and software interconnected with actual
aircraft electrical harnesses

n Real-time tests and simulation supported by dSPACE real-time
hardware and I/O

n Sensor-based landing aid with the help of dust-penetrating radar
sensors to display the helicopters position above ground

n Tests with dSPACE Simulator and AutomationDesk
n Runnig the algorithms on a MicroAutoBox in a flight simulator
1)
2015
27
Engineering
Sensor-Based
Landing Aid for
Helicopters
n Evaluating all systems integration
Hardware
Integration and
Test Facility (ITF)
Application Fields / Commercial & OffHighway Vehicles
Commercial & OffHighway Vehicles

ECU development for trucks, buses, and offhighway vehicles
Efficient ECU Development

The commercial vehicles industry is embracing embedded
electronics to optimize and expand the performance of
applications for trucks, buses, and off-highway vehicles.
Efficiency, productivity, and innovation are key in todays
vehicle electronics world. New technologies such as hybrid
drives are gaining momentum, and constant innovation
and optimization is necessary for control algorithms in
fields such as engine and powertrain, active and passive
safety, and special equipment. At the same time, ECU
software is becoming more complex, and numerous components from suppliers have to be integrated into vehicles.
Moreover, as a commercial vehicles manufacturer, you
usually have to handle numerous variants and custom
requirements. All this adds up to enormous complexity
and diversity. And commercial vehicles are usually produced in smaller quantities than passenger cars, though
28
they command far higher prices. As a consequence, both

the development process and the development tools in
the commercial vehicles industry have to be enormously
efficient and flexible to master cost and development time,
and to handle variants and integration tasks. To be
equipped for the challenges, you need a partner that can
provide you with a well-proven, highly efficient development environment: dSPACE. We will support you from
beginning to end, giving you proven, flexible, perfectly
integrated solutions from a single source. dSPACE supports
all the development phases, from architecture-based system design and block-diagram-based function prototyping
to ECU autocoding, HIL testing/virtual vehicles, virtual
validation, and data management. dSPACEs products and
development teams are in constant demand by many
major commercial vehicle manufacturers and suppliers.
2015
Introduction
Application Fields / Commercial & OffHighway Vehicles
Examples
Application
Details
Virtual Bus
Verifying the maturity of a new

bus electrics/electronics archi
tecture with HIL integration tests
Heavy Duty
Equipment
HIL and SIL tests for heavyduty

equipment with dSPACE
Automotive Simulation Models
(ASM)
Diesel Injection
Systems
Electronic control unit for diesel

engines
Hybrid Drive for

Wheel Loader
Developing a wheel loader with

a hybrid drive
By reducing fuel consumption, the hybrid drive lowers CO2 emissions

and provides considerable cost savings
Complete Truck
Electronic Tests
Testing complete truck electronics
n
n
n
Customer tested 33 networked ECUs with dSPACE Simulator

dSPACE ASM for variant handling
Automated testing with virtual rebuild of buses and trucks
Agricultural
Equipment
Developing transmission control

algorithms and further functio
nalities for farm tractors and
harvesters
n
n
TargetLink boosts coding speed like an additional programmer

Requirements with respect to code quality, readability and integration
capability were fully met
Application Fields
Early virtual test drives made possible by smooth interaction between

the environment model and dSPACE Simulators
n Frontloading error detection in the testing process shortens
development and test times
ASM diesel engine model and physical turbocharger model for testing
the engine ECU of heavy duty equipment, combined with customized
drivetrain model
n Testing laboratory with numerous HIL test benches from dSPACE
1)
2015
29
Engineering
Hardware
Software
Focus on improving injection and combustion processes and

considerably reducing fuel consumption and exhaust emissions
n TargetLink for complex control functions
Application Fields / Electric Drives
Electric Drives
Efficient controller development
Driving for Precision

Electric drives have been used increasingly over the past few
years. Not only in drive and automation technologies, but
also in vehicles. They have numerous advantages and wideranging application potential in many areas. Electric motors
can be very small and fit almost anywhere. They have very
high dynamics and can provide high torque at lower rotational speed. Other reasons are improved energy saving due
Electric Motors for Automotive Applications

In automotive applications, electric drives are increasingly
being incorporated into several complex, basic, and safetyrelevant vehicle functions. dSPACE products can accelerate
the ECU software development for electric drive applications
in many scenarios, such as for mild-/full hybrid cars, electric
vehicles, electric brake systems, powertrain actuators, electric
power steering (EPS), auxiliary aggregates (oil pump, water
pump) etc.
to power on demand, better controllability, and easier maintenance. dSPACE provides exactly the right products and
solutions for simulating electric drives, and for developing
and testing their servos or control units. From flexible dSPACE
development systems and special hardware and software for
electric drives to building complete systems, dSPACE will
accelerate your drive to the future.
Electric Motors for Non-Automotive Applications

Electric motors are also in widespread use in the capital
goods industry, medical technology, and aerospace sector.
Applications for dSPACE products in non-automotive control
software development include wind energy converters, electric trains, printing machines, medical equipment, robots etc.
n Battery management application examples (p. 23)
30
2015
Introduction
Application Fields / Electric Drives
Examples
Application
Details
Servocontrollers
in Industrial
Automation
n Automated software tests on a
n High number of controller variants

n Uses dSPACE Simulator including EMH Solution and ControlDesk
HIL simulator
with Python scripts
Mild Hybrid Car
n Developing hybrid control
functions for a mild hybrid car
Application Fields
n Simulation model based on the ASM Electric Components Library

n Electrical engine integrated into the car in addition to the gasoline
engine
n About 80% of the hybrid controller strategys code was generated
with dSPACE TargetLink

n MicroAutoBox and dSPACE Simulator used for controller
development and testing

Virtual Vehicle
n Test system for over 20
networked ECUs and various

electric drives
n Real-time execution of Automotive Simulation Models (ASM) with a
network simulator
n Function and diagnostic tests including random tests integrated into
test automation
n Studying control algorithms for
electric vehicles
Mechatronic
Testbench
Integration
n HIL test system for steering
systems with optic feedback for

a realistic drive feeling
n Development objective: a yaw-stable vehicle

n In-wheel motor technology
n Test drive with dSPACE hardware for fast algorithm calculation
n dSPACE hardware drives the electric motors via converters
Software
Electric Vehicle
n Simulation model provides features such as automatic parking and
lane-keeping assistants for enhancing comfort and active safety

n HIL system and driving simulator use dSPACE ASMs, visualization is
performed by dSPACE MotionDesk

n Successfully runs driver assistance systems
Permanent Magnet
Electrical Machine
n Integration testing with a
modular FPGA platform for SIL3

(EN 61508) drives technology
n Real-time modeling using FPGA-
based technology
n dSPACE HIL test bench for ensuring the drive controllers compliance
Hardware
FPGA-based Drive
Controller
with strict quality guidelines

n Uses AutomationDesk for automatic software integration tests
n HIL bench to emulate a permanent magnet electrical machine for
ECU functional validation

n Simulation of electric motors with the ASM XSG Electric Component
1)
2015
31
Engineering
Library and dSPACE Modular Hardware
Application Fields / Medical Engineering
Medical Engineering
Control development for medical applications
Safe, Fast Development

Safety and reliability are the top priorities in medical engineering and also a major challenge with the increasing complexity brought by innovative procedures and combinations of
medical devices. The solution comes from reliable, sophisticated development tools, that support your process even
while minimizing the time and cost of your projects.
dSPACE products enable the manufacturers of electronic
controls and control units to dramatically cut their development times and costs, and systematically increase their productivity.
Tools with Years of Engineering Success
dSPACE products have proven to be valuable tools in the field
of medical engineering in many ways (see also p. 33). They
have also played an important role in the automotive and
aerospace industries, as well as in mechatronic projects in
other industrial and academic fields, for many years.
From Early Concept to Volume Production

dSPACE tools support all stages of model-based development
by integrating the MATLAB/Simulink environment:
n Medical device design: Using dSPACE off-the-shelf
hardware components ensures efficient development
of algorithms and controller functions. Medical devices
can be validated at an early stage without expensive
and time-consuming in-house developments.
n Automatic code generation: Target code is generated
straight from your verified function models with no
manual programming, ensuring consistency between
model and code. Different simulation options support
the verification process from the model level early in
the development process to the final code.
n Medical device tests: Single software functions or
whole medical devices are tested automatically in a
simulated environment and with various test scenarios.
You can use dSPACE software and hardware for your entire
development process or in individual stages. Whichever you
choose to do, they will have a real impact on efficiency.
n
dSPACE Systems (p. 10)
n Certification for developing safety-critical systems
(p. 218)
32
2015
Introduction
Application Fields / Medical Engineering
Examples
Application
Details
Artificial
Respiration
n Neural impulse measurement for
n Artificial ventilation uses neural impulses to respond early to the
more comfortable artificial

respiration
patients breath initiation

n DS1005, DS2002, DS2102 used for simulation and signal
n Experimental system helps to
Blood Pump
Control
n Developing a controller that
Safe Surgical
Instruments
n Semiautomatic surgical saw for
Medical Training
Equipment
n Childbirth simulator for training
Prosthetic Wrist
patent an impedance sensor for

blood flow measurement through
the heart
continuously adjusts the output
of a blood pump to the patients
needs
safe sectioning of bones
obstetricians and residents

(robotic medical research project)
n Prosthetic wrist development for
n Mini-turbine for cardiac assistance

n Automatic speed control with a dSPACE prototyping system
n Avoiding trauma to soft tissue adjacent to bones

n Intelligent, sensor-based incision depth control
n dSPACE real-time system for overall control
n Practicing diagnostic and therapeutic manipulations safely with a
childbirth simulator
n ControlDesk used for configuration and MotionDesk for visualization
n Wrist simulator controlled by a dSPACE prototyping system for
functional testing and comparative assessment of wrist prostheses
1)
2015
33
Engineering
Hardware
more successful wrist replacement surgery
n dSPACE prototyping system and bypass techniques mimic a pacemaker

n Replay program for automated testing
Software
Impedance
Sensor for Heart
Pacemaker
Application Fields
measurement, and ControlDesk for experiment control
Application Fields / Research and Education
Research and Education

Industry-proven development tools for teaching and research
Controller Development with Industry-Proven Tools

dSPACE offers universities and research institutes flexible
systems with all the options needed for the model-based
development of mechatronic controls. dSPACE has pioneered
and optimized tools for controller development for many
years as an independent system partner. Cooperating closely
with the industry, we have created a comprehensive development environment that has become a standard in many
companies. dSPACE supports all the development phases,
from architecture-based system design and block-diagrambased function prototyping to autocoding and HIL testing.
NEW: MicroLabBox Compact Power in the Lab

Discover the new MicroLabBox, a compact all-in-one
prototyping system for the laboratory. It offers high
performance at a compact size and at low system costs.
Read more on page 516!
34
Offers for Academia

For universities, dSPACE has put together attractive product
packages: the ACE Kits real-time development systems
consisting of powerful hardware and comprehensive software
tools. All ACE Kits include software for seamlessly integrating
the modeling tools MATLAB and Simulink and for operating the real-time hardware. The price of each kit is far lower
than the total of all its individual components. The ACE Kits
enable you to:
n Test even the most complex control in real time
n Demonstrate high-end control development
from block diagram design to online controller
optimization
n Let your students gain experience with control
development tools
n Work under easy-to-use, intuitive Windows interfaces
n Implement your Simulink models on real-time hardware
within seconds
n Observe the effects of parameter changes on your
systems behavior
For educational purposes, there are special classroom
licenses available for several dSPACE software products.
2015
Introduction
Application Fields / Research and Education
Examples
Application
Details
Developing a SelfDriving Vehicle
n Electric, self-driving prototype
n Vehicle performs autonomous trips on the university campus
n Gravitational wave research with
dSPACE equipment
n Equipped with adaptive cruise control, automatic lane keeping, etc.

n MicroAutoBoxes used for evaluation and as an automatic driver control
n Researchers have set up an observatory dedicated to detecting
Application Fields
Gravitational Wave
Research
vehicle with driver assistance

functions included
gravitational waves
n dSPACE equipment helps to eliminate seismic noise
Miniature Robot
n Miniature robot for precision
assembly
Test Bench for
3-Phase Induction
Motors
n University students constructed
High-Speed Robots
n Developing new robots for high-
their own test bench for 3-phase

induction motors
speed manipulation tasks
n Control via dSPACE prototyping system

n Positioning workpieces at a repeat accuracy of under 10 m
n Control function development with dSPACE tools
n T
est bench playing a key role in the transfer of rapid control
prototyping technology between the university and industry

n Evaluating sensor and camera signals for robot control
n dSPACE modular hardware used for setting up a robust, high-
Intelligent Flying
System
n Unmanned aerial vehicle (UAV)
Nanopositioning
Machine
n Developing nanopositioning
that flies autonomously
machines with dSPACE tools
Software
performance real-time system

n Test environment based on hardware-in-the-loop (HIL) test equipment
n Developing
subsystems for communication between the UAV and

the ground station
n Positioning processes controlled by a DS1006 Processor Board and
various dSPACE I/O boards
1)
2015
35
Engineering
Hardware
n Positioning precision: 1 nm in a 200 x 200 x 25 mm positioning range
Application Fields / Other Fields
Other Fields
The challenge of streamlined control development
Cutting-Edge Technology
Wherever mechatronic control systems are used in drives,
industrial automation, medical applications, and others
controllers have to perform ever more complex tasks.
Manufacturers have realized that the gap between increasing
complexity and shorter development times can only be
closed by optimizing and parallelizing the development
tasks. dSPACE provides a complete and seamless development process with user-oriented products.
36
Accelerated Control Development

Well-proven development methods have become the standard in controller development: rapid control prototyping
with a dSPACE prototyping system, automatic code generation with TargetLink, and hardware-in-the-loop testing
with dSPACE Simulator. As a user of dSPACE systems, you
will find the same familiar working environment for developing, programming and testing control systems. The result
is an accelerated and simplified development process that
helps you put your ideas into practice faster and eliminate
errors sooner.
2015
Introduction
Application Fields / Other Fields
Adaptive UltraLightweight
Structures
Traction Control for

Railways
Testing regenerative energy

supplies (wind and solar) in the
megawatt range
Developing the converter control

Simulating load conditions, wind strength, and solar radiation
n Uses dSPACE prototyping system including the AC Motor Control
Solution
Active vibration control for

buildings
Speeding up traction control unit

development for AC electric
locomotives
Gas Turbine Ship

Propulsion
Testing the control software of a

gas turbine propulsion system
Personal
Transportation
System
New personal transportation

system uses MicroAutoBox as an
onboard control unit
Self-Navigating
Research Boat
Developing a selfnavigating
research boat with MicroAutoBox
on board
Beverage Filling
Machines
Simulation environment for

testing process control software
Application Fields
Regenerative
Energy
Details
Adaptive loadbearing shell

Reduces duration of vibration by 80 %
n Uses dSPACE prototyping system
n
Number of power test bench runs reduced by using dSPACE HIL

system in a very early development stage
n Using the DS5203 FPGAs fast computing feature for a highprecision
traction control simulation
dSPACE HIL system enables tough gas turbine ECU specifications to
be met
n Testing emergency shutdown and warning functions without
operating the turbine
Software
Application
Developing and testing control functions by using dSPACE proto

typing systems
n MicroAutoBox has a new job as a regular onboard control unit
Unmanned marine vehicle for carrying out numerous measurement
and observation tasks
n MicroAutoBox performs all the tasks involved in navigating and
steering the vehicle
dSPACE HIL system for testing a programmable logic controller (PLC)
reliably under the conditions of a simulated plant and for boosting
machine efficiency
1)
2015
37
Engineering
Hardware
Examples
Software
System Architecture Software ______________ 40
Implementation Software ________________ 48
Simulation Software ___________________ 100
Experiment and Visualization Software ______ 106
Test Automation Software _______________ 156
Production Code Generation Software ______ 180
ECU Interface Software _________________ 226
Real-Time Models _____________________ 236
Data Management Software _____________ 270
System Architecture Software / SystemDesk
SystemDesk
Modeling system architecture and generating virtual ECUs
Highlights
n
ECU software architecture and system development for
AUTOSAR R3 and R4
n
Easy and efficient modeling with diagrams and editors
n Generation of virtual ECUs for early validation with VEOS
or SCALEXIO
n
Coupling with TargetLink for function development
n
Complete and documented API for automation
n
Powerful validation of AUTOSAR models
Application Areas
SystemDesk is a system architecture tool that provides sophisticated and extensive support for modeling AUTOSAR
architectures and systems for application software. Comprehensive graphical support facilitates the first use but
also enables efficient and error-reduced working during
large-scale projects.
Additionally SystemDesk makes validating AUTOSAR-based
system architectures possible at an early development stage.
Therefore, virtual ECUs (V-ECUs) are generated out of the
application software and used as units under test with the
dSPACE simulation platforms, such as the PC-based simulation platform VEOS (p. 100) for validating the ECU software.
Two SystemDesk Versions for AUTOSAR

Because SystemDesk is an AUTOSAR tool, it supports all current AUTOSAR versions and new versions are implemented
continuously. Due to the considerable differences between
the latest AUTOSAR releases R3 and R4, SystemDesk is available in two major versions to give both AUTOSAR versions
comprehensive support.
SystemDesk 4.3
n
Supports AUTOSAR R4
n
n
SystemDesk Generation Module
The modules can be combined or used separately.
40
Key Benefits
n
Clear system overview due to graphical modeling with
diagrams
n
Flawless data input due to sophisticated dialogs and editors
n
Easy generation of virtual ECUs for validation purposes
n Reliable project quality through comprehensive rule-based
validation of consistency and correctness
n
Convenient development process due to automation of
recurring tasks or remote control by third-party tools via
the open API
SystemDesk 3.2
n
Supports AUTOSAR 3.x
n
n
SystemDesk Generation Module
n
SystemDesk RTE Generation Module
The SystemDesk Modeling Module is mandatory, the SystemDesk Generation Module and SystemDesk RTE Generation
Module are optional.
See the functionality overview on page 41 for a detailed

comparison of the two versions.
2015
Introduction
Functionality Overview
Functionality
Description
AUTOSAR modeling
n Modeling of software architectures and systems according to the AUTOSAR standard

n Clear overview due to graphical modeling with diagrams
n Sophisticated editors and dialogs for easy and faultless data entry
Application Fields
n Data exchange: flexible and easy-to-configure import and export of ARXML files
n Complete support of AUTOSAR meta model1)
n Import of communication matrices (DBC, LDF, FIBEX)
V-ECU generation
n Generation of virtual ECUs for simulation with VEOS and SCALEXIO

n Easy and mostly automatic integration
n Mostly automatic configuration and generation of required basic software modules according the system
requirements
n Partial configuration of basic software (such as COM)
n Comprehensive, rule-based validation of the system architecture and ECU software regarding consistency,
Process support
correctness, and completeness

n Easy data exchange with dSPACEs code generator TargetLink
n Coupleable with every AUTOSAR-compliant basic software configuration tool
Software
n Completely documented API for automating tasks such as report generation, creating a software
architecture or adding a composition with ports

n Hyperlink connection between model elements and single requirements in a requirement management
tool such as IBM Rational DOORS

1)
SystemDesk 4.x only
Order Information
Description
SystemDesk 4.x

(p. 43)
n Modeling AUTOSAR compositions and systems
containing one or more networked AUTOSAR ECUs
SystemDesk V-ECU Generation n Generating virtual ECUs (V-ECUs) including

nonoptimized RTE
Module (p. 46)
n Building simulation systems for offline simulation
with VEOS
n Generating optimized RTE production code
SystemDesk RTE Generation
Module
SystemDesk 3.x
Order Number
n SYD_MOD
Add-on for
SystemDesk
Modeling Module
n SYD_GEN
Add-on for
SystemDesk
Modeling Module
n SYD_RTE
Hardware
Product
Product
Description
Order Number
TargetLink
n Production code generation
See p. 180
Engineering
Relevant Software
n Integration of models, functions, and production code in software components and
architectures designed in SystemDesk

n Offline simulation of virtual ECUs
See p. 100
n Offline simulation of Simulink plant models together with virtual ECUs from SystemDesk
2015
41
VEOS
Working with SystemDesk

SystemDesk supports your development process with numerous features for intuitive working:
n
AUTOSAR-Compliant Modeling
n
Project Validation
Use SystemDesks authoring capabilities to create and edit

software architecture and system descriptions according to
the AUTOSAR standard.
Use SystemDesks validation to ensure that your project is

complete and consistent. You can define your own custom
validation rules to also check for company-specific project
requirements.
n
Dialogs and Diagrams
For an easy and efficient capture and configuration of common AUTOSAR data, SystemDesk offers convenient, preconfigured dialogs. Additionally special diagrams of the
software architecture and system elements help to keep an
overview over your model.
n
Complete and Documented Tool API
Use the open tool API to automate recurring design tasks

and extend the features of SystemDesk according to projectspecific requirements.
n
Import and Export of AUTOSAR Files
n
Data Exchange with TargetLink
You can exchange data seamlessly between SystemDesk and

dSPACE's production code generator TargetLink (p. 180).
This gives you a safe process in a model-based development
environment for including the actual functionality in the
software architecture.
SystemDesk offers comprehensive features for importing

and exporting AUTOSAR files. You can flexibly configure
the data to be included in each individual project. Import
and export are done with just a few clicks.
Connecting and using configuration and version management tools with SystemDesk is made easy with special import and export options.
n
Generation of Virtual ECUs for Simulation
Use SystemDesk to generate virtual ECUs (V-ECUs) that

include basic software modules to get a realistic representation of the real ECU. Simulate the V-ECU with VEOS (p.
100) or SCALEXIO (p. 296) to validate your software when
a hardware prototype is not available (yet).
42
2015
Introduction
Application Fields
Application Areas
The SystemDesk Modeling Module enables the modeling
of AUTOSAR software architectures and systems containing
one or more networked AUTOSAR ECUs. It supports the
software architecture development process from modeling software components (SWCs) to specifying system
aspects including the hardware topology and network
communication.
Software
Key Benefits
n
Easy workflow and intuitive working environment
n
Easy start in working with AUTOSAR
n
Ideally suited for large production projects
n
Reliable data exchange between different project
members
Example Workflow for Modeling an ECU Software Architecture According to AUTOSAR
Hardware
Engineering
The first step is to define the software components (SWCs),

which each represent a functionality, and the data they exchange with each other. Since the components can be developed individually, development work can be split between
several developers. For example, an OEM can develop an overall
system design and then extract the specifications for suppliers
to provide the SWCs.
Additionally existing SWCs or other parts of the architecture,

such as data types, can be imported for reusing existing software. SystemDesk supports the modeling process by a graphical
representation of the SWCs and their interconnections. New
SWCs, their ports and connections are modeled in this diagram,
providing developers with an intuitive working method and
offering a well-defined overview of even the most complex
system.
n
Designing Software Components
The next step is to define and configure the internal behavior of the software components. Among others, this comprises runnables, which are C functions inside of software
components, and the means of communication between
them and with the outside of the software component.
SystemDesk supports the configuration with sophisticated
dialogs. These dialogs offer guidance so you can enter data

easily and avoid potential errors.
Additionally several integrated validation procedures make
sure the modeled elements and references are AUTOSARcompliant and consistent.
2015
43
n
Modeling the Software Architecture
n
Data Exchange with TargetLink
After the software components are designed, their functions can be implemented from any C code generation tool.
SystemDesk is closely coupled with dSPACE's production
code generator TargetLink (p. 180). Both tools support an
SWC container concept for transferring all required data.
All the files in this container that belong to a modeled
software component, such as ARXML files for the software
component, data types and interfaces, are exported from
SystemDesk. TargetLink users import the SWC container
and use the defined elements to automatically create an
AUTOSAR frame model for the components. Then they
develop the actual functionality and generate AUTOSARcompliant code. This code is transferred back to SystemDesk
together with any generated ASAP2 files, plus the ARXML
files with additional implementation information. The SWC
containers are handled and merged in the SWC Container
Manager, a specialized tool with a graphical user interface
which can be opened from SystemDesk and TargetLink.

Once the options for the export are defined, such as which
files and data to include, the following import/export just
requires a few clicks.
n
Modeling the System
In the last process step, a system consisting of a software

architecture, a hardware topology, and a network communication description is created.
The software architecture was developed in the first step
when designing the software components.
The hardware topology of an E/E system can be specified
independently of any software architecture. It describes the
available ECUs and their interconnections via buses. Each
software component from the software architecture has to
be mapped to one ECU.
The communication between atomic software components
that reside on different ECUs (inter-ECU communication) has
to be mapped to the network communication. This means
that data elements have to be mapped to network signals.
A predefined communication matrix, such as a DBC, FIBEX,
or LDF file, can be imported into SystemDesk to configure
the network communication.
In SystemDesk you can create a custom view of the system
to concentrate on single parts or tasks. Convenient map-
44
ping editors present the data in a clear order and offer easy
means for working on specific tasks.
Once the system is modeled, it can be integrated either
in a basic software configuration tool to create the final
ECU or in SystemDesk as a virtual ECU for simulation on a
dSPACE simulation platform.
Special editors in SystemDesk make the mapping convenient.
2015
Introduction
n Data Transfer to Basic Software Configuration Tools
Application Fields
To develop the basic software components for the final ECU,

the system description modeled in SystemDesk has to be
transferred to a basic software configuration tool. SystemDesk can be connected to any AUTOSAR-compliant basic
software configuration tool for generating and configuring
basic software modules such as OS and COM. You can flexibly define which data to include in the export and save this
configuration for the next export. Additionally, before you
export your system description, an integrated validation in
SystemDesk enables you to check the model for correctness
and integrity against project specifications.
Hardware
from SystemDesk, the parameters for the basic software can

be configured in EB tresos Studio. The tool automatically
generates the implementation code for the operating system and other AUTOSAR-compliant basic software modules.
Together with the C code for the SWCs, the implementation code from EB tresos Studio makes up the final code
for the ECU.
2015
45
Engineering
Cooperation with EB Automotive

dSPACE and EB Automotive cooperate to offer an optimal
tool chain for developing AUTOSAR-based ECU software:
dSPACE TargetLink, dSPACE SystemDesk, and EB tresos
Studio.
EB tresos Studio allows complete ECU basic software configuration, integration and validation in one single tool
environment. Based on the system description files exported
Software
By default, SystemDesk supports data exchange with EB

tresos. Additional support for further third-party tools can
be added.
SystemDesk VECU Generation Module

Application Areas
For virtual validation applications, the SystemDesk V-ECU
Generation Module lets you model and generate virtual
ECUs (V-ECUs). V-ECUs enable you to test the system's overall behavior with either the PC-based simulation platform
VEOS (p. 100) or the hardware-in-the-loop (HIL) simulator
SCALEXIO (p. 293) as soon as the implementation with
C code is available.
A V-ECU can consist of just a single application software
component (SWC) containing multiple functions, or a more
complex software architecture containing several connected
application SWCs including the basic SWCs.
46
Key Benefits
n
Guided creation of virtual ECUs out of the software architecture
n
Selective adjustment of BSW components tailored to
specific requirements
n
All required basic software modules for the simulation
Feature Overview
The SystemDesk V-ECU Generation Module makes it possible to configure and generate BSW modules, e.g., the
RTE, OS, or I/O hardware abstraction, or the ECU State Manager. The module provides convenient editors for this, for
example, for mapping runnables to tasks. It also offers
process support for automatic BSW module updates and
configuration as well as for generating the V-ECU implementation. To configure V-ECUs for different test and validation scenarios, you can define RTE intervention points.
All of SystemDesks V-ECU configuration and generation
options can be controlled via integrated scripting options

or the COM-based automation interface. This enables you
to integrate the generation and building of V-ECUs into
your testing and development processes and to automate
configuration steps, for example, with Python-based scripts.
V-ECUs can also be connected to Simulink plant models
outside of SystemDesk. The resulting simulation system
comprises executable representations of ECUs, including
their environment and all their interconnections.
Integration Into the Development Tool Chain

V-ECUs created with SystemDesk comprise components
from the application and the basic software, and provide
functionalities comparable to those of real ECUs. V-ECUs
can be simulated with the dSPACE PC-based simulation
platform VEOS for an early verification of the ECU software. For rapid control prototyping (RCP) purposes, the RTI
AUTOSAR Blockset (p. 82) allows V-ECUs to be deployed
on dSPACEs RCP system MicroAutoBox II (p. 522). They
can be run together with the physical plant, and evaluated in the laboratory or in the vehicle. For experimenting
and visualizing the simulation, you can use ControlDesk

Next Generation (p. 106). VEOS offline simulation of complex software architectures can be used for single V-ECUs
and ECU networks including bus simulation, and also for
software-in-the-loop (SIL) and processor-in-the-loop (PIL)
simulation. A V-ECU can also be used for HIL simulation
with dSPACE SCALEXIO if the ECU hardware prototype is
not available yet. ControlDesk Next Generation is again used
for this, with the same layouts as for simulation with VEOS.
2015
Introduction
n
Bus Simulation
Application Fields
When the hardware topology has been defined, you can

distribute software components in SystemDesk to different ECUs, import predefined communication matrixes and
generate simulation systems. For each ECU, SystemDesk
provides the required basic software components.
You can use VEOS to simulate the bus communication between the ECUs. Arbitration effects, transfer times and
transmission delays of bus messages or ECU and bus breakdowns can be simulated for CAN and LIN buses and verified in an early phase of development. Networks including
FlexRay buses can be modeled and simulated as idealized
buses.
Software
Use Cases
n
Simulation at Software Architecture Level
The modeled software architectures have to be verified
and tested, even if the underlying hardware topology is
not defined yet (virtual functional bus (VFB) mode). Hereby
functional errors or error behavior in the communication
between software components can be found and fixed as
soon as possible. SystemDesk provides the basic software
modules needed for simulation, such as RTE and OS, and
offers options for modeling, configuring and integrating
basic software components.
Together with the PC-based simulation platform VEOS,
software architectures can be simulated early in the development phase.
n
Processor-in-the-Loop Simulation
n
Further Features
In addition to software-in-the-loop (SIL) simulation for

simulation at the software architecture level or bus simulation, SystemDesk also supports processor-in-the-loop (PIL)
simulation. Therefore, you can use SystemDesk to build
virtual ECUs for different target processors and execute
them on the associated evaluation board by using VEOS.
By simulating the ECU code on the target processor, you
can test the memory consumption and other effects in a
realistic scenario.
n
Code coverage: Analyzes to which extent the code
has been tested. SystemDesk offers code coverage

analysis with CTC++ from Testwell. The code coverage
information is collected during the simulation run and
the results are displayed on a HTML page.
n
Integrating compiled Windows object files
n
Integrating Simulink models as AUTOSAR SWCs
n
Debugging, e.g., in step mode
2015
47
Engineering
Hardware
Implementation Software / ConfigurationDesk
ConfigurationDesk
Configuration and implementation software for dSPACE SCALEXIO Hardware
Highlights
n Configure real-time applications graphically
n Manage signal paths between external devices
(like ECUs or loads) and behavior model interfaces
n Implement behavior model code and I/O function
code on dSPACE hardware
n Import of virtual ECUs
n NEW: Multicore and multi-processing-unit applications
n NEW: Support of Functional Mock-up Units (FMU)
Application Fields
ConfigurationDesk is an intuitive, graphical configuration
and implementation tool. It is ideal for handling HIL realtime applications based on dSPACE SCALEXIO hardware,
and for implementing behavior models and I/O function
code on dSPACE SCALEXIO hardware. You can define and
document external devices such as ECUs and loads, including their signal properties (descriptions, electrical properties,
failure simulation settings, load settings). ConfigurationDesk
displays user-defined views of the signal path between the
ECU pins/load pins and the behavior model interfaces.
The Benefits
With ConfigurationDesk, it is easy to implement the behavior
model code (from MATLAB/Simulink/Simulink Coder)
and the I/O function code (from ConfigurationDesk) on the
dSPACE SCALEXIO hardware. The entire build process for a
real-time application is handled by ConfigurationDesk. Comprehensive documentation options and graphical displays
give you great project transparency a great advantage
with large-scale HIL project especially. You can assemble
and configure the project-specific hardware offline as a
"virtual system", in other words, as a purely software-based
configuration. A real-time application can be executed for
test runs even if parts of the necessary (and configured) I/O
hardware are not physically available. In addition, you can
generate a Microsoft Excel file with information on the
wiring harness and on external devices.
ConfigurationDesk Version for RapidPro

There is a special ConfigurationDesk version available for configuring the
dSPACE RapidPro hardware. This configuration version supports you in
configuring your RapidPro hardware and wiring it to sensors and actuators,
and enables you to monitor the hardware states during operation.
For more information about ConfigurationDesk for RapidPro,
please see p. 52
48
2015
Introduction
Functionality
Description
I/O configuration and

documentation
n I/O configuration for connecting a MATLAB/Simulink behavior model to dSPACE SCALEXIO hardware:
n
External device topologies (properties of ECU pins and load pins)

Device port mapping (connections between the ECU/load pins and the signal ports of an I/O function)
n I/O functions (describe the functionality between a set of external device ports and a set of model ports
independently of the hardware topology)
n Model port mapping (connections between function ports and model ports)
n Model topology (model ports used for the ConfigurationDesk application)
n Hardware resource assignment (mapping I/O functions to hardware resources)
n Hardware topology (hardware resources used by I/O functions)
n Documentation:
n External device topologies (properties of ECU pins/load pins)
n Model topology (describes the interface to the MATLAB/Simulink model)
n Hardware topology (describes the simulator hardware: boards, internal wiring, internal loads, board locations, )
n Microsoft Excel file with pin information for external wiring harnesses
n CAN and LIN signals are configured with the RTI CAN MultiMessage Blockset and the RTI LIN MultiMessage Blockset.
FlexRay nodes are configured with the dSPACE FlexRay Configuration Package.
Software
Real-time code generation
Application Fields
n Complete build process for I/O functions (ConfigurationDesk) and the behavior model (MATLAB/Simulink/Simulink Coder)
Order Information
Products
Order Number
ConfigurationDesk Loader Version (SCALEXIO)

For use without license, limited function range (downloading real-time
applications possible, but no changes or builds allowed)
n Free of charge
ConfigurationDesk Implementation Version

(SCALEXIO)
n CFD_I_100 (implementation version for 100 functions)
n License for SCALEXIO Real-Time Library is needed
Hardware

n CFD_I_UNLTD (for an unlimited number of functions)
n CFD_I_MC (implementation version for SCALEXIO multicore applications)
n License for SCALEXIO Real-Time Library for is needed
SCALEXIO Failure Simulation (p. 301)
n SCLX_FS_100 (for 100 functions)

Engineering
n SCLX_FS_UNLTD (for an unlimited number of functions)
SCALEXIO Real-Time Library for downloading and handling real-time

applications for the SCALEXIO system
n SCLX_RTLib
n SCLX_RTLib_MC (for multicore applications)
n SCLX_RTLib_VECU (for applications containing V-ECUs)
Relevant Software
Required
Optional
Order Number
n MathWorks MATLAB
/Simulink /Simulink Coder
n Operating system
www.dspace.com/goto?os_compatibility
n RTI CAN MultiMessage Blockset (p. 70)
n RTICANMM_BS (for applications containing CAN bus configurations)
n RTI LIN MultiMessage Blockset (p. 73)
n RTILINMM_BS (for applications containing LIN bus configurations)
n SCALEXIO Ethernet Solution (p. 89)
n SCLX_ETH_SOL (for adding Ethernet I/O functions to ConfigurationDesk)
n dSPACE FlexRay Configuration Package (p. 76)
n FCP (for applications containing FlexRay bus configurations)
n Microsoft Excel
2015
49
Software
Application (Example)
Creating and Executing a New Real-Time Application
with ConfigurationDesk
You can quickly create new real-time applications with
ConfigurationDesk. The typical procedure is shown below,
though the steps can be performed in a different order.
Step
Description
1. Create project and application
n Whole real-time applications can be managed in ConfigurationDesk. This includes not only the associated
2. Define external devices
n It takes just a few clicks to define the interfaces and signal properties of external devices such as ECUs
3. Select and configure I/O functions
n I/O ports can be connected to the external devices graphically. You can define different views to focus on
ConfigurationDesk application data, but also general files such as project plans and specifications.
and loads in ConfigurationDesk.
specific data sets. I/O functions automatically fetch failure simulation settings and load settings from the
definitions of external devices.
4. Create model ports
n The behavior model and ConfigurationDesk applications are connected via model port blocks.
5. Design the Simulink model
n The model port blocks generated by ConfigurationDesk can be integrated into the MATLAB/Simulink
model to implement the inputs and outputs between the model and the hardware. You can also use
Simulink inputs and outputs in the model instead (only at the topmost model level, not inside subsystems).
6. Assign hardware resources
n With ConfigurationDesk, the hardware resources (such as channels on the DS2601 Signal Measurement
Board or the DS2621 Signal Generation Board) can be quickly assigned to the I/O functions.
7. Run the build process for the application n You can run the entire build process with ConfigurationDesk, both for the I/O functions and for
the behavior model.
and create the application for the dSPACE
hardware
8. Download the application to the
dSPACE hardware
n The real-time application can be transferred to the dSPACE hardware quickly.
Failure Simulation License

To use failure simulation with SCALEXIO, you have to
activate it with an additional FIU license. This must match
the number of I/O channels you want to use. For example,
if you work with a ConfigurationDesk license for 300 I/O
functions, you require a SCALEXIO Failure Simulation License
for 300 functions.
Importing Virtual ECUs

In ConfigurationDesk you can integrate virtual ECUs (VECUs) into a real-time application just like any other behavior
models. With the SCALEXIO real-time hardware (p. 296),
V-ECUs can be simulated alone or in combination with real
ECUs. The V-ECUs can contain CAN controllers to simulate
CAN bus communication between the ECUs.
50
For further information on failure simulation with

SCALEXIO, please see p.301.
For information on generating V-ECUs, please refer to

SystemDesk V-ECU Generation Module (p. 46).
2015
Introduction
Application Fields
The user workflow for importing and connecting FMUs to

other model interfaces and to I/O is identical to the workflow
for V-ECUs and Simulink models.
For more information on FMI and its support in the dSPACE
tool chain, please refer to page 25.
2015
51
Engineering
Hardware
NEW: Support of Functional Mock-up Units

ConfigurationDesk supports the open Functional Mock-up
Interface (FMI) standard. This enables the users to use different modeling approaches (e.g., based on physical modeling
with Modelica) by using Functional Mock-up Units (FMUs).
In HIL projects, FMUs can be integrated together with V-ECUs
and Simulink models.
The intermodel communication in this workflow is transferred from Simulink to ConfigurationDesk.

One processor core executes one model. Several models
are combined to processing-unit-applications. These can be
assigned to processing units in ConfigurationDesk, which
automatically performs the core-to-model assignment within
each unit.
One processing unit consists of several processor cores. One
processor core in each processing unit is always reserved for
communication with the host PC. The other cores can be
used for behavior model calculation.
Software
NEW: Multicore or Multi-Processing-Units for

Complex Models
Large, complex models can be distributed across multiple
processing units and processor cores to ensure the simulation runs in real time. Two different workflows are possible
for this. The first is to use separate Simulink models for
each core and import them into ConfigurationDesk. The
intermodel communication in this workflow is configured
in ConfigurationDesk. In the second workflow, there is one
overall Simulink model for the whole application, and a
special Simulink block is used to specify which of its subsystems should be computed together on one core. The overall
model is then automatically split into separate model files.
Configuration Version for RapidPro

Key Features
n Configuring the RapidPro hardware (p. 542)
n Monitoring the hardware states during operation
n Support for wiring the RapidPro hardware to sensors
and actuators
Application Area
The configuration version offers you configuration and diagnostics functions for RapidPro hardware (p. 542) and
supports you in putting the hardware into operation.
The RapidPro hardware acts as an extension to dSPACE
prototyping systems to cover application scenarios which
require signal conditioning, power stages, and intelligent
I/O subsystems.
52
Benefits
The hardware is displayed in an intuitive structured view.
You can change the configurations of the individual module
channels and monitor the hardware states during operation.
Channel-specific diagnostics (open load, etc.) are provided in
a list view. You can manage the configurations of different
hardware setups via the Project Manager. A pinout list for
wiring the RapidPro hardware to sensors and actuators can
be exported as a comma-separated value (CSV) file or a
Microsoft Excel file.
2015
Introduction
Functionality
Description
RapidPro hardware configuration
ConfigurationDesk displays the RapidPro hardware in a structured view, and provides intuitive access to all the
relevant configuration settings. Monitoring of analog and digital signal values is available to support you in
connecting sensors and actuators to the RapidPro hardware when the system is put into operation.
Diagnostics handling
During operation, diagnostic information such as overcurrent, short circuit, open load, overheat, and over- and
undervoltage detection is monitored and displayed. This makes it easy to detect and locate faults.
Project management
ConfigurationDesks Project Manager allows you to organize all the relevant project information such as hardware
configurations and application-specific data.
Wiring information
To help you wire your RapidPro hardware, a pinout list with all the relevant information can be exported as
a comma-separated value (CSV) file or a Microsoft Excel file.
Application Fields
Order Number
ConfigurationDesk Loader Version (RapidPro)

For use without license, limited function range
n Free of charge
ConfigurationDesk Configuration Version

(RapidPro)
n CFD-C
2015
53
Engineering
Hardware
Products
Software
Order Information
Implementation Software / RealTime Interface
RealTime Interface
Implementation software for running models on dSPACE hardware
Highlights
n Automatic implementation of MATLAB/Simulink/
Stateflow models on dSPACE hardware
n Automatic code generation
n Graphical I/O configuration via comprehensive
Simulink block libraries
n Easy and safe to use due to automatic consistency
checks
n Support of model referencing hierarchies1)
Application Areas
No matter whether you are performing rapid control prototyping or hardware-in-the-loop simulation: Real-Time Interface (RTI) is the link between dSPACE hardware and the
development software MATLAB/Simulink/Stateflow from
MathWorks.
Key Benefits
RTI lets you concentrate fully on the actual design process
and carry out fast design iterations. It extends the C code
generator Simulink Coder (formerly Real-Time Workshop)
Working with RTI

To connect your model to a dSPACE I/O board, just drag &
drop the I/O module from the RTI block library and then connect it to the Simulink blocks. All settings, such as parameterization, are available by clicking the appropriate blocks.
Simulink Coder (formerly Real-Time Workshop) generates
the model code while RTI provides blocks that implement the
I/O capabilities of dSPACE systems in your Simulink models,
thus preparing the model for the real-time application. Your
real-time model is compiled, downloaded, and started automatically on your real-time hardware, without you having to
write a single line of code. RTI guides you during the configuration. RTI provides consistency checks, so potential errors
can be identified and corrected before or during the build
process.
54
2015
for the seamless, automatic implementation of your

Simulink and Stateflow models on the real-time hardware.
The implementation time is greatly reduced. The hardware
configuration for the real-time application is guided by
automatic consistency checks to prevent parameterization
errors. For maximum flexibility, each RTI version supports
several different MATLAB releases (see www.dspace.com/
go/Compatibility). Models from most previous MATLAB and
RTI releases are migrated automatically when newer versions
of RTI are used.
Comprehensive Functionalities
RTI handles any kind of continuous-time, discrete-time, and
multirate system. Depending on the I/O hardware, different
channels of the same I/O board can be used with different
sample rates, and even in different subsystems. RTI supports
asynchronous events and lets you set task priorities and task
overrun strategies for executing the interrupt-driven subsystems. It also supports time-triggered tasks and timetables,
which allow you to implement tasks and groups of tasks
with variable or predefined delay times in relation to an
associated trigger event. This makes task handling in your
model very flexible. In addition, RTI offers checks which help
avoid double or improper use of channels.
1)
Please contact dSPACE for information on features and limitations.
Introduction
Implementation Software / Real-Time Interface
Functionality
Description
I/O configuration
n
Comprehensive block library for specifying the hardware setup
n
Configuration of dSPACE I/O simply by connecting the relevant blocks to the Simulink blocks
Generating real-time code
Automatic task definition
parameter specification, such as voltage ranges, resolutions, digital I/O, serial interface parameters,
and PWM frequencies
n
Automatic checks on parameter ranges and consistency
n
I/O access anywhere in your model and at different sample rates
n
Separate blocks for different functions of complex I/O boards
n
Data typing and data-typed I/O
n
Asynchronous execution of Simulink subsystems triggered by hardware or software interrupts
n
S-functions and user-written code
n
Generation of C code by Simulink Coder (formerly Real-Time Workshop)
n
C code optimization for real-time implementations
n
Support of Simulink Coder (formerly Real-Time Workshop) code optimizations
n
Generation of initialization functions and I/O function calls
Application Fields
n
I/O
n
Support of multirate systems and preemptive, priority-based multitasking
n
Single timer and multiple timer task mode
n
Asynchronous tasks
Software
n
External hardware interrupts
n
Software interrupts
n
Configurable priority and overrun handling for each task
n
Turnaround time measurement for each task
n
Optional synchronization of periodic timer tasks to external events
n
Time-triggered tasks and timetables
n
Non-real-time simulation modes
Invoking the compiler
n
Automatic compiler call that compiles and links the model
Loading and starting the application
n
Program download to the real-time hardware
n
Simulation control
n
Interactive control, monitoring, and data acquisition with ControlDesk Next Generation (p. 106)
Hardware
n
Data acquisition with time stamps
Order Information
Order Number
Real-Time Interface
n
RTI
2015
55
Engineering
Product
Relevant Software and Hardware

Software
Required
Order Number
n
Microtec C Compiler (p. 98) for DS1103, DS1104, DS1005, and MicroAutoBoxII
n
CCPPPC
n
GNU C Compiler for DS1006
n
DS1006_COMP
n
n
DS1007_COMP
n
GNU C Compiler for MicroLabBox
n
MLBX_COMP
n
Operating system: www.dspace.com/goto?os_compatibility
n
MATLAB/Simulink/Simulink Coder (formerly Real-Time Workshop) from
The MathWorks
For maximum flexibility, each RTI release supports several different MATLAB
releases (see www.dspace.com/goto?Compatibility)
Optional
n
Real-Time Interface for Multiprocessor Systems RTI-MP (p. 60)
n
RTI_MP
n
Real-Time Interface Bypass Blockset (p. 62)
n
RTIBYPASS_BS
n
Real-Time Interface CAN Blockset (p. 68)
n
RTICAN_BS
n
Real-Time Interface CAN MultiMessage Blockset (p. 70)
n
RTICANMM_BS
n
Real-Time Interface LIN MultiMessage Blockset (p. 73)
n
RTILINMM_BS
n
dSPACE FlexRay Configuration Package (p. 76)
n
FCP
n
RTI RapidPro Control Unit Blockset (p. 549)
n
RTIRAPIDPRO_BS
n
NEW: RTI AUTOSAR Blockset (p. 82)
n
RTIAUTOSAR_PKG
n
RTI FPGA Programming Blockset (p. 86)
n
RTIFPGA_BS
n
Stateflow/Stateflow Coder from The MathWorks
n
Ethernet Blocksets (p. 88)
Hardware
Required
See p. 88
Order Number
n
Pentium
4 at 2 GHz (or equivalent)
n
1 GB RAM (minimum), 2 GB RAM or more (recommended)
Optional
n
DS1103 PPC Controller Board (p. 334)
n
DS1103
n
DS1104 R&D Controller Board (p. 340)
n
DS1104
n
DS1005 PPC Board (p. 352)
n
DS1005
n
DS1006 Processor Board (p. 356)
n
DS1006
n
NEW: DS1007 PPC Processor Board (p. 362)
n
DS1007
n
MicroAutoBox II (p. 522)1)
n
See p. 522
n
NEW: MicroLabBox with front panel
n
MLBX_1302F
n
NEW: MicroLabBox with top panel
n
MLBX_1302T
The former MicroAutoBox can also be used.
1)
Implementing a Model with Real-Time Interface

Model Design
In this example, the closed control loop of the positioning
system for a hard disk drive is shown in the block diagram.
Both the controller and the model of the controlled system
are designed in the MATLAB/Simulink development environment.
56
2015
Introduction
Application Fields
Parameter Specification
I/O parameters are specified by double-clicking an I/O block
and entering the data in graphical user interfaces. In this
example, the input signals are the feedback value and the
reference signal. The reference signal now comes from an
external signal generator and is read in by an ADC block.
The output signal from the controller is the control signal
u_M, which is output by the hardware via a DAC block.
2015
57
Engineering
Hardware
Software
Graphical I/O Configuration

When you have finished testing your model in Simulink, it
has to be prepared for implementation on the real-time
hardware. The plant model is replaced by I/O blocks that
form the interfaces to the real controlled system. To add an
I/O model, simply drag a block from the RTI I/O library to
the model and connect the block with the I/O of the controller.
Implementation on dSPACE Hardware

Automatic implementation of the Simulink model on dSPACE
hardware is the key to rapid design iterations. With RTI you
will not see a single line of code during this process. A
single click on Build starts the implementation, including
code generation, compiling, and downloading. You can
select an integration algorithm and a step size in the solver
page of the Simulation Parameters dialog. Build procedures
can also be automated with the help of scripts. This is
especially useful for large models.
58
Interaction with Experiment Software

When your application is running on the real-time hardware,
the whole dSPACE experiment software is at your disposal.
RTI ensures that you have control over each individual variable immediately after the implementation process.
ControlDesk Next Generation provides an instrument panel
that enables you to change parameters and monitor signals
without regenerating the code. ControlDesk Next Generation also displays the time histories of any variable used by
your application.
2015
Introduction
Blocksets for Real-Time Interface
Real-Time Interface
CAN Blockset
Real-Time Interface
CAN MultiMessage
Blockset
Real-Time Interface
RapidPro Control Unit
Blockset
Real-Time Interface
Bypass Blockset
dSPACE FlexRay
Configuration
Package
Real-Time Interface
LIN MultiMessage
Blockset
Real-Time Interface
AUTOSAR Blockset
Real-Time Interface
FPGA Programming
Blockset
Ethernet Blocksets
RTI Bypass Blockset

For configuring bypass applications.
CAN Blocksets
For combining dSPACE systems with CAN communication
networks.
n RTI CAN Blockset (p. 68)

For combining dSPACE systems with LIN communication
networks.
dSPACE FlexRay Configuration Package

For configuring dSPACE systems in FlexRay communication networks.
RTI RapidPro Control Unit Blockset

Extensive I/O functionalities for the MicroAutoBox II1) or
DS1005 used in combination with the RapidPro Control
Unit, e.g., for engine, chassis, and drives control.
n RTI RapidPro Control Unit Blockset (p. 549)

Using AUTOSAR software components in a MATLAB/
Simulink environment
n RTI AUTOSAR Blockset (p. 82)

Integrating FPGA models in dSPACE systems.
n RTI FPGA Programming Blockset (p. 86)
Engineering
Real-Time Interface for Multiprocessor Systems

For graphical setup of multiprocessor structures.
n RTI-MP (p. 60)
Hardware
Software
Ethernet Blocksets
Connecting dSPACE hardware to other devices via Ethernet
n Ethernet Blocksets (p. 88)
1)
2015
59
Real-Time Interface
for Multiprocessor Systems
Application Fields
Supporting dSPACE Hardware

No matter whether you are using dSPACE systems with
single-board hardware, modular hardware, or MicroAutoBoxII1): RTI supports all dSPACE real-time processors and
allows convenient model and I/O configuration of your
dSPACE system.
Implementation Software / RealTime Interface for Multiprocessor Systems (RTIMP)
RealTime Interface for Multiprocessor Systems (RTIMP)

For graphical setup of multiprocessor structures
Highlights
n Interprocessor interrupts for synchronized tasks
across several CPUs
n Graphical setup of multiprocessor systems
within Simulink
60
Application Areas
The multiprocessor option for Real-Time Interface (RTI-MP)
supports multiprocessor and multicore systems based on
dSPACEs modular hardware and helps to increase the
performance of real-time simulations. It assists in setting
up multiprocessor networks, including the communication
channels. Multicore applications are configured in the same
way as multiprocessor applications.
Key Benefits
RTI-MP offers a maximum of convenience to accomplish
tasks such as:
n Partitioning the system for optimum processor load
n Defining interprocessor communication channels
n Producing the communication code for a network
of several processors or cores
System dynamics can be designed in Simulink.
Working with RTI-MP

RTI-MP enables you to partition your system model and allocate the parts to the processors or cores by using simple
drag & drop operations. Each processor submodel can be
adjusted individually for optimum performance, including
step sizes, integration algorithms and trigger conditions.
After specification, you can implement your model on the
processor boards with a single mouse click. Build procedures
can also be automated with the help of scripts.
RTI-MP for dSPACE Simulator

In practical development work, several processor boards
are often connected to one networked dSPACE Simulator
(p. 496), and highly dynamic simulation models exchange
simulation data via Gigalink modules. An easy way of specifying the topology of a whole network is therefore essential.
RTI-MP offers special blocks to configure Gigalink communication within Simulink. The real-time application, including
real-time synchronization between the simulators, can then
be generated with a single click.
2015
Introduction
Implementation Software / RealTime Interface for Multiprocessor Systems (RTIMP)
Functionality
Description
Partitioning the Simulink model
Adding Simulink blocks for model partitioning via drag & drop
Generation of highly optimized realtime simulation engine and communication code
n Support of triggered subsystems distributed over multiple processors or cores
n Full support of interprocessor interrupts
n
Integration algorithm and step size specific to each processor and core
Single/multitasking mode
n Swinging buffer or shared memory communication mechanism for each individual connection
n Interprocessor communication at different sampling rates
Optimizing speed and accuracy
Testing and documenting
Implementing the model on

multiprocessor or multicore hardware
Communication mechanisms
Application Fields
Documentation of entire multiprocessor setup
Automatic code generation for one processor or complete system

Download and start with a single click
n Data acquisition with time stamps
n Profile information for communication channels for optimizing the partitioning
n
Communication via highspeed optical connection (Gigalink) enabled

Asynchronous data transfer in shared memory mode
n Synchronized and unsynchronized block data transfer in swinging buffer mode
n Buffering and unbuffering of data via communication connection
Software
Order Information
Product
Order Number
RealTime Interface for Multiprocessor Systems (RTIMP)
RTI_MP

RealTime Interface (p. 54)
RTI
Microtec C Compiler (p. 98) for DS1005 or
CCPPPC
GNU C Compiler (p. 98) (DS1006, DS1007, MicroLabBox)
See p. 99
For information on standard hardware and software requirements for Real-Time Interface, please see p. 58.
Hardware
Optional
Order Number
n
DS1005 PPC Board (p. 352) or
DS1005
DS1006
DS910 Gigalink Module (p. 355) or
DS910
DS911 Gigalink Module (p. 361)
DS911
DS1007
MLBX_1302F
MLBX_1302T
Optional (only for multicore n NEW: MicroLabBox with front panel

applications)
n NEW: MicroLabBox with top panel
Engineering
1)
Automatic implementation is started via

buttons: RTIMP downloads your model
to the multiprocessor system and starts
running it automatically.
2015
61
Required
Order Number
1)
Hardware
Software
Implementation Software / RTI Bypass Blockset
Real-Time Interface Bypass Blockset

ECU interfacing for rapid control prototyping and intrusive testing of existing ECU software
Highlights
n Supports rapid control prototyping (RCP) and whitebox testing of physical as well as virtual ECUs (V-ECUs)
n No need for ECU source code or build environment
n Synchronizing the execution of model-based
algorithms with ECU-internal functions and events
n Real-time read and write access to ECU internal
variables and parameters
Application Areas
The dSPACE tool chain for bypassing and ECU interfacing
consists of the RTI Bypass Blockset and the ECU Interface
Manager (see p. 226). It can be used for applications in
rapid control prototyping as well as for white-box testing
of existing ECU software.
When only some parts of an existing ECU software need to
be optimized or enhanced, bypassing is a powerful and
proven method for rapid control prototyping. It can be employed when no Simulink models of the original control
algorithms are available, or when there is no access to the
source code of ECU software. MATLAB/Simulink models
can be used to bypass and, as a consequence, replace
original ECU functions.
The dSPACE tool chain for bypassing and ECU interfacing
also makes test case development considerably easier. You
can use the tool chain to apply test stimuli in real time that
are triggered by ECU-internal events. In addition, ECU internal memory can be read and written in real time. ECU
functions can be stimulated with specific, reproducible test
data, which makes it easier to cover test cases with a complex setup. External sensors or actuators in the ECU that are
difficult to stimulate or hard to access externally can be
bypassed in order to directly stimulate the ECU functions
under test. Thus, the test coverage of ECU software can be
enhanced considerably.
62
Key Benefits
As the RTI Bypass Blockset hides ECU-specific information
on the bypass interface, control and test engineers can
completely concentrate on function design and test case
development. Based on the ECU description file (A2L file),
users can flexibly select model inputs and outputs as well
as triggers without modifying the ECU software.
A variety of ECU interfaces are supported, such as CCP, XCP
on CAN, XCP on Ethernet, XCP on FlexRay, and dedicated
ECU interfaces such as dSPACE DCI-GSIs, or DPMEM PODs.
If you use the dSPACE bypassing services (see p. 230 and
p. 231), dedicated mechanisms ensure data consistency and
safe operation.
The RTI Bypass Blockset is part of a complete tool chain
for service-based bypassing that supports different bypass
methods and different platforms for model execution:
n External bypassing on dedicated RCP systems
n Internal bypassing directly on the target ECU
n Virtual bypassing of virtual ECUs in a PC-based
simulation or on MicroAutoBox II without using a
physical target ECU at all
The RTI Bypass Blockset supports all bypass methods and
all ECU interfaces with the same intuitive look and feel. It
is easy to switch between the different bypass methods and
platforms, as no changes to the Simulink model are required.
The blockset allows developers to reuse legacy functions,
only available as C source code, in their Simulink models.
Furthermore, a powerful automation API facilitates the integration of the RTI Bypass Blockset into customer-specific
development tool chains.
2015
Introduction
Functionality
Description
Selecting ECU functions and variables
n
Flexibly mapping new Simulink models to ECU functions to trigger their execution
n
Selecting ECU variables via an integrated A2L file browser or by defining new ones via
dialogs
n
Uploading and downloading ECU variables including data vectors
Measurement and calibration
n
Real-time data acquisition and data stimulation of ECU variables including data vectors
n
Switching between bypass execution platforms without changes to the Simulink model
Application Fields
Configuration of bypass interfaces and services
n
Specifying several variable description files (A2L files) for the same bypass interface
n
Model-based configuration of bypass service and interface based on A2L files
n
Switching on/off the bypass function during run-time
Dynamic model configuration
n
Enabling and disabling service calls in the ECU code
n
Deactivating read/write access to selected ECU variables during run time without
recompiling the model

n
Changing the ECU addresses, data types and value conversion methods of variables
dynamically without modifying or recompiling the Simulink model

Interrupt configuration
Subinterrupt number assignment
External bypassing
Automation API for configuring bypass blocks via scripts

Supported ECU interfaces and
standards for external bypassing
n
XCP on CAN, XCP on Ethernet (UDP/IP), XCP on FlexRay
Software
Tool automation
n
CCP (CAN Calibration Protocol)
n
Seed & key access to ECU for XCP and CCP
n
JTAG/OCDS, JTAG/SDI, JTAG/Nexus, Nexus/READI, AUD/AUD2, NBD, H-UDI
n
Dual-port memory (DPMEM)
Supported bypass services
n
dSPACE Calibration and Bypassing Service (see p. 230)
n
dSPACE XCP Service for external bypassing via CAN, Flexray and Ethernet buses
n
Third-party XCP services for measurement and calibration
Safety
n
Configurable failure checking and double buffer mechanism
n
Configurable fall-back strategy when the connection between the RCP system and ECU
is interrupted
n
Switching calibration pages via XCP
Hardware
XCP-related options
n
XCP on CAN gateway functionality for arbitrated access to the ECU via multiple tools
Internal bypassing
Microcontroller support
Supported Microcontroller Families

n
Freescale MPC55xx, MPC56xx, and MPC57xx
n
ST Microelectronics SPC56 and SPC 57
n
Infineon Tricore incl. AURIX
n
Renesas V850 and RH850
Support of whole microcontroller families; no ECU-specific licenses required.

n
Calling ECU-internal functions from the Simulink model
dSPACE Internal Bypassing Service (see p. 231)
dSPACE Bypassing Service integrated in VEOS and MicroAutoBox II
Engineering
Virtual bypassing
n
Integrating functions that are available as C source code into the Simulink model
2015
63
Reuse of existing software

functions
External Bypassing
This bypass method is an efficient approach to developing
new software functions and optimizing existing controller
strategies. It can also be used for white-box testing of ECU
software.
The external bypass method uses a dedicated RCP system
to execute a new controller or test model, while the original
ECU runs on the target ECU, and can remain unchanged.
During the design and test phases, external bypassing allows
even complex Simulink models to be executed, since there
are almost no resource constraints such as available RAM,
ROM (flash), processor performance, or additional I/O channels. Real-time behavior is guaranteed even for complex
bypass functions. Any additional sensors and actuators that
are needed can be connected directly to the prototyping
system. dSPACE supports numerous interfaces to connect
the prototyping system to the ECU, such as CCP, XCP or
on-chip debug interfaces.
Bypassing
RCP System
New control strategy
(under development)
Y=f(X)
ECU
interface
X
Existing control strategies
ECU
White-Box Testing
dSPACE real-time system
Test function
Stimulate
Compare
ECU
interface
X
Control strategies under test
ECU
RTI Bypass Blockset with

Internal Bypass Plug-In
Bypass model
Rapid prototyping
systems
ECU
interfaces
Experiment
environment
ECU service
code
External bypass workflow
64
2015
Introduction
Internal Bypassing
Internal bypassing can be used for on-target prototyping,
i.e., rapid control prototyping on the target ECU, as well as
for white-box testing. With internal bypassing, new controller or test models can be implemented directly on the existing ECU by using its free RAM and flash memory areas.
Target code for the bypass model is generated from the
Simulink model and merged into the existing ECU image
file (HEX file). No special rapid control prototyping or test
hardware is needed. Because the new models are executed
directly on the target hardware, there are no communication
latencies to external systems, and the functions can be integrated into very fast control loops.
Application Fields
Bypass model
New control
strategy
Y=f(X)
ECU
Software
Existing control strategies
RTI Bypass Blockset

Bypass model
A2L
(with information
on bypass hooks)
HEX
(with
bypass hooks)
Measurement
and calibration tool
A2L
Hardware
HEX
(with internal
bypass function)
(with variables
related to internal
bypass function)
Flash ECU
2015
65
Engineering
Workflow with the Internal Bypass PlugIn for the RTI Bypass Blockset.
Virtual Bypassing
With dSPACE VEOS (p. 100), you can run AUTOSAR software
in a PC-based simulation as a virtual ECU (V-ECU), and
simulate it together with realistic plant models.
A V-ECU can also be deployed on MicroAutoBox II by means
of the RTI AUTOSAR Blockset (p. 82) and executed under
real-time conditions together with a physical plant.
New functions can therefore be tested and validated even
before prototypes of the target ECU become available.
Controller model
(under development)
V-ECU
The RTI Bypass Blockset supports VEOS and MicroAutoBox

II as target platforms in the same way that it supports
physical target ECUs. It allows new functions to be executed in the context of a V-ECU, synchronized to specific tasks
or runnables and with arbitrary access to the A2L variables
of the V-ECU.

Bypass model
A2L
(with information
on bypass hooks)
V-ECU
A2L
HEX
(with variables
related to internal
bypass function)
Controller model
(under development)
(with
bypass hooks)
Measurement
Plant model
HEX
(with internal
bypass function)
Virtual bypass workflow for PCbased simulation of a VECU.
66
2015
Introduction

Bypass model
Application Fields
A2L
(with information
on bypass hooks)
A2L
(with variables
related to internal
bypass function)
HEX
(with
bypass hooks)
HEX
Measurement
Software
(with internal
bypass function)
MicroAutoBox II with V-ECU
Engineering
Importing ASAM-MCD 2MC Files

An ASAM-MCD 2MC ECU description file (A2L file) can be
easily imported as a database. An intuitive variable browser
with search options and hierarchical representation of variables facilitates the handling of large description files that
contain a high number of variables. The variable names are
ally into the ECU source code, or by using the ECU Interface
Manager (p. 226). The ECU Interface Manager allows integrating the bypass into the original ECU Hex code of the
ECU software. Thus, no access to the build environment or
source code is required.
mapped to the respective addresses on the ECU. The blockset lets you access ECU variables via their names and automatically performs conversion between the ECU HEX representation and the physical representation on the dSPACE
system.
2015
67
Bypass Integration
In order to use the RTI Bypass Blockset for ECU interfacing
and bypassing purposes, a bypass service needs to be integrated into the ECU software that handles the communication and synchronization between the new controller and
test model, and the original ECU software. This can be
achieved by integrating the service and service calls manu-
Hardware
Virtual bypass workflow for MicroAutoBox IIbased realtime execution of VECU.
Implementation Software / RTI CAN Blockset
RTI CAN Blockset

For combining dSPACE systems with CAN communication networks
Highlights
n Ideal for developing and testing control functions
that communicate via a CAN bus system
n Database file import
n CAN raw data access

n One Simulink block for each functionality/
each message
68
Application Areas
The RTI CAN Blockset is an extension for Real-Time Interface
(p. 56) and can be used for combining dSPACE systems with
CAN communication networks and for configuring these
CAN networks. The RTI CAN Blockset and the RTI CAN
MultiMessage Blockset (p. 70) differ with regard to their

features and application areas (rapid control prototyping/
hardware-in-the-loop simulation).
Key Benefits
The RTI CAN Blockset is especially suited for developing and
testing control functions that communicate via a CAN bus
system. To set up a message with the RTI CAN Blockset,
simply choose the appropriate block from the CAN block
library and connect it to your Simulink model. Configuration
information such as the baud rate, identifier, message
length, and interrupts, can be entered in dialogs.
The blocksets multiple support allows simultaneous use of

several DBC files for one model, so the DBC file variants are
easier to handle and can be switched during run time. With
the blockset, CAN raw data can be acessed directly from
within Simulink. This means that, using the raw data, protocols can be created on the Simulink model level.
2015
Introduction
Implementation Software / RTI CAN Blockset
Functionality
Description
General
n
Message-oriented Simulink blockset for combining dSPACE systems with CAN communication networks and
for configuring these CAN networks

n
One Simulink block for each functionality/each message
Initialization and configuration
n
Importing database files (see below)
n
Configuring baud rate, sample mode, bit timing parameters, termination resistors, etc.
Application Fields
n
DBC file support
n
User-defined database support via custom parser
n
Multiple DBC file support allowing simultaneous use of several DBC files for one model
Signal and
message handling
n
Dialog-based setup of receive, transmit, request and remote messages (for example, format, identifier, signal
composition, and encoding/decoding)

n
Loop-back functionality: CAN messages sent by one CAN controller can be made available to the same
CAN controller
n
Gateway block to transfer messages between two CAN buses unidirectionally or bidirectionally, without message
or signal manipulation (not applicable to DS1103)

n
Displaying status information on CAN controller
n
Various options for manipulating signals and messages
n
Multiple message access: The same CAN messages can be sent and received from within different model subsystems
Software
n
Block outputs for time stamp information: receive time, transmit time, delta time, delay time
n
Different sample times and tasks for different messages (each message represented by its own block)
Signal and message handling
n
Custom encoding and decoding for the generation (TX) and verification (RX) of checksums and parity bits
n
Raw data manipulation directly from Simulink
n
User defined messages with signal representation
n
Manipulating CAN signals at model design
n
Fixed message cycle time
Interrupts
n
Supported interrupts: receive, transmit, request and remote messages, bus off
Product
Order Number
Real-Time Interface CAN Blockset
n RTICAN_BS
Hardware
Order Information

Order Number
n Real-Time Interface1) (p. 54)
n RTI
n Microtec C Compiler for DS1005 and MicroAutoBox II2) (p. 94) or
n CCPPPC
n GNU C Compiler for DS1006
n DS1006_COMP
n DS1007_COMP
n GNU C Compiler for MicroLabBox
n MLBX_COMP
n DS1005 PPC Board (p. 352)
n DS1005
n NEW: DS1007 PPC Processor Board (p. 362)
n DS1007
n DS1006 Processor Board (p. 356)
n DS1006
n DS1103 PPC Controller Board (p. 334)
n DS1103
n DS2202 HIL I/O Board (p. 382)
n DS2202
n DS2211 HIL I/O Board (p. 386)
n DS2211
n DS4302 CAN Interface Board (p. 418)
n DS4302
n MicroAutoBox II
n See p. 522
Order Number
2)
(p. 522)
n NEW: MicroLabBox2) (p. 516) with front panel
n MLBX_ 1302F
n NEW: MicroLabBox2) (p. 516) with top panel
n MLBX_ 1302T
2)
1)
2015
69
Hardware
Optional
Engineering
Software
Required
Implementation Software / RTI CAN MultiMessage Blockset

For combining dSPACE systems with CAN communication networks
Highlights
n Ideal for handling complex CAN setups,
especially in hardware-in-the-loop applications
n Convenient configuration of CAN setups
n Database file import (DBC, FIBEX, AUTOSAR)

n Managing a very high number of messages
from one Simulink block
n J1939 Add-On
n NEW: CAN FD support
n NEW: Partial networking support

70
Application Areas
The RTI CAN MultiMessage Blockset is an extension for
Real-Time Interface (RTI) (p. 54) and can be used for combining dSPACE systems with CAN communication networks
and for configuring these CAN networks. The RTI CAN
MultiMessage Blockset and the RTI CAN Blockset (p. 68)
differ with regard to their features and application
areas (rapid control prototyping/hardware-in-the-loop
simulation).
Key Benefits
The strong point of the RTI CAN MultiMessage Blockset is
handling complex CAN setups, especially in hardware-inthe-loop applications. You can control, configure, and
manipulate a very high number of CAN messages from one
single Simulink block. Not only does handling become very
straightforward, but the size of the model files is also
reduced. This cuts code generation time and build time. CAN
configurations can easily be read in from communication
matrix description files such as database container files
(DBC), ASAM-MCD2D (FIBEX), AUTOSAR System Template
files and not only CAN or J1939 formats but also the CAN
FD (Flexible Data Rate) protocol with a much higher data
rate and an extended payload data length. These functions
make the RTI CAN MultiMessage Blockset a time-efficient
and cost-efficient solution for managing complex CAN setups.
Configuration of CAN interfaces

Working with large hardware-in-the-loop (HIL) systems
means working with a considerable volume of CAN messages. Moreover, the test environments and communication
matrix (DBC, FIBEX, AUTOSAR) change frequently during
the development process. CAN configuration updates in
large models and parameter changes can be done with just
a few clicks.
Parameters and Messages

Parameters can be directly accessed in ControlDesk Next
Generation (p. 106) and AutomationDesk (p. 156) via user
trace files. The CAN Navigator is also supported for easy
handling of CAN configurations, including messages and
signal manipulation in ControlDesk. Numerous test cases
can be created via flexible manipulation on message and
signal level. The current value of the signals in messages can
be defined. Messages can be transmitted spontaneously
(kick-out) and can also be enabled. In addition, they can be
transferred directly between two CAN buses unidirectionally
or bidirectionally via the Gateway block, without message
or signal manipulation. The message transmission and signal
manipulation option can be changed during run time.
2015
Introduction
Functionality
Description
General
n
Database-file-oriented Simulink blockset for combining dSPACE systems with CAN communication networks
and for configuring these CAN networks

n
Managing a very high number of messages from one Simulink block
Application Fields
n
Supports ControlDesk Next Generation Bus Navigator (p. 134)
n
Supports dynamic changes in communication behavior such as signal manipulations and error simulation/detection
Initialization and configuration
n
Importing database files (see below)
n
Configuring baud rate, sample mode, bit timing parameters, termination resistors, etc.
n
Supports DBC, MAT, FIBEX and AUTOSAR files1)
n
User-defined database support via custom parser
n
Multiple database file support allowing simultaneous use of several database files for one model
n
Supports multiple database file variants that can be switched between during run time
n
Multiple, fast, and ECU-dependent selection of transmit and receive messages
n
Trigger reactions for sending messages as result events for a received message
n
Message composition read-only (given by database file)
n
All transmit (TX) messages are received automatically (loop-back) for transmit confirmation
Software
n
Gateway block to transfer messages between two CAN buses unidirectionally or bidirectionally, without message
or signal manipulation (not applicable to DS1103)

n
Message transfer between two CAN buses configurable during run time (gateway)
n
Direct switch from gateway signal to other sources such as counters
n
Various options for manipulating signals and messages
n
Providing all messages, signals, and status information via Simulink bus for easy access everywhere in the model
n
Block outputs for time stamp information: receive time, transmit time, delta time, delay time
scheduler to support different cycle times of messages and CAN-compliant scheduling by priority and
bus load. Automatic handling of bus load to avoid turnaround time peaks
n
Different sample times and tasks only for complete bus configurations
n
No support of remote/request messages
n
No interrupt handling (e.g., received interrupts)
Hardware
n
Internal
n
Custom CRC functionality
n
Internal parity calculation
n
Internal counter
n
Internal toggle
n
Custom Code functionality to manipulate raw data or signals
n
Raw data as input to or output from Simulink
n
Raw data manipulation from within experiment software (AutomationDesk, ControlDesk)
n
Configuration of database-independent (free) raw messages
n
Capture messages: receiving messages in a given filter range as a stream to Simulink
CAN signals from experiment software for special signal behaviors such as different counter or
signal values for a defined number of transmissions
n
Changing CAN messages during run time
n
Dynamic message triggering: global enabling, spontaneous transmission (kick-out), cyclic message activation, etc.
n
Message definitions including IDs and lengths changeable at run time
n
No interrupts supported
n
Supports trigger reactions
Interrupts
Optional: J1939 support
Engineering
n
Changing
n
J1939 support in RTI CAN MultiMessage Blockset
n
Support of J1939 Network Management (Address Claim)
n
Support of J1939 Broadcast Announce Messages (BAM)
n
Support of J1939 Request to Send/Clear to Send (RTS/CTS)
n
For more information, please contact dSPACE
Please contact dSPACE for appropriate version.
1)
2015
71
n
Support of the J1939 DBC Format
Order Information
Product
Order Number
Real-Time Interface CAN MultiMessage Blockset
n
RTICANMM_BS
Add-On: RTI CAN MultiMessage-J1939 Blockset
n
RTICANMM_J1939_BS

Software
Required
Order Number
n
Real-Time Interface1) (p. 54) or
n
RTI
n
ConfigurationDesk (p. 48)
n
CFD_I_xxx
n
Microtec C Compiler for DS1005 and MicroAutoBox II
2)
Optional
1)
2)
72
n
CCPPPC
n
DS1006_COMP
n
n
DS1007_COMP
n
n
MLBX_COMP
n
ControlDesk Next Generation with Bus Navigator Module
n
See p. 134
Hardware
Optional
(p. 522) or
n
Order Number
n
n
DS1005
n
n
DS1006
n
n
DS1007
n
n
DS1103
n
DS2202 HIL I/O Board (p. 382)
n
DS2202
n
DS2211 HIL I/O Board (p. 386)
n
DS2211
n
DS4302 CAN Interface Board (p. 418)
n
DS4302
n
NEW: DS4342 CAN FD Interface Module (p. 427)
n
DS4342
n
MicroAutoBox II2) (p. 522)
n
See p. 522
n
SCALEXIO Processing Unit (p. 304)
n
See p. 304
n NEW: MicroLabBox2) (p. 516) with front panel
n MLBX_ 1302F
n NEW: MicroLabBox
n MLBX_ 1302T
2)
(p. 516) with top panel
n
DS2671 (p. 324)
n
DS2671
n
DS2680 I/O Unit (with bus support) (p. 308)
n
DS2680_2672
2015
Implementation Software / RTI LIN MultiMessage Blockset
Introduction

For combining dSPACE systems with LIN communication networks
Application Fields
Highlights
Key Benefits
The strong point of the RTI LIN MultiMessage Blockset is
handling complex LIN setups, allowing you to control and
configure all unconditional and event-triggered LIN frames
from one single Simulink block (configuration via database
file). LIN configurations can easily be read in from communication matrix description files such as LDF, DBC, and AUTOSAR
System Template.
Hardware
Application Areas
The RTI LIN MultiMessage Blockset is an extension for RealTime Interface and can be used for combining dSPACE systems with LIN communication networks and for configuring
these LIN networks.
Software
n Convenient configuration of LIN setups

n For rapid control prototyping and hardware-in-the-loop
simulation
n Database file import (LDF, DBC, AUTOSAR)
n LIN raw data access

Functionality
Description
General
Signal initialization/configuration
n
n
n
n
n
n
Node configuration
n
n
n
n
n
n
n
1)
Importing LDF (LIN Database Files), support of LIN standard 1.3, 2.0, 2.1, 2.2
Importing AUTOSAR System Templates (*.arxml)1)
Importing database container (DBC) files
Importing FIBEX (ASAM MCD2 NET) files
Specifying baud rate, transceiver type, terminating resistors, etc.
Switching between several schedules defined in LDF file
Generating LIN schedules (list of grouped frames defined in LDF file)
Configurable LIN network serial number
Enabling/disabling automatic configuration
Manipulation option: Node enable/disable overwrites automatic configuration
Support of configured and preconfigured slave nodes
Master request and slave response frames also useable in model during automatic node configuration
Slave: Conditional change NAD Service
Slave: Read by Identifier Service
2015
73
Engineering
Databasefileoriented Simulink blockset for combining dSPACE systems with LIN communication networks and
for configuring these LIN networks
n One Simulink block per bus configuration
Functionality
Description
Frames
n Setting receive and transmit messages

n Encoding input signals from the Simulink model as raw data and transmitting the raw data to the LIN bus
n Decoding raw data and providing physical signals as outputs
n Manipulating raw data, for example, using checksums, toggling bits, inserting parity bits
n Support of event-triggered frames
n Changing frame length during run-time and dynamically
n Special run-time frame manipulation features: suppress response for n frames, corrupt LIN frame checksum for n frames
n Capturing frames not defined in LDF file or model
n Online switching between raw and signal data inputs
n Special signal generation: counter, in-data user checksum
n Energy saving modes (sleep/wake-up)
Bus events
n Sending wake-up and sleep requests

n Schedule is always restarted with first frame in schedule
n Fixed response time, manipulation of baudrate, break length, break delimiter, and LIN frame checksum
n No interrupt support
LIN slave tasks
n Classic or enhanced checksum

n Unconditional frames
n Event-triggered frames
LIN master tasks
n Sending wakeup and sleep commands

n Diagnostic frames (no diagnostic commands supported)
n Go-to-sleep without sending sleep command
Further manipulation options
n Online source switch for each signal: input, counter, constant, signal error value (for manual and automated tests)
n Enable saturation of signal-in ports
Handling characteristics
n Graphical one-for-all configuration interface

n Interface to Simulink via bus selectors
n User defined, automatically generated mapping
n Generation of Simulink input ports for non-mapped signals
n Generation of frame based ControlDesk Next Generation layouts with Bus Navigator
Order Information
74
Product
Order Number
Real-Time Interface LIN MultiMessage Blockset
n RTILINMM_BS
2015
Introduction

Order Number
n Real-Time Interface1) (p. 54) or
n RTI
n ConfigurationDesk (p. 48)
n CFD_I_xxx
n Microtec C Compiler (p. 98) for DS1005 and
n CCPPPC
Application Fields
Software
Required
MicroAutoBox II2) or
n DS1006_COMP
n DS1007_COMP
n ControlDesk Next Generation with Bus Navigator Module n See p. 134
Hardware
Optional
n DS1005
n DS1006
n DS1007
n DS4330 LIN Interface Board (p. 421)
n DS4330
n MicroAutoBox II2) (p. 522)
n See p. 522
n SCALEXIO Processing Unit (p. 304)
n See p. 304
n DS2671 (p. 324)
n DS2671
n DS2680 I/O Unit (with bus support) (p. 306)
n DS2680_2672
Hardware
For information on standard hardware and software requirements for Real-Time Interface (RTI), please see p. 54.
Engineering
2)
2015
75
1)
Order Number
Software
Optional
Implementation Software / dSPACE FlexRay Configuration Package

Configuring dSPACE systems in FlexRay networks
Highlights
n Integrating dSPACE systems as simulation or
monitoring nodes in a FlexRay network
n Efficient configuration of FlexRay simulations
n For rapid control prototyping and hardware-in-theloop simulation, including restbus simulation
n Blockset for creating application-specific
Simulink models
n Protocol data unit (PDU) support
76
Application Areas
The dSPACE FlexRay Configuration Package is used to integrate dSPACE hardware as simulation or monitoring nodes
in a FlexRay network. Nodes are configured with the dSPACE
FlexRay Configuration Tool according to a communication
matrix containing scheduling information for signals and
frames transmitted via the FlexRay bus. The communication
information is linked to a MATLAB/Simulink model via the
RTI FlexRay Configuration Blockset. The resulting FlexRay
application can be executed on a dSPACE system.
Key Benefits
The dSPACE FlexRay Configuration Package is an extensive
solution for using FlexRay in dSPACEs MicroAutoBox II or
modular systems. The package makes FlexRay configurations
easy and hides much of FlexRays complexity. Configuration
settings can be stored as project files. The number of FlexRay
controllers needed can be optimized. The dSPACE FlexRay
Configuration Package has been designed in close cooperation with advanced users of the FlexRay protocol to
ensure it meets your requirements. The package supports
two FlexRay channels.
dSPACE FlexRay Configuration Tool

The dSPACE FlexRay Configuration Tool lets you configure
a dSPACE system as a simulation node in a FlexRay network.
It relies on the network and scheduling data available in a
FIBEX or AUTOSAR XML representation. Numerous consistency checks are performed when the communication description is imported. Various views help in managing the
FlexRay configuration. The tool generates the communication code and controller configuration.
RTI FlexRay Configuration Blockset

Application-specific Simulink models can be created using
the RTI FlexRay Configuration Blockset as a basis. The block
attributes are filled with data generated by the dSPACE
FlexRay Configuration Tool. The blockset contains additional blocks that can be used for task execution control,
interrupt and error handling, status information, and
controller reset. The RTI FlexRay Configuration Blockset
supports the sending and receiving of protocol data units
(PDUs), which are also used in AUTOSAR. Such units comprise several signals, which can be handled in the model
using only one Simulink block per PDU.
2015
Introduction
dSPACE FlexRay Configuration Tool
Functionality
Description
Importing communication descriptions
1)
n
Reads communication descriptions for FlexRay and validates via plausibility checks
n
Ignores irrelevant data
n
Support of various FIBEX versions (including versions 3.x and 4.1)2)
Handling
Application Fields
n
Support of various AUTOSAR System Template versions (including versions 4.x)2)
n
Hierarchical view of the communication description
n
Visualizes parameters
n
Filter and view options, as well as search masks for handling larger descriptions
n
Generates a report for the present configuration
n
Select
Frame handling
n
Raw data access for frames with or without signals
Software
PDU handling
signals, PDUs and frames for creating blocks with the RTI FlexRay Configuration Blockset
(for use in simulation)
n
All the frames sent to a real ECU are automatically identified and configured for simulation (restbus simulation)
n
PDU update bit manipulation
n
Alive counter for PDUs
n
CRC check for PDUs by user CRC C-code file
n
Raw data access for PDUs
Signal and frame selection
n
CRC check for frames by user CRC C-code file
n
Enable/disable static frames via software: A null frame or old value (CHI Code option) is send
n
Enable/disable buffers of static slots via hardware: There is no bus activity in the slots
Task configuration
n
Generate and configure communication tasks automatically or manually and according to the selected
signals, PDUs and frames

n
Consistency checks for eliminating invalid configurations in tasks
n
Configure dSPACE hardware, including the connected FlexRay communication controllers
dSPACE tools for FlexRay rely on the existence of a communication description containing information for time-triggered message scheduling.
The information is used to configure a dSPACE hardware platform to communicate messages, using a MATLAB/Simulink model for handling
the messages.
2)
Hardware
1)
RTI FlexRay Configuration Blockset

Functionality
Description
Model generation
n
Generates MATLAB/Simulink blocks for FlexRay communication
n
Combine the model frames with application models, for example, for function prototyping or restbus simulation
n
Blocks for FlexRay controllers, tasks, and synchronization settings
n
Blocks for sending and receiving protocol data units (PDUs)
Simulation stage
n
Use a dSPACE platform as a monitoring or simulation node in a FlexRay communication system
2015
77
Engineering
n
Trigger blocks for dynamic frames
Order Information
Product
Order Number
n
FCP
FlexRay Configuration Blockset (included with dSPACE FlexRay Configuration Package)
n
RTIFLEXRAY_CONF_BS
dSPACE FlexRay Configuration Tool (included with dSPACE FlexRay Configuration Package)
n
FLEXRAY_CONF_TOOL

Software
Required
Optional
Order Number
n
Real-Time Interface
1)
(p. 54) or
n
RTI
n
n
CFD_I_xxx
n
Microtec C Compiler for DS1005 and MicroAutoBox II (p. 492)
n
CCPPPC
n
GNU C compiler for AMD OpteronTM for DS1006
n
DS1006_COMP
n
n
DS1007_COMP
n
Tools for generating a FlexRay communication matrix2)
n
ControlDesk Next Generation with Bus Navigator Module
n
See p. 134
Required
n
Interface modules with FlexRay communication controller,
n
DS4340
Optional
such as the DS4340 FlexRay Interface Module3) (p. 426)

for PHS based systems
n
DS1005 PPC Board4) (p. 352)
n
DS1005
n
DS1006 Processor Board4) (p. 356)
n
DS1006
Hardware
Order Number
n
NEW: DS1007 PPC Processor Board
4)
(p. 362)
n
DS1007
n
n
See p. 522
n
n
See p. 304
n
DS2671 (p. 324)
n
DS2671
n
DS2680 I/O Unit (with bus support) (p. 306)
n
DS2680_2672
For further information on available solutions, please contact dSPACE.
3)
For further available products and the latest version information, please contact dSPACE.
4)
With DS4505 Interface Board or the FlexRay Interface Board based on DS4501.
5)
1)
2)
78
2015
Introduction
Working with the FlexRay Configuration Package

combination with dSPACEs RTI blocksets. The models are
executed on the hardware in real time. Model execution
and bus access are synchronized. The results can be visualized in an experiment environment such as ControlDesk.
dSPACE FlexRay
Configuration Tool
Configuration
of signals, frames
and tasks for
simulation
Application Fields
Working with dSPACE Tools

dSPACE hardware systems from MicroAutoBox II to modular hardware can be used for various fields of FlexRay
applications. The systems are equipped with slots for modules containing a FlexRay communication controller. The
application models are created in MATLAB/Simulink in
RTI FlexRay
Configuration Blockset
FlexRay blockset
for modeling with
MATLAB/Simulink
Software
Generation of
Simulink
model frame
Hardware
select all the signals, frames for FIBEX 2.x and PDUs for
FIBEX 3.x and AUTOSAR you want to use in your simulation.
If you want to set up a restbus simulation for a single ECU,
just select the ECU and let the tool look up all the frames
sent to it.
Engineering
Selecting Signals, PDUs and Frames

The dSPACE FlexRay Configuration Tool is the bridge
between the network or system level view and the node- or
ECU-specific view. After a FIBEX file is imported, the FlexRay
network description and scheduling data are displayed in a
clearly arranged hierarchical view. This is combined with
additional display and sorting options, and you can easily
Simulation on
dSPACE hardware
2015
79
FIBEX file
Creating a Task Schedule

You can create a task schedule by selecting signals, frames
for FIBEX 2.x and PDUs for FIBEX 3.x and AUTOSAR. The
schedule includes communication routines for sending and
receiving FlexRay frames, for both the static and the dynamic parts of the communication cycle. It also covers application tasks for your functional or restbus simulation
models. The task schedule can be derived automatically
according to a fixed scheme for positioning communication
Code Generation
The configuration tool has been given all the information
it needs to generate the actual communication code and
the settings for initializing the FlexRay controller. The tool
also calculates the required number of FlexRay controllers,
taking into account the available communication buffers,
and startup and synchronization behavior. The code generator is prepared to support Freescale and Bosch E-Ray
controller implementations for FlexRay1).
routines. Alternatively, you have full control to define it

manually. When you do so, various checks are performed
in the background to ensure the task schedule you define
is consistent. The third and final category of tasks covers
the synchronization task. This is executed at the end of each
application cycle to align task execution to the global time
on the FlexRay bus.
Creating the FlexRay Model

You can now take the results of the configuration tool,
which acts as a kind of preprocessor tool, and continue with
the usual model-based design flow. When a FlexRay model
is created for the first time, blocks from the RTI FlexRay
Configuration Blockset library are copied to the model and
their parameter values are set automatically according to
the configuration data that was generated previously. The
resulting model frame represents a complete interface to
the FlexRay network and a local task schedule. It can be
supplemented by the actual functional or restbus simulation
models and further blocks from the library, for example, for
receiving status information and handling error situations.
For more information on supported controllers, please contact dSPACE.
1)
80
2015
Introduction
Application Fields
n Alive counter manipulation via TRC file

n Change CRC algorithms at run time
n Send and receive invalid signals
n Simulate synchronization service breakdown
n Simulate time-triggered task execution breakdown
with optional restart at correct synchronization
2015
81
Engineering
Hardware
Selected Failure Simulation Methods

n Failure and restart of a FlexRay controller
n Enable/disable transmission of a static frame
n Enable/disable transmission of a cyclic dynamic
FlexRay frame
n Enable/disable all event-based dynamic FlexRay frames
n Enable/disable all cyclic FlexRay frames
(a null frame or old value is sent)
dSPACE hardware system. The driver and initialization code

of the configuration tool is integrated during this build
process. The generated code is downloaded to the dSPACE
hardware and acts as a full-fledged node in the FlexRay
network, sending and receiving FlexRay frames in real time.
Software
Modifying the Model

Later on, you will most likely face modifications to the communication description file, representing new integration
stages in the vehicle project. To preserve the modeling results
already obtained, the RTI FlexRay Configuration Blockset
comes with an update mechanism for handling changes in
the configuration data, for example, introducing new signal
and frame blocks and discarding old ones. The resulting
FlexRay application model is compiled for execution on a
Implementation Software / RTI AUTOSAR Blockset

MATLAB/Simulink- and AUTOSAR-based co-development,
validation and prototyping on MicroAutoBox II
Highlights
n Combination of AUTOSAR software development
and model-based controller design in MATLAB/
Simulink
n Support of virtual ECUs (V-ECUs) for software
validation and rapid control prototyping
n Dedicated AUTOSAR operating system (OS) with
a comprehensive feature set
n Seamless workflow from offline simulation to rapid
control prototyping to production software
development for target ECUs
Application Areas
The RTI AUTOSAR Blockset is an extension to Real-Time
Interface (RTI) with a focus on rapid control prototyping,
and ECU software testing and validation.
You can use it to execute AUTOSAR software, from individual AUTOSAR SWCs to entire virtual AUTOSAR ECUs, on
dSPACEs compact, in-vehicle-capable real-time system MicroAutoBox II. These are some typical application scenarios
for the blockset:
n Prototyping and evaluating new Simulink control
algorithms that include existing AUTOSAR software
components (SWCs)
n Benchmarking new AUTOSAR SWCs on a standardized reference hardware
n Testing and validating AUTOSAR software under realtime conditions before the target ECU becomes
available
n Testing and validating AUTOSAR software together
with the physical plant, in the laboratory or in the
vehicle
82
Key Benefits
The RTI AUTOSAR Blockset lets you import AUTOSAR
software from SystemDesk into MATLAB/Simulink in the
form of virtual ECUs (V-ECUs) and use it on MicroAutoBox II.
V-ECUs are realistic representations of future ECU software.
By using the RTI I/O libraries, the V-ECU can use the powerful and flexible I/O of MicroAutoBox II. The model-based
configuration of the I/O blocks makes setting up a V-ECU
with physical I/Os quick and easy. Because of its comprehensive I/O range, the same MicroAutoBox II can be
equipped with different V-ECUs to stand in for a multitude
of AUTOSAR ECUs.
The RTI AUTOSAR Blockset brings with it a dedicated
AUTOSAR OS for MicroAutoBox II. This OS supports AUTOSAR versions 3.x and 4.x. It conforms to AUTOSAR OS
Scalability Class 1, ensuring a high level of compatibility.
By supporting advanced OS concepts, such as extended
tasks, the OS enables a powerful real-time execution of
AUTOSAR software that closely resembles the behavior of
production-grade target ECUs. The OS lets you test realtime aspects of the software even before prototypes of a
target ECU become available.
2015
Introduction
Functionality
Description
AUTOSAR OS on MicroAutoBox II
n
Realtimecapable, preemptive AUTOSAR OS
n
Automatic configuration of OS and BSW services
Application Fields
n
Conforms to AUTOSAR Scalability Class 1 and comprises:
n
Full OSEK OS conformance (all conformance classes)
n
Support of all OSEK APIs
n
AUTOSAR Counter Interface
n
AUTOSAR Software Free Running Timer Interface (SWFRT)
n
AUTOSAR Schedule Tables
n
AUTOSAR Stack Monitoring
n
Synchronized measurement of Simulink signals and global VECU variables in parallel
n
Standard ASAM A2L file support
n
Extended measurement, calibration and debugging possibilities compared to RTEs on productiongrade
target ECUs to allow tracking RTE communication

Basis Software (BSW) Services
n
ECU State Manager (EcuM)
Software
n
NV RAM Manager (NvM)
n
AUTOSAR CAN stack
Supported AUTOSAR versions
n
Versions 3.1, 3.2
n
Versions 4.0.3 , 4.1.1, 4.1.2
Support for bypassing1)
The RTI AUTOSAR Blockset prepares imported VECUs for virtual bypassing on MicroAutoBox II.
Planned for 2015
AUTOSAR SWCs
SystemDesk
New RTI AUTOSAR Blockset
Hardware
such as digital or analog input and output ports with production tools is often a very complex and error-prone task.
The model-based I/O configuration with the dSPACE RTI I/O
blocksets makes setting up a V-ECU with physical I/Os quick
and easy. Its comprehensive range of I/O lets you adapt
MicroAutoBox II to a wide range of ECUs.
In combination with the RTI AUTOSAR Blockset, MicroAutoBox II can therefore flexibly stand in for a multitude of
different AUTOSAR ECUs long before physical prototypes
of an ECU become available.
Engineering
Working with AUTOSAR on MicroAutoBox II

The RTI AUTOSAR Blockset lets you import AUTOSAR software from SystemDesk into MATLAB/Simulink in the form
of virtual ECUs (V-ECUs) and use it on MicroAutoBox II.
V-ECUs comprise AUTOSAR application software, the AUTOSAR Runtime Environment (RTE), AUTOSAR Basic Software (BSW) and OS configurations.
The RTI AUTOSAR Blockset automatically configures the
AUTOSAR OS and the BSW services on MicroAutoBox II
according to the configuration settings. For instance, the
AUTOSAR CAN stack is configured automatically based on
the configuration you made in SystemDesk. Configuring I/O
MicroAutoBox II
XML
.c
.h
V-ECU
2015
83
1)
A Seamless Development Tool Chain

dSPACE offers a seamless tool chain for working with
AUTOSAR software. This tool chain consists of the dSPACE
tools TargetLink, SystemDesk, VEOS, and the RTI AUTOSAR Blockset for MicroAutoBox II.
AUTOSAR SWCs are the building blocks of AUTOSAR software and can be developed in various ways. They can, for
instance, be created manually as C source code. Or they
can be developed with a model-based production code
generator such as dSPACE TargetLink.
With SystemDesk, SWCs can be imported and combined
into an AUTOSAR application software. In addition, SystemDesk lets you model entire software architectures, configure
the corresponding AUTOSAR OS and BSW services, generate an RTE and export them as V-ECUs.
Such V-ECUs can be run and tested on a PC in the simulator dSPACE VEOS to validate functional properties of the
software. The same V-ECU can also be executed without
modifications on MicroAutoBox II by using the RTI AUTOSAR
AUTOSAR SWCs
Blockset. Real-time-specific parts of the software behavior

can thus be tested and the V-ECU can be validated under
realistic operating conditions. With this approach, the behavior of AUTOSAR software can be prototyped together
with a physical plant in the laboratory, and experienced
directly in the vehicle.
In order to optimize or enhance certain aspects of a V-ECU,
the RTI Bypass Blockset allows individual functions and runnables to be replaced with new Simulink models. Hence,
you can evaluate and test the behavior of the new models
in combination with the existing ECU software.
This tool chain covers all phases of function and software
development, from control design to software architecture
definition and integration, from offline simulation to invehicle RCP. The continuous use of ControlDesk Next Generation leverages synergies, because the same measurement and calibration data and experiment layouts can be
used across all platforms, and even in the production ECU.
SystemDesk
XML
.c
.h
V-ECU
TargetLink/
Simulink
Function Design
84
VEOS
PC-based
Simulation
MicroAutoBox II with
RTI AUTOSAR Blockset
Rapid Control
Prototyping
Production ECU &

basic software tools
Production
Software Integration
2015
Introduction
Product
Order Number
n RTI_AUTOSAR_VECU_BS
Application Fields
Order Information
Optional
n
Real-Time Interface
n
RTI
n
RTI XCP on Ethernet Blockset
n
RTIETHXCP_BS
n
RTI Bypass Blockset
n
SystemDesk
See p. 40
n
VEOS
See p. 100
n
TargetLink
See p. 180
n
See p. 106
n
RTI CAN Blockset
n
RTICAN_BS
n
See p. 70
n
n
RTILINMM_BS
n
n
FCP
n
Ethernet Blocksets
See p. 88
Hardware
Order Number
See p. 522
Hardware
n
MicroAutoBox II
Engineering
Required
RTIBYPASS_BS
2015
85
Required
Order Number
Software
Software
Implementation Software / RTI FPGA Programming Blockset

Integrating FPGA models in dSPACE systems
Highlights
n Easy connection of FPGA models to
processor models (Simulink, RTI)
n Model-based I/O configuration
n Offline simulation in Simulink
n Supports various dSPACE FPGA platforms
Application Areas
The RTI FPGA Programming Blockset is a Simulink blockset
for using an FPGA model created with the Xilinx System
Generator blockset with a dSPACE system. It provides RTI
blocks for implementing the interface between the FPGA
mounted on a dSPACE board and its I/O, and the interface
between the dSPACE FPGA board and its processor board.
The blockset can be used with the following dSPACE
FPGA platforms, which provide user-programmable FPGAs:
n

DS5203 FPGA Board (p. 438).
n

DS2655 FPGA Base Board (p. 311).
n MicroAutoBox II 1401/1511/1512 and 1401/1512/1513
(p. 522) extended with a DS1552 Multi I/O Module.
n NEW: MicroLabBox (p. 516).
Typical application scenarios for rapid control prototyping
(RCP) and hardware-in-the-loop (HIL) simulation are:
n Projects in automotives, industrial automation,
medical engineering, and aviation
n Signal preprocessing, adapting new interfaces,
very fast control loops, designing and testing
new concepts for electrified powertrains
Key Benefits
The dSPACE FPGA platforms provide a Xilinx FPGA, for which
you can implement an application graphically using the Xilinx
System Generator in Simulink. The RTI FPGA Programming
Blockset allows you to integrate the resulting FPGA model in
a Simulink model that runs on dSPACE hardware. The RTI
FPGA Programming Blockset is a convenient way to connect
the I/O boards I/O driver components and to model the
connection to a processor-based computation node (DS1005
or DS1006 processor boards or MicroAutoBox II). The data
exchange supports fixed point data types as well as floating
point data types. Thus, FPGA programming is seamlessly
integrated into the Simulink environment. With the FPGA
blockset, you can synthesize, build and program the FPGA
or processor directly from Simulink for optimal convenience.
Alternatively, the handcode interface lets you program
the FPGA boards in VHDL (VHSIC Hardware Description
Language) or Verilog.
Two worlds integrated: FPGA model components created with

the Xilinx System Generator blockset and RTI blocks.
86
2015
Introduction
Implementation Software / RTI FPGA Programming Blockset
Functionality
Description
General
n
Integrating an FPGA model on a dSPACE FPGA platform
n
I/O configuration
Application Fields
n
Automatic generation of a processor model template on the basis of a FPGA application
FPGA interface
n
Programming the FPGA with the Xilinx System Generator
n
Integrating an FPGA model created with the Xilinx System Generator
n
Offline simulation in Simulink
Handcode interface
n
Programming the FPGA in VHDL or Verilog
I/O access
n
Connecting the FPGA model with analog and digital input and output signals with the RTI FPGA Blockset
Processor-FPGA communication
n
Connecting the FPGA model with the processor model running on the computation node
(DS1005, DS1006 or DS1007, SCLX_RTPC, MicroLabBox or MicroAutoBox II)

types for system bus communication with the dSPACE FPGA platforms:
register, register groups, buffer
n Implementing interrupt-driven tasks in the processor model triggered from the FPGA model.
n
Access
Software
Asynchronous tasks
Order Information
Product
Order Number
RTI FPGA Programming Blockset FPGA Interface or
n RTIFPGA_BS
RTI FPGA Programming Blockset Handcode Interface
n RTIFPGA_HC
Software
Required
Hardware

Order Number
n
Real-Time Interface
1)
(p. 54)
n
RTI
n
ConfigurationDesk (for SCALEXIO)
n
See p. 48
n
Xilinx ISE / Vivado Design Suite2)
Please see www.xilinx.com

n
CCPPPC
n
n
DS1006_COMP
n
n
DS1007_COMP
n
n
MLBX_COMP
n
DS5203 FPGA Board (SX95) or
n
DS5203_SX95
n
DS5203 FPGA Board (LX50) (p. 438)
n
DS5203_LX50
n
DS1005 PPC Board (p. 352) or
n
DS1005
n
n
DS1006
n
n
DS1007
n
DS2655 FPGA Base Board (p. 311)
n
DS2655
n
n
SCLX_RTPC
n
MicroAutoBox II 1401/1511/1512 and 1401/1512/1513 (pp. 522-525)
n
See p. 496
n
DS1552 Multi I/O Module for MicroAutoBox II (p. 522)
n
DS1552
n
NEW: MicroLabBox with front panel (p. 516)
n
MLBX_ 1302F
n
NEW: MicroLabBox with top panel (p. 516)
n
MLBX_ 1302T
Hardware
Optional
Order Number
Please note that due to the introduction of the Vivado software, Xilinx will no longer support the Xilinx System Generator for
DSPs in combination with the ISE Design Suite after MathWorks MATLAB and Simulink Release R2013b.
For information on standard hardware and software requirements for Xilinx products, please see www.xilinx.com
1)
2)
2015
87
n
Microtec C Compiler for DS1005 (p. 98) and MicroAutoBox (p. 522)
Engineering
n
Xilinx System Generator for DSP2) only for FPGA Interface version (RTIFPGA_BS)
Implementation Software / Ethernet Blocksets
Ethernet Blocksets
Overview of Ethernet implementation software
Highlights
n Connection of dSPACE real-time systems to
Ethernet networks and devices
n Convenient configuration of Ethernet setups
n For rapid control prototyping (RCP) and
hardware-in-the-loop (HIL) simulation
Application Areas
Ethernet is an integral part of various dSPACE applications
and solutions, where it is used for communication between
dSPACE systems and other systems, or for co-simulation
coupling, etc. It can also be used as a vehicle network or
bypassing interface.
dSPACE Ethernet implementation software allows customers to efficiently integrate Ethernet functions into a wide
range of applications.
88
Key Benefits
Ethernet is a long-established networking technology for the
most diverse applications that was first used for networking
local computers. Since its beginnings, the technology has
evolved and now offers great features such as flexibility,
efficient pricing, and accumulated know-how. As an ISO
Open Systems Interconnection (OSI) model, Ethernet can be
tailored to many different applications, allowing it to enter
more fields, such as industrial automation. Today, it is even
being used in the vehicle.
dSPACE Ethernet implementation software offers an easyto-use graphical user interface and application-tailored
solutions.
2015
Introduction
Supported dSPACE
platforms
NEW: RTI Ethernet Blockset
RTI Ethernet (UDP) Blockset
Ethernet Configuration Package
n DS1007 PPC Processor Board (p. 362)
n MicroAutoBox (p. 522)
n MicroLabBox (p. 516)
Application Fields

n DS1007 PPC Processor Board (p. 362)
Purpose
Supported dSPACE
platforms
Additionaly required
hardware
n LVDS_CAB13/14
n DS921
n DS4121, LVDS_CAB14
Connects DS1007 and MicroLabBox to

Ethernet devices.
Supports bypassing applications with
DS1007-based real-time systems.
Connects dSPACE real-time systems to

Ethernet devices and networks.
Suitable for bypassing.
Supports automotive middleware

SOME/IP.
Connects DS1006-based dSPACE realtime systems to Ethernet devices and
networks.
NEW: SCALEXIO Ethernet Solution
DS1006QC Ethernet Solution
DS4504 Ethernet Solution
Uses the second SCALEXIO Processing

Units (p. 304) Ethernet interface.
Optional: additional 2-Port Ethernet
Package.
n DS921
n DS4504, DS4504_ETX, DS381
Connects DS1006-based modular

dSPACE real-time systems to Ethernet
devices and networks.
Connects modular dSPACE real-time

systems to Ethernet devices and
networks.
Engineering
Hardware
Connects SCALEXIO-based dSPACE

real-time systems to Ethernet devices
and networks.
2015
89
Purpose
Software
Additionaly required
hardware
Technical Features
RTI Ethernet Blockset
Ethernet Configuration Package
Ethernet standard
10/100/1000 Mb/s
100/1000 Mb/s
(MABX II);
10/100 Mbit/s (DS4121, LVDS_CAB14)
10/100/1000 Mb/s
Protocols
UDP/IP, TCP/IP
UDP/IP
UDP/IP
Maximum number of sockets 256

Supported middleware
SOME/IP
IP fragmentation
Yes
No
Maximum payload of UDP

datagram
Operation modes
65507 bytes
1472 bytes
Full duplex/half duplex
Full duplex
Auto-MDIX
Yes
Yes
DHCP client
Yes
No
Dynamic change of
destination address
Yes (UDP/IP)
No
Receive/transmit queue
Yes/Yes
Yes/Yes
Send broadcast messages
Yes
No
Technical Features
SCALEXIO Ethernet Solution
DS4504 Ethernet Solution
Ethernet standard
10/100/1000 Mb/s
10/100/1000 Mb/s
10/100 Mb/s
UDP/IP, TCP/IP
96 receive, 96 transmit
UDP/IP, TCP/IP
Protocols
UDP/IP, TCP/IP
Maximum number of sockets 65535
Supported middleware
90
IP fragmentation
Yes
Yes
Yes
Maximum payload of UDP

datagram
65507 bytes (UDP/IP)
65507 bytes
65507 bytes
Operation modes
Auto-MDIX
Yes
Yes
No
DHCP client
Yes
Yes
Yes
Dynamic change of
destination address
Yes (UDP/IP, TCP/IP)
Receive/transmit queue
Yes/Yes
Yes/No
Yes/No
Send broadcast messages
Yes
Yes
Yes
2015
Introduction
Product
Order Number
n RTI_ETH/UDP_BS
DS4504 ETH Solution
n DS4504_ETH_SOL
n DS1006QC_ETH_SOL
dSPACE Ethernet Configuration Package
n ECP
n RTI_ETH_BS
SCALEXIO Ethernet Solution
n SCLX_ETH_SOL
Application Fields
Order Information
2015
91
Engineering
Hardware
Software
For information about our 10 Mb/s Ethernet Interface

please see p. 475.
Implementation Software / ADASIS v2 HR Blockset
ADASIS v2 Horizon Reconstructor Blockset

Developing and testing mapbased driver assistance systems using the ADASIS v2 protocol
Highlights
n Simulink blockset for accessing electronic horizon
data via the ADASIS v2 protocol
n Graphical selection of predictive road data for
easier development of map-based driver assistance
functions
n Ready-to-use model blocks for road profiles,
intersections, stubs, and protocol metadata
n Same reconstructor code as for production ECUs
from Elektrobit
Application Areas
Advanced driver assistance systems (ADAS) such as predictive powertrain control, curve lights and curve warnings use
predictive road data, called the electronic horizon, which
is calculated from digital road maps and from the vehicles
current position and driving direction.
To facilitate the development and implementation of such
driver assistance systems, the ADASIS Forum (www.ertico.
com/adasisforum) specified the ADASIS v2 standard for the
transmission of electronic horizon data. The ADASIS v2
Horizon Reconstructor Blockset lets you access the electronic horizon data from within a Simulink model, so you
can use it during function development without having to
implement the protocol yourself.
92
Key Benefits
Using the ADASIS v2 Horizon Reconstructor Blockset together with the dSPACE PC-based simulation platform
VEOS, the MicroAutoBox or AutoBox rapid prototyping
system, you can develop driver assistance systems in short
iteration cycles and directly experience their effects on a PC
or in the real vehicle.
Only a few mouse clicks are needed to select the predictive
road data, connect it to the driver assistance function in
the model, and generate the code and load it to the
development system. So function developers can give their
full attention to implementing the actual ADAS application
without the time-consuming task of implementing the
ADASIS v2 protocol themselves.
The ADASIS v2 Horizon Reconstructor Blockset is based on
the ADASIS v2 reconstructor code for production ECUs from
Elektrobit. By means of this the transition from prototyping
to target ECU implementation is facilitated.
2015
Introduction
Implementation Software / ADASIS v2 HR Blockset
Functionality
Description
General
n
Access to the electronic horizon data from within a Simulink model (e.g., to road curvature, slope
and speed limit information)
Application Fields
n
Graphical selection of predictive road data for connection to the actual driver assistance functions in
the Simulink model

n
Independent of the transmisson medium; can be combined with CAN or Ethernet blocksets
n
Dedicated blocks for road profiles, intersections, stubs, and protocol metadata
n
ADASIS v2 reconstructor code for target ECUs from Elektrobit
Order Information
Order Number
ADASIS v2 Horizon Reconstructor Blockset
n ADASISV2HR_BS
Software
Product

Software
Order Number
n
Real-Time Interface1) (p. 56)
n
RTI
n
dSPACE VEOS
See p. 96
Hardware
Optional
Order Number
n
n
DS1005
n
n
DS1006
n
n
DS1007
n
MicroAutoBox II2)
See p. 522
n
SCALEXIO
(p. 522)
Hardware
Optional
See p. 296
2)
Various MicroAutoBox variants are available.
2015
93
Engineering
1)
Implementation Software / XSG Utils Library
XSG Utils Library

Readytouse function blocks for faster implementation of FPGA models
Highlights
n Completely open models for Simulink and
Xilinx System Generator (XSG)
n Real-time FPGA programming
n Wide range of function blocks
n For rapid control prototyping or hardware-in-the-loop
(HIL) simulation projects
Application Areas
The XSG Utils Library offers users of real-time FPGA applications enhanced function blocks for implementing their own
projects. The library is completely open and can be used in
the following applications:
n Rapid control prototyping projects using dSPACE
MicroAutoBox II (p. 522) or DS5203 FPGA Board (p. 438)
n Hardware-in-the-loop (HIL) simulation with the DS5203
FPGA Board (p. 438) used in a dSPACE Simulator or with
the DS2655 FPGA Base Board (p. 311) for SCALEXIO
dSPACE offers a variable license model:
n XSG Utils Library for developers of FPGA and processor
applications
n XSG Utils Interface Library for users to embed pre-configured FPGA applications into existing Simulink models
Available Function Blocks

n Scope
n PWM Measurement
n PWM Generator
n Look-up Table
n I/O Access Functions
n Integrator
n PI Controller
n Average Calculator
94
Key Benefits
The XSG Utils Library contains essential, often needed function
blocks for FPGA programming, similar to standard Simulink
functions. The high-quality function blocks are ready-to-use
and easy to adapt to your project, so they greatly facilitate
your FPGA programming. They range from enhanced I/O,
scope, and look-up table functions to an average calculator,
sine generator and wavetable encoder.
So that you can buy just the function set you need for your
own FPGA application, dSPACE offers the XSG Utils Library
as a subset of the functions in the XSG Electric Components
Library (p. 249) or XSG ACMC Library (p. 96). Different versions of all these libraries are available for developers and
for users of FPGA applications.
The XSG Utils Library offers pre-built custom instruments
that enable a quick access to the most used functions out
of ControlDesk Next Generation (p. 106).
n Sine Generator
n Discrete PT1
n Scaling
n Wavetable Encoder
n APU
n Small Apps
n Version Info
2015
Introduction
Implementation Software / XSG Utils Library
Functionality
Description
Scope
Captures 8 (out of a selection of 16) high-frequency signals within the FPGA clock rate and sends the captured data
synchronously to the processor, where it can be displayed and stored, for example, in ControlDesk XY plotters.
PWM Measurement
Measures the dead time (between HSD and LSD), high time and period time of a single- or three-phase signal.
PWM Generator
Generates a pulse-center-aligned PWM signal (single-phase and three-phase). The dead time and the duty cycle can
be set on the processor side (online tunable).
Look-up Table
Configures the accuracy of the normed table, and the minimum and maximum data values to cover, and specifies the
amount of bits to be calculated automatically. Linear interpolation algorithms or the Use Input Below method can be
configured online: 1-D, 2-D and 3-D look-up tables are available.
I/O Access Functions
Enables flexible programming and run-time parameterization of the onboard FPGA I/O as well as the stimulus mode.
Application Fields
Technical Details of the Main Functions
Product
Order Number
XSG Utils Interface Library
n FPGA_XSG_UTILS_IF
XSG Utils Library (includes XSG Utils Interface Library)
n FPGA_XSG_UTILS
XSG Electric Components Interface Library including XSG Utils Interface Library
n FPGA_XSG_EC_IF
XSG Electric Components Library including XSG Utils Library and XSG Electric Interface Components Library (p. 249)
n FPGA_XSG_EC
XSG AC Motor Control Interface Library including XSG Utils Interface Library
n FPGA_XSG_ACMC_IF
XSG AC Motor Control Library including XSG Utils Library and XSG ACMC Interface Library (p. 96)
n FPGA_XSG_ACMC
Software
Order Information
See p. 54
ConfigurationDesk for use with DS2655
See p. 48
See p. 86
Xilinx ISE FoundationTM 1)
Please see www.xilinx.com
See p. 106
DS5203 FPGA Board
See p. 438
DS2655 FPGA Base Board
See p. 311
MicroAutoBox II with I/O extensions for Simulink-programmable FPGA
See p. 522
Hardware
Optional
Order Number
Please note that due to the introduction of the Vivado software, Xilinx no longer supports the Xilinx System Generator for DSPs
in combination with the ISE Design Suite after MathWorks MATLAB and Simulink Release R2013b.
Engineering
Optional
Real-Time Interface depending on the target
1)
2015
95
Required
Order Number
Hardware
Software
Implementation Software / XSG AC Motor Control Library
XSG AC Motor Control Library

FPGAbased control design for MicroAutoBox II, SCALEXIO and PHSbased systems
Highlights
n
FPGA library for high-speed electric drive control
n
High performance position sensor processing
n
Flexible PWM generation
n
Connection of diverse position encoders
n
Examples of controller models for various AC motors
Key Benefits
The XSG AC Motor Control library is used for high-performance e-drive control with sample rates above 50 kHz by
performing custom control algorithms or parts of it on an
FPGA. FPGA library components can be combined freely (e.g.
encoder interfaces and PWM) on various FPGA platforms
with different I/O modules and can also be connected to
custom design components.
Purpose
The XSG AC Motor Control library lets you program inside
the FPGA. This mainly involves the high-performance processing of various position sensors and in conjunction with the
included XSG Utils library (p. 94), the flexible generation
of PWM patterns. You can use the RTI FPGA Programming
Blockset (p. 86) to position and combine these components
however required.
Features
n
All library components are open and accessible to users
n
SSI (synchronous serial interface) encoder processing
n Incremental encoder processing (TTL or sine)
n Flexible PWM generation (using included XSG Utils library)
n
Hall sensor processing
n
Small applications and components for control
n
Resolver and LVDT processing
n
Examples of controller models for various AC motors
Supported Hardware
System
Platform
PHSbased system
DS5203 (SX95/LX50)
DS5203 (SX95/LX50) with DS5203M1
DS1512 with DS1552
DS1512 with DS1553
DS2655 with DS2655M1
MicroAutoBox II
SCALEXIO
+
u d*
i d* = 0A
id
u b*
Product
Order Number
XSG ACMC Interface Library including

XSG Utils Interface Library
FPGA_XSG_ACMC_IF
XSG ACMC Library including XSG Utils Library

and XSG ACMC Interface Library
FPGA_XSG_ACMC
q-current ctrl
u q*
i q*
n*
u a*
d,q
speed ctrl
Order Information
96
KINTEX
d-current ctrl
iq
a,b,c
u c*
ia
d,q
ib
a,b,c
ic
2015
Implementation Software / Power RealTime Library
Introduction
NEW: Power RealTime Library

Easy real-time simulation of power electronics circuits developed with SimPowerSystems
Application Fields
Highlights
n
Real-time simulation of SimPowerSystems circuits for
the HIL simulation of power electronics

n
Automatic real-time code generation for dSPACE
Purpose
The library provides mean value models for power electronics
bridge circuits. These models precisely emulate the switching of power semiconductor devices. The simulation speed
is increased by pre-calculation of model states and model
separation for the distribution across several computational
nodes. Library functions for the easy integration of models
in asynchronous rasters help to avoid interference effects.
Hardware
Key Benefits
The dSPACE Power RealTime Library can be used for the realtime calculation of electrical models developed in SimPower
Systems. The blockset provides different ways for modifying
a SimPowerSystems model to allow real-time-capable code
generation on dSPACE real-time processors by means of
Simulink Coder.
Software
real-time processors
n
Optimized interfaces for dSPACE I/O boards
Features
linear parts and slow switching semiconductors, such as
rectifiers.
n Mean value models can be used for fast switching semiconductors and connected to dSPACE I/O channels for
PWM measurement, such as with the DS5202 FPGA Base
Board with EMH Solution, or the DS2655 in combination
with the XSG Utils Library.

n
SimPowerSystems can be used in separate triggered
tasks (task handling).
n
Support of model separation (model splitting)
n
Pre-computation of switch-configuration-dependent
matrices (mode caching)
n
Model analysis tools for enhanced usability
Engineering
n Standard SimPowerSystems components can be used for
Required
Optional
Order Number
Real-Time Interface depending on the target
ConfigurationDesk for use with DS2655
XSG Utils Library
Hardware
Required
Optional
See p. 54
See p. 48
See p. 106
See p. 94
Order Number
DS1006 Processor Board

DS5203 FPGA Board
EMH Solution
n DS1006
n SCLX_RTPC
See p. 438
See p. 311
See p. 464
2015
97
Software
Implementation Software / Compilers
Compilers
For translating C code into object code
Highlights
n New: Support of C++
n Support of ANSI standard C
n Including shell programs for single-step compiling,
assembling, and linking
n Automatic invocation during code generation
process when used with Real-Time Interface (RTI)
Overview
Compilers
Features
dSPACE Products
Microtec PowerPCC Compiler
n
Generates executable object code for PowerPC processors
n
DS1103 (p. 334)
n
Sophisticated optimization pass for efficient, compact object code
n
DS1104 (p. 340)
n
Assembler and linker included
n
DS1005 (p. 352)
n
Run-time libraries included
n
n
Generates executable object code for TIs C31 and VC33 DSPs
n
DS2211 (p. 386)
n
n
DS2302 (p. 392)
Texas Instruments TMS320

Optimizing C Compiler
n
n
GNU C Compiler
n
Generates executable object code for x86 processors
n
DS1006 (p. 356)
n
n
DS1007 (p. 362)
n
n
MicroLabBox (p. 516)
n
1)
98
2015
Introduction
Implementation Software / Compilers
Order Number
n
CCPPPC
Texas Instruments C3X/4X Code Composer
n
TMDS3240130
n
DS1006_COMP
n
DS1007_COMP
n
MLBX_COMP
2015
99
Engineering
Hardware
Software
Product
Microtec PowerPC C Compiler
Application Fields
Order Information
Simulation Software / VEOS
VEOS
Platform for PCbased simulation
Highlights
n Early validation of ECU software by PC-based
simulation
n Comprehensive, realistic simulation of ECU
network communication for CAN and LIN buses
n Seamless integration with RCP and HIL tool chains
n Openness through support of automotive standards
n NEW: Support of Functional Mock-up Interface
n NEW: Support of multi-model scenarios
Application Areas
dSPACE VEOS is a PC-based simulation platform that promotes the use of virtual validation in the development of
electronic control units (ECUs). VEOS makes it possible to
simulate a wide range of different models function models,
Functional Mock-up Units (FMUs), virtual ECUs (V-ECUs), and
vehicle models independently of any specific simulation
hardware in early development stages.
For multi-model scenarios VEOS supports importing, connecting and running any number of functions and plant
models based on Simulink or Functional Mock-up Interface
(FMI) 2.0 thereby extending the scope of your applications.
Systematic Extension to the dSPACE Tool Chain

VEOS works hand in hand with other dSPACE products to
provide a complete tool chain for the development and
testing process. This means that tools and models which
are commonly used in rapid control prototyping and HIL
simulation can also be used in the virtual world. Similarly,
layouts from HIL simulation can be reused in PC-based simulation with VEOS and vice versa. VEOS also provides open
interfaces for you to connect and utilize your existing tools.
n Simulink and dSPACE Target for Offline Simulation for
generating C-code-based simulations
100
Key Benefits
Running on a standard PC, VEOS gives function developers,
software architects and ECU testers numerous new options
for virtual validation in an early project phase.
n New functions can be integrated with the overall ECU
software to test how they interact.
n A virtual test bench with powerful engine and vehicle
dynamics models is permanently available for designing
complex controller strategies.
n Complex vehicle and environment models can be integrated with virtual ECUs to simulate and test an entire
virtual vehicle.
n In preparation for hardware-in-the-loop simulation, models and tests can be created, set up and run on a PC
independently of the hardware-in-the-loop (HIL) system.
n TargetLink (p. 180) for generating AUTOSAR and nonAUTOSAR simulations based on production code
n SystemDesk (p. 40) for generating virtual ECUs
n Automotive Simulation Models (p. 236) for complex
environment models
n ModelDesk (p. 261) for graphically configuring and
parameterizing environment models
n ControlDesk Next Generation (p. 106) for experimenting
and visualizing simulations
n MotionDesk (p. 140) for visualizing simulation scenarios
n AutomationDesk (p. 156) for creating tests and automating simulation runs
2015
Introduction
Functionality
Description
PC-based simulation
n Simulation of different models, from function models to virtual ECUs, bus systems, and vehicle models
n No additional hardware needed for simulation
Simulink support
n Simulation
of Simulink function models and Simulink environment models (such as dSPACE ASMs)
of S-functions, model referencing, multitasking, triggered or enabled subsystems and tunable
parameters
n Support
n Simulation of TargetLink-generated code used in virtual ECUs (V-ECUs)
Application Fields
TargetLink support
n Support for AUTOSAR as well as non-AUTOSAR TargetLink code
AUTOSAR support
n Simulation
of virtual ECUs which are generated by SystemDesk

of realistic AUTOSAR operating systems
n Support of AUTOSAR basic software modules, such as DEM, NVRAM or ECU state manager
n Support of AUTOSAR R3.0, R3.1, R3.2, and R4
n Support
n Simulation of ECU network communication on CAN and LIN buses, including messages, scheduling and arbitration
n Idealized
bus simulation for FlexRay
HIL API support
n Support of HIL API Model Access port
XCP support
n Access to Simulink and TargetLink models as well as V-ECUs via XCP to SystemDesk
Debugging
n C code debugging during a running simulation
Code coverage
n Analyzing the extent to which code has been tested with CTC++ from Testwell
Processor-in-the-loop (PIL) simulation
n Running ECU code for the target processor on an evaluation board
Software
Bus simulation
n Support of Freescale MPC 5604B and Infineon TriCore 1797 evaluation board
Tool chain integration
n Off-the-shelf integration into the dSPACE rapid control prototyping (RCP) and hardware-in-the-loop (HIL) tool chain
Order Information
Application
Description
Order Number
Offline simulation of Simulink models
n Basic variant
n VEOS_BASE
Hardware
n Simulation of several Simulink models or FMUs

n The dSPACE Target for Offline Simulation for generating offline simulation binaries from
Simulink models (Simulink Coder is needed)

Offline simulation of one or more
virtual ECUs
n Add-on to the base variant VEOS_BASE
Offline simulation of virtual ECUs with

virtual CAN or LIN bus simulation
n Add-on to VEOS_ECU
n VEOS_ECU
n Simulation of Simulink models or FMUs together with 1... n SystemDesk V-ECUs

n VEOS_BUS
n Connecting SystemDesk V-ECUs via CAN bus

n VEOS_PIL
Engineering
Offline simulation for processor-in-the- n Add-on to VEOS_ECU

loop simulation
n Offline simulation for testing the virtual ECU with the target processor
Relevant Software
Software
Required
n Operating system: www.dspace.com/goto?os_compatibility
Optional
n Simulink
n dSPACE Automotive Simulation Models (p. 236)
n ModelDesk (p. 261)
n MotionDesk (p. 140)
2015
101
Features and Benefits

PC-Based Simulation of Heterogeneous Models
With VEOS, you can simulate Simulink and TargetLink models, FMUs, AUTOSAR software components, virtual ECUs,
and ECU networks in one single environment right on your
PC. This enables a fast integration and validation process for
your ECU software very early in the development process.
You will find errors long before the first hardware prototype
exists and save a lot of time and costs. Another advantage
of a PC-based simulation platform is that the parameters,
models and results can easily be exchanged between different kinds of user groups in the development process.
An error which has been found by a software architect,
integrator or tester is much easier for function developers
to understand, investigate and fix if they can use the same
simulation and testing environment.
Comprehensive Bus Simulation

Using VEOS, you can also simulate a network of AUTOSAR
virtual ECUs. These include a realistic operating system and
can be extended with basic software such as DEM, NVRAM
or the ECU state manager as the simulation scenario requires. A predefined COM stack can be included or configured for a virtual ECU in SystemDesk. CAN and LIN buses
and their bus-specific effects can be simulated with VEOS
on a PC without additional hardware. This gives you precise
simulation of distributed functions, including ECU network
communication, very early in the development process.
Openness Through Automotive Standards

VEOS can easily be integrated into your existing tool chain,
as it supports automotive standards such as
n ASAM (p. 25)
n AUTOSAR (p. 25)
n Functional Mock-up Inferface (FMI) (p. 25)
102
CAN/LIN Bus
So when you add VEOS to your rapid control prototyping

or HIL tool chain to perform PC-based simulation, you can
keep your existing tools. By deciding to use VEOS, you gain
high flexibility and investment protection for new projects
and challenges.
2015
Introduction
VEOS for Virtual Test Drive

n Use your own PC for closedloop tests of ADAS functions
n Reuse plant and environment
models
n Use models and automated
tests seamlessly throughout
all development phases
n Support of Simulink,
TargetLink, legacy C code,
AUTOSAR, and FMI
Model and
environment
parameterization
Simulation model
Visualization and
animation
Application Fields
Use Cases
Instruments,
simulation control
and validation
Software
Virtual test drive

using your own PC
Virtual bypassing with VEOS

n Same function models for
virtual and real ECUs
n Realistic closed-loop
simulation with virtual ECUs
and complex environment
models
n Easy stimulation with real,
recorded environment data
Hardware
Function/
Software Developer
V-ECU
Reuse of existing
virtual ECUs
New Simulink
function, to be tested
Reuse of the same

Simulink model for
external and internal
bypassing
Function/
Software Developer
2015
103
Engineering
Execution of function
tests inside a virtual ECU
in a virtual environment
Preparing Hardware-in-theLoop Tests

n Preparing HIL test artifacts
such as automated tests,
layouts, and model
configurations on the PC
n Identifying errors in the HIL
tests even before execution
n Maximizing HIL simulator
utilization
n Support of the HIL API
standard
Model and
environment
parameterization
Instrumentation and
simulation control
dSPACE and thirdparty simulation

models
Development and test

of HIL models, layouts
and test scenarios
Test automation
and reporting
Enhancing and
reusing HIL tests
Simulator
HIL Tester
Frontloading Hardware-inthe-Loop Tests

n No ECU prototype necessary
n Quick updates if changes
occur
n Easy to duplicate V-ECUs for
simultaneous use in different
tests
n Increased software quality
due to early automated tests
Test automation
and reporting
Instrumentation and
simulation control
Visualization and
animation
Execution of function tests

on a PC with virtual ECUs
HIL Tester
104
2015
Virtual ECU Testing

n Continuous integration of
ECU software using the PC
n Benefit from familiar debugging, code coverage and
parameter analysis settings
n Processor-in-the-Loop simulation of virtual ECUs
n Support of AUTOSAR-based
and non-AUTOSAR-based
workflows
Integration of
software components
and generation of VECUs
Application Fields
Introduction
Instruments,
simulation control
and validation
Software
Execution of integration
tests with virtual ECUs
Software
Integrator
Virtual Test Bench

n PC as virtual text bench
available at all times
n Integration of specialized
models from the computation department using FMI
n Realistic simulation using
virtual ECUs and complex
simulation models on the PC
n Use of an integrated tool chain
FMU
C Code
Simulation model
Stimulus
Instruments,
simulation control
and validation
Engineering
Execution of function tests

with realistic stimulus and
simulation models
HIL Tester
2015
105
Functional
Mock-Up Unit
Hardware
XML
Experiment and Visualization Software / ControlDesk Next Generation

Universal experiment software for electronic control unit (ECU) development
Highlights
n Universal, modular experiment and instrumentation
software for ECU development

n Integrated ECU calibration, measurement and
diagnostics access (CCP, XCP, ODX)

n Synchronized data capture across ECUs,
RCP and HIL platforms, and bus systems
n Powerful layouting, instrumentation, measurement
and post-processing
Application Areas
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 right to the end. These
are some of the tasks it can be used for:
n Rapid control prototyping (fullpass, bypass)
n Hardware-in-the-loop simulation
n ECU measurement, calibration, and diagnostics
n Access to vehicle bus systems (CAN, LIN, FlexRay)
n Virtual validation with dSPACE VEOS1) (p. 100, p. 123)
Virtual
validation1)
Rapid control
prototyping
(fullpassing/
bypassing)
Key Benefits
ControlDesk Next Generation unites functionalities that
until today required several specialized tools. It provides
access to simulation platforms as well as to connected bus
systems and can perform measurement, calibration and
diagnostics on ECUs, e.g., via standardized ASAM interfaces.
Its flexible modular structure (p. 108) provides high scalability to meet the requirements of specific application cases.
This gives you clear advantages in terms of handling, the
amount of training needed, the required computing power,
and costs.
Hardware-in-theloop simulation
ECU
(measurement,
calibration and
diagnostics)
Access to vehicle
bus systems
Synchronized time base on all platforms/devices
CAN
LIN
PC-based
offline simulation
106
1)
2015
FlexRay
Please see www.dspace.com/goto?VET for more information on virtual validation with virtual ECUs, and p. 123 for more
information on PC-based simulation with dSPACE VEOS.
Introduction
Module
Description
ControlDesk Next Generation Basic Version
n Same tool for rapid control prototyping, HIL simulation, offline simulation, ECU calibration
and diagnostics
n Easy creation of layouts and instruments
n Synchronous measurement on all data sources
n Integrated project and experiment management
Application Fields
n Integrated measurement data management (with ASAM MDF 4.1 support for import and export)
n Compatibility with several ASAM standards (such as MDF, XCP, CCP, ASAP2, ODX)
n Powerful tool automation capabilities for user-specific extensions and optimal process integration
n CAN access by dSPACE hardware and PC bus interfaces (e.g. DCI-CAN1): CAN monitoring,
CAN logging, and dedicated instruments for CAN bus objects

n Operator mode (protects your projects and experiments against unauthorized changes)
n Support of dSPACE VEOS for PC-based offline simulation (p. 123)
ControlDesk Next Generation Operator Version
n Using projects and experiment data that have been created before with the Basic Version
n Protection against altering and creating projects and experiments
Standard Platforms Module
n Support of dSPACE RCP and HIL platforms (DS1005, DS1006, DS1007, DS1103, DS1104,
Multiprocessor Module
n For using ControlDesk Next Generation with dSPACE multiprocessor systems based on
MicroAutoBox, NEW: MicroLabBox)
Software
DS1005 or DS1006
n Support of multicore applications for DS1006, DS1007, and MicroLabBox
n Add-on to Standard Platforms Module
SCALEXIO Platform Module1)

SCALEXIO Multicore Module
n For using ControlDesk Next Generation with dSPACE SCALEXIO

n Support of multicore applications for dSPACE SCALEXIO
n Add-on to SCALEXIO Platform Module
SCALEXIO Multiprocessor Module2)
n Support of multi-processing-unit applications for dSPACE SCALEXIO

n Add-on to SCALEXIO Platform Module
ECU Interface Module
n AUD, NBD, JTAG/Nexus, JTAG/OCDS and JTAG/SDI

n CCP (CAN Calibration Protocol)
n XCP on CAN, XCP on Ethernet3) (TCP/IP and UDP/IP), XCP on FlexRay
n Compliance with the ODX database standard (ASAM MCD-2D v2.0.1 and v2.2.0
Hardware
ECU Diagnostics Module
(ISO 22901-1))
n Support of ISO protocols for CAN and K-line
n Dedicated instruments to execute diagnostic services and to read or clear the ECU fault memory
n ECU flash programming via diagnostic interfaces
n Support of ASAM MCD-3D v2.0.2
Signal Editor Module4)
n For graphical stimulus definition

n Time-synchronous stimulus generation on dSPACE real-time hardware and Simulink models
simulated in dSPACE VEOS

n Measured data can easily be replayed
n Several stimulus patterns can be executed independently
Engineering
n Support of HIL-API stimulus format (.stz files, i.e., zipped .sti files)
Bus Navigator Module
n Support of CAN (incl. J1939), LIN, and FlexRay5) buses for dSPACE hardware or PC bus interfaces
n Replaying recorded CAN messages
n Dedicated instruments for LIN and FlexRay bus objects
n LIN monitoring and logging for dSPACE hardware
n FlexRay monitoring and logging via PC bus interfaces
n Managing the failure insertion unit (FIU) of dSPACE Simulator
n Automation interface for measurement, calibration, and diagnostics according to the ASAM
MCD-3 standard
n Continuous data acquisition in real-time raster
n Remote ASAM MCD-3 access to ControlDesk Next Generation via COM/DCOM API
The SCALEXIO Platform Module includes the Standard Platforms Module.

2)
The SCALEXIO Multiprocessor Module includes the SCALEXIO Multicore Module.
3)
Also for access to simulated virtual ECUs.
4)
Signal generation not supported for the DS1103, DS1104, DS1007, and MicroLabBox.
5)
The MCD3 Automation Module is not supported by the ControlDesk Next Generation Operator Version.
1)
2015
107
Failure Simulation Module

MCD3 Automation Module5)
Module Overview
ControlDesk Next Generation: Modules

ControlDesk
Next Generation
Basic Version1)
Versions
Standard
Platforms
Module
Platform
support
Multiprocessor
Module 3)
ControlDesk
Next Generation
Operator Version2)
SCALEXIO
Platform
Module4)
SCALEXIO
Multicore
Module5)
1)
2)
SCALEXIO
Multiprocessor Module5)7)
3)
4)
5)
MCD3 Automation Module6)
Signal Editor Module
6)
Additional
functionality
7)
Comprehensive Basic Version;

a free Loader Version (platform
handling only) is also available.
Protection against altering
and creating projects and
experiments.
Add-on to the Standard
Platforms Module
Includes the Standard
Platform Module.
Add-on to the SCALEXIO
Platform Module
Please note: The MCD3
Automation Module is not
supported by the Operator
Version.
The SCALEXIO Multiprocessor
Module includes the SCALEXIO
Multicore Module.
Order Information
Product
Order Number

Standard Platforms Module
Multiprocessor Module9)
SCALEXIO Multicore Module11)
SCALEXIO Multiprocessor Module11)13)
MCD3 Automation Module
ControlDesk Next Generation Loader Version
CDNG_BASIC
CDNG_O8)
CDNG_STD
CDNG_MP
CDNG_SCLX
CDNG_SCLX_MC
CDNG_SCLX_MP
CDNG_ECU
CDNG_DIAG
CDNG_SE
CDNG_BNV
CDNG_FS
CDNG_MCD3
Free of charge
Relevant Software and Hardware12)

Software
Order Number
Required
Optional
Operating system: www.dspace.com/go/os_compatibility

dSPACE VEOS for PC-based simulation
dSPACE SYNECT for storing ControlDesk projects in the SYNECT database
Hardware
8)
9)
10)
11)
12)
2015
See p. 101
See p. 271
Order Number
Required
108
13)
Pentium 4 at 2.0 GHz or faster

1 GB RAM or more
CDNG_O is free of charge, but is available only if ordered together with CDNG_STD or CDNG_SCLX.
Add-on to the Standard Platforms Module
The SCALEXIO Platform Module includes the Standard Platforms Module.
Add-on to the SCALEXIO Platform Module
ControlDesk Next Generation is also approved for the MicroAutoBox Embedded PC (running under
Microsoft Windows 7, 32-bit Ultimate).
The SCALEXIO Multiprocessor Module includes the SCALEXIO Multicore Module.
Introduction
NEW: ControlDesk 5.3

Feature Area
Improvement
dSPACE Platforms
n Support
Platform Management and

Platforms/Devices
n Support
of Kvaser Leaf Light HS interface for CAN

dSPACE real-time hardware also in the rare case of corrupted boot firmware
n Enhancements to memory segment management
n Video capturing device: playing data from video streams
n VEOS platform: New automation event when pausing a running simulation
n DS1005-based and DS1006based multiprocessor systems: Editing processor names
n New time plotter instrument for displaying signals that are measured in a time-based raster
n Adding a Python script to an instrument to extend its functionalities flexibly and to thus create new custom
instruments
n Conveniently placing all the variables of a subgroup on a layout
n New Stopwatch instruments
Projects and Experiments
n Support of different SYNECT server versions
Variable Management
n Compressing variable descriptions to avoid long project loading times
Measurement and Recording
n Signal-wise loading of MDF 4.x data to handle large measurement files
Application Fields
n Accessing
Software
Instrumentation
of the new MicroLabBox (p. 516)
n Using a sample count trigger as a stop trigger for a time-based raster
Data Set Management
n Handling writeable measurements as parameters
n Enhanced description of diagnostics variables in the Variable Browser

n Fault Memory instrument: Display of DTC number and level
n Stimulation of VECU variables (A2L) in a VEOS simulation
n CAN FD support for dSPACE platforms (MicroAutoBox, DS1005, DS1006, DS1007)

n Synchronizing monitoring/logging with measurements
Tool Automation
n Accessing meta information of variable descriptions
Hardware
n Handling messages via automation
2015
109
Engineering
ControlDesk Next Generation Product Support Center

The ControlDesk Next Generation Product Support Center is
the primary online resource for ControlDesk Next Generation
users and provides information about releases, compatibility
information, FAQs, additional utilities, etc. The entry gate is
www.dspace.com/cdngpsc

Comprehensive Functionalities
The ControlDesk Next Generation Basic Version is a
comprehensive basic module offering many fundamental
features for experiment creation and management, instrumentation, etc. The module can be extended with further
ControlDesk Next Generation modules. With the Control
Desk Next Generation Basic Version, you can prepare
project/experiment data (such as layouts, data sets and
measurements) for later use in the operator mode or in the
ControlDesk Next Generation Operator Version (p. 124).
Intuitive, Ribbon-based User Interface

n State-of-the-art GUI technology (ribbons) as used
by other tools (Microsoft Office 2007 and newer,
MATLAB R2012b and newer)
n Ribbons to group commands for customer workflows
(different sizes and icons indicate importance to improve
memorability and touchscreen usability)
n Backstage view for central opening, importing and
saving of projects
n Start page for easy access to most recently opened
projects and user documentation
Start page for easy access to recent projects and user

documentation.
Description
n Easy creation of layouts and instruments
n Synchronous measurement on all data sources
n Integrated project and experiment management
n Integrated measurement data analysis
n Compatibility with several ASAM standards
n Powerful tool automation capabilities for user-specific extensions and optimal process integration
n CAN access by dSPACE hardware1) and PC bus interfaces (e.g. DCI-CAN1): CAN monitoring, CAN logging, and automatically generated Bus Instruments
for CAN messages

n Operator mode (protects your projects and experiments against unauthorized changes)
n Support of dSPACE VEOS for offline simulation (p. 123)
n Camera interface and video instrument (p. 119)
Order Information
110
Product
Order Number
n CDNG_BASIC
2015
To access the CAN interfaces of dSPACE hardware (i.e., to send and receive CAN messages), the Standard
Platforms Module (p. 125) is necessary.
1)
Introduction
Project Management
Application Fields
level is for organizing your instrument panels (layouts),

variable descriptions, data sets, signal generators, failure
simulation systems, and more. All your data is well structured
at all times and easy access is provided by the ControlDesk
Next Generation Project Manager. You can manage your
ControlDesk Next Generation projects with your version
control system. Check-out and check-in operations are
directly supported by ControlDesk Next Generation.
Software
Organizing Projects and Experiments

ControlDesk Next Generation organizes your work in
projects and experiments. A project is the outer organizational frame for your work on a topic. Within the project you can have many experiments, for example, each
representing a unique hardware setup. You can also assign
different variable descriptions to a single platform/
device in the experiment and easily switch between
them later on. The project level also holds global documents such as specifications or reports. The experiment
Hardware
Selecting a project and experiment in ControlDesk

Next Generation.
Using a SYNECT Server for Managing

ControlDesk Data
n Option to store entire ControlDesk projects in the
SYNECT database1)
n Modified projects and file-based items (such as layouts)
can be submitted to the database
n ConfigurationDesk build results can be directly
imported from the database1)
n Multiuser database, usable from different PCs
n Versioning projects in connection with SYNECT server
n NEW: Support of different SYNECT server versions
Access to SYNECT running on the same PC is free of charge. SYNECT Base is only necessary to access
a SYNECT database running on a separate PC.
1)
2015
111
Layouts can be grouped in folders.
Engineering
Example project in ControlDesk Next Generations

Project Manager.
Instrumentation
Visualizing Variables on Layouts
ControlDesk Next Generation offers two ways to visualize
variables on layouts. One possibility is to select variables via
the Variable Browser, place them on the layout (via drag &
drop or keyboard), and assign instruments to them (suitable
instruments like the table editor are shown). Another way is
to select an instrument from the Instrument Selector, place

it on the layout, configure it, and then assign variables to
the instrument. The Variable Browser uniformly shows the
variables of the platforms/devices contained in the experiment, and the list can be filtered.
A variable can easily be displayed in an instrument.
Instrument Selector
The Instrument Selector offers the entire set of instruments,
that can be placed on the layout (drag & drop). From there,
the instrument can be configured, and variables can be
assigned to it. You can define favorite instruments to be
offered every time you work with the variable-based
layouting. Pre-configured instruments (e.g., background
color definable) can be saved as custom instruments.
Table Editor
112
Instrument
Selector
2015
Introduction
Application Fields
Editing 3-D Maps

ControlDesk Next Generation has powerful features
for editing 3-D maps:
n Interpolation when axis values are changed
n Interpolation of all maps related to the
same shared axis
n XZ and YZ projections of 3-D maps
n Easy exchange of data with Microsoft Excel
Software
Variable Array
With the Variable Array instrument it is easy to quickly visualize multiple variables. Each variable is displayed in a row of
the instrument. The variables are marked via multi-selection
and dragged to the layout. The Variable Array provides
different column and cell types. This combination of both lets
you individually specify what is displayed in the instrument
cells and how you can change a parameter value.
Hardware
Variable Array
3-D map in the Table Editor
Multiswitch Instrument
2015
113
Engineering
Multiswitch Instrument
n Instrument for changing variable values by clicking
sensitive areas in the instrument and for visualizing
different states, depending on the current value of the
connected variable
n You can easily implement different switch types, e.g.,
rotary switches (with different positions, optionally
spring-loaded), manual and automatic gearshifts,
ignition locks
Plotter
The plotter in ControlDesk Next Generation is the central component for data visualization. With plotters, the
measured data can be compared to online data. Plotter data
can be displayed continuously or triggered (similar to an
oscilloscope).
The Plotter instrument provides a variety of features dedicated to efficient data analysis:
n XY cursor
n Time cursor
n Zoom view
n Option to display several y-axes in a stacked view
n Scroll bar below display area for navigation
n Automatic calculation of maximum, minimum, mean
value, and standard deviation over displayed time interval

n Various print and image creation capabilities
n Option to synchronize the time intervals of multiple
plotters
n Display of signals over time or as XY plot
n Save selected signals and time interval to a new
measurement file, with or without data reduction

n Move and copy signals from one y-axis to another,
or to another instrument (drag & drop)

n Display bit signals
n A leading raster can be assigned to the plotter to
directly connect the triggered visualization to a

triggered measurement raster
Data visualization with ControlDesk Next Generations plotter
Plotter with leading raster visualization
Time/Index Plotters
The Time Plotter (NEW) lets you display signals that are
measured in a time-based raster (time plots), while the Index
Plotter lets you display the values of measurement variables
in relation to corresponding event numbers (index plots). In
comparison to the standard Plotter, the Time/Index Plotters
have an enhanced performance.
n Plotter toolbar for quick function access
Time Plotter
n Easy zooming and moving

n Data cursors to analyze the curves
n Requires little layout space
n Axes can be made invisible
n Background picture possible
n Individual background color setting
n Triggered display without flickering
n Automatic triggering
n Manual trigger settings directly within the instrument
n Higher drawing performance by using hardware acceleration
Index Plotter
n Animation continues while zooming
114
2015
Introduction
Application Fields
XY Plotter
n Visualization of several curves (xy pairs of signals)
n Triggered XY Plotter visualization (specially suited for
high-frequency applications such as electric drive systems)
n Background picture possible
n Easy zooming and moving
n Data cursors to analyze the curves
XY Plotter
Avionics Instruments
The Primary Flight Display (PFD) for aerospace applications
offers an altimeter, an artificial horizon, a heading indicator,
and an airspeed indicator.
Primary Flight Display

2015
115
Engineering
Hardware
Software
Steering Controller
The Steering Controller provides a graphical representation of a connected game controller device and lets you
calibrate scalar parameters by moving the device or pressing its buttons or switches. The instrument provides force
feedback support.
Browser Instrument
The Browser Instrument allows you to integrate objects such
as web pages and other documents (like PDF files) directly
on ControlDesk layouts.
Sound Controller
The Sound Controller can be used to play simple sounds or
complex sounds in relation to specific variable values. So
you can create realistic sounds for your simulation model
(engine sounds, horns, wipers, etc.).
116
2015
Introduction
Application Fields
NEW: Extending Instrument Functionalities via Python

You can add a Python script to each instrument and assign Python code to the events of the selected instrument.
This lets you extend the instruments functionality via automation more flexibly.
Adding a Python script to an instrument
Software
NEW: Stopwatch Instrument

The stopwatch instrument was created by using the new
Python script feature for instrument extension described
above.
Hardware
Stopwatch instrument
General Handling
View Set dialog
2015
117
Customized View Set toolbar
Engineering
View Sets
ControlDesk Next Generations View Sets are named configurations which help manage different control bar and tool
bar configurations. This saves an enormous amount of time
when you work with different use cases and functionalities,
as the View Sets can easily be switched via a specific View
Set toolbar, and can be restored to a reset state that has
been saved before. View Sets can be created, renamed,
imported and exported, or assigned to a user-selected
image for customization.
Measurement
Easy Configuration of Measurements
To handle measurements and recordings, ControlDesk Next
Generation provides the Measurement Configuration tool.
The Measurement Configuration tool gives you access to
all the variables selected for measurement and recording,
lets you configure measurements and recordings, and helps
you define and manage triggers for measurement. All the
variables of all the platforms and devices in the active
experiment that are selected for recording can be listed.
Multi-raster measurements can be performed.
Triggered Measurements
You can define real-time triggers to influence the data stream
between the PC and the dSPACE hardware. The plotter can
be synchronized with these settings for an oscilloscope-like
presentation.
Measurement configuration
List of measured signals
Multiple Recorders
You can record to different destination files concurrently,
with independent start/stop triggering.
Multiple recorders
118
2015
Introduction
Application Fields
and to make audio recordings. The instrument also provides

file-based video streaming.
NEW: Simulating a real camera by playing video streams
synchronously to signals from other platforms during measurement.
Software
Camera Interface and Video Instrument

An integrated camera interface with associated video
instrument lets you record and replay camera images/videos
(e.g., with a USB webcam) synchronously to a measurement
recording. This makes it a lot easier to interpret measurements. It is possible to preview recordings in the online mode
the wiper control unit, the vehicle bus and the video camera
time-synchronously. ControlDesk can also replay the logged
data for detailed analysis later on. A dedicated video instrument lets you select and visualize individual video frames
and associate them with other measurement data.
Hardware
A typical use scenario is the validation of a vehicles wiper

control and rain sensor, where an extra video camera is usually mounted in the vehicle during test drives. This camera is
used to record the ambient weather conditions, the movement of the wipers and the raindrops on the windscreen.
ControlDesk Next Generation can be used to log data from
Engineering
Camera view
Windscreen
ControlDesk
Next Generation
Ethernet, USB
Sensor and
control unit
Camera
Recording and replaying video

and bus data synchronously.
2015
119
LIN, CAN, FlexRay
Measurement Data Pool

The Measurement Data Pool gives you an overview of all the
measurement files loaded in ControlDesk Next Generation
and displays the variables and bookmarks associated with
each file. Powerful filter options make it easy to find and
show the relevant information. Complete measurement files

can by assigned to an existing layout. Data can be imported
and exported in standard formats (such as ASAM MDF).
Measurement Data Pool
120
Bookmarks
You can set bookmarks during a measurement or recording
to mark certain measurement points you want to analyze
later. Bookmarks can be set either manually or automatically,
for example, by definable triggers. The bookmark navigator
gives you a list of all the bookmarks in the current measurement and in the measurement files loaded in ControlDesk
Next Generation. The bookmark navigator is linked with the

visualization in the Plotter instrument. When a bookmark is
selected in the navigator, the correct time context is displayed
in the plotter and the associated bookmark is highlighted.
You can edit and search for bookmarks in the navigator.
Calculated Variables
You can create new variables, called calculated variables,
whose values are calculated from other variables in the
associated description file. A formula editor helps you
define the calculation method. It is even possible to access
previous values in order to implement filters, derivations,
integrations or statistical functions such as mean values.
Calculated variables can be connected to instruments in
ControlDesk Next Generation and recorded in measurement

files just like normal measurement variables. You can also
create calculated variables based on variables in measurement files during postprocessing. Import and export options
for calculated variables and formulas makes it easy to reuse
them in different experiments and projects.
2015
Introduction
Tool Automation
Python Editor
ControlDesk Next Generation has an integrated Python
editor with syntax highlighting and automatic code completion
(IntelliSense). In conjunction with the Python interpreter, which
also ships with ControlDesk Next Generation, you have all
you need to write automation scripts efficiently. The interactive
command line interpreter in ControlDesk Next Generation
lets you test your lines of code on the go while scripting.
Application Fields
Software
Advanced ControlDesk Automation

n Event handling: React by automation scripts or external
tools (such as AutomationDesk, p. 156) to tool events
from ControlDesk Next Generation (such as start
measurement)
n Procedural and object-oriented programming features
n Manual modification of generated scripts for advanced
operations with built-in Source Code Editor
Hardware
tasks, such as parameter studies

n Automated experiment creation and configuration
n Powerful event mechanism to react to tool and user
events, for example
n ControlDesk Next Generation tool automation library
available with AutomationDesk
Use Case Examples for Tool Automation

n Layout and instrument handling
n Data set handling
n Experiment handling
n Platform handling
n Project handling
n Failure simulation
n Controlling monitoring, logging, and replay of Bus
Navigator
n Read and write variables directly without instruments
n Automated processing of recurrent, time-consuming
Engineering
Key Benefits
ControlDesk Next Generation integrates perfectly into

your existing development process. (For automation based
on the ASAM MCD-3 standard, please see p. 138, MCD-3
Automation Module).
n NEW: Accessing meta information of variable
descriptions
n NEW: Handling messages via automation
Available with AutomationDesk:

Tool Automation Library for ControlDesk
Next Generation
Event Configuration dialog
2015
121
ControlDesk Next Generation API

An object model in ControlDesk Next Generation
Basic Version lets you access many of its functions by
automation scripts. The Application Programming Interface is accessible from .NET programming languages (e.g.,
Visual Basic and C#) and COM/DCOM-based programming languages (e.g. Python and C++). With scripts you can
perform your complex workflows in no time, such as creating a project and experiment with your custom settings.
The API also lets you implement individual functionality, such
as exporting data sets in a custom file format, to ensure that
Data Sets
Data Structures with Parameter Values
Different operations can be performed on data sets loaded
in ControlDesk Next Generation. You can copy and rename
data sets and export them as a CDF file (Calibration Data
Format as standardized by ASAM), DCM file, or Microsoft
Excel-compatible file. Data sets can also be write-protected.
Data Set Manager

With the Data Set Manager, you can list, compare and
merge calibration parameters contained in data sets, and
edit data sets. New data sets can be created and calibration notes can be added to individual parameters. You can
compare any number of data sets and show their differences. ControlDesk Next Generation provides options to
generate reports as XML, HTML or PDF files. In addition,

with customer-specific XML style sheets you can adapt
reports individually. You can store data sets in a global
pool and compare them with data sets from other projects and experiments. You can import .par files from
ControlDesk 3.x into an experiment as a data set.
Data Set Manager
Calibrating Variables
ControlDesk Next Generation offers many input instruments
for adjusting parameter values. Of course, it is possible to
calibrate scalar as well as multidimensional parameters.
Parameter changes can be made as physical values or as
represented on the target platform, as HEX, decimal, or
binary values.
122
2015
Introduction
dSPACE VEOS Platform for PCbased Simulation

models in a very early development stage, before rapid control prototyping (RCP) and hardware-in-the-loop simulation
(HIL), and independently of any specific simulation hardware. These early validation activities substantially increase
the maturity level of your models. With ControlDesk Next
Generation, you can conveniently reuse your data, such as
experiments, layouts, and data sets resulting in a smooth,
seamless workflow between early validation, RCP, and HIL.
Application Fields
Virtual Validation
VEOS (p. 100) is the dSPACE platform for virtual validation
in the development of electronic control units (ECUs). VEOS
makes it possible to validate ECU software early by PC-based
simulation and to realistically simulate ECU network communication (CAN). ControlDesk Next Generation and VEOS
together allow you to run and access a wide range of different models: function models, virtual ECUs (V-ECUs), and
vehicle/environment models. You can set up experiments,
layouts and data sets and validate function and environment
Hardware
Software
Plant Model
PCbased simulation with VEOS and

ControlDesk Next Generation.
2015
123
Engineering
XCP

Protection Against Unauthorized Changes
ControlDesk Next Generation Operator Version is a costeffective version of ControlDesk Next Generation that provides
a subset of functionality for running existing experiments.
When using ControlDesk Next Generation Operator Version,
you can only use project/experiment data (such as layouts,
data sets and measurements) that were previously created
and saved with ControlDesk Next Generation Basic Version
(p. 110). The Operator Version provides the same functionalities as the operator mode of the Basic Version.
Description
n Use projects and experiment data that were previously created with the Basic Version
n Protect against altering and creating projects and experiments
n Perform measurements on platforms/devices (corresponding platform/device module licenses needed)
n Use existing layouts (without modification)
n Reload variable descriptions
n Record data files (automatically added to the experiment)
n Export measurement data files
n Change the working data set
n Duplicate and export data sets
n Use tool automation (for all functionality available with the Operator Version)
n Work with Bus Navigator instruments included on existing layouts
n Monitor, log and replay bus data with the Bus Navigator (CDNG_BNV license needed)
n Perform signal generation with existing signal descriptions (CDNG_SIGNALEDITOR license needed)
n Work with failure patterns of existing failure simulation systems (CDNG_FS license needed)
n Please note: The MCD3 Automation Module is not supported by the Operator Version.
Order Information
124
Product
Order Number
n CDNG_O1)
2015
1)
CDNG_O is offered free charge, but is only available by ordering together with CDNG_STD (p. 125) or CDNG_SCLX (p. 127).
Introduction
Standard Platforms Module1)
Hardware
Software
Application Fields
Access to dSPACE Real-Time Platforms

The Standard Platforms Module is an optional software module which provides access to the dSPACE real-time platforms
DS1103, DS1104, DS1005, DS10062), DS10072), MicroAutoBox, and MicroLabBox2). With this access it is possible to
perform measurements and adjust parameter values on
the dSPACE hardware with ControlDesk Next Generation.
Support of dSPACE RCP and HIL platforms (DS1005, DS10062), DS10072), DS1103, DS1104, MicroAutoBox, MicroLabBox2))
Order Number
Standard Platforms Module1)
1)
2)
CDNG_STD
Upgrade to SCALEXIO Platform Module possible (p. 127)

The Multiprocessor Module is also necessary when you use multicore applications on a DS1006, DS1007, or MicroLabBox.
2015
125
Product
Engineering
Order Information
Access to Multiprocessor Features
The Multiprocessor Module is an add-on module to the
Standard Platforms Module, and it provides access to the
multiprocessor features of the dSPACE real-time platforms
DS1005 and DS10061) as well as to using multicore applications on the DS1006, DS1007, and MicroLabBox.
Example:
MicroLabBox
DS1007 (Dual-Core)
Gigalink
DS1006 (Quad-Core)
3 x DS1006 (Single-Core)
or 3 x DS1005
Using ControlDesk Next Generation with the Multiprocessor Module for multiprocessor applications (DS1005, DS1006) and multicore
applications (DS1006, DS1007, MicroLabBox).
Order Information
126
Product
Order Number
2015
1)
CDNG_MP
The Multiprocessor Module is also necessary when you use multicore applications on a DS1006, DS1007, or MicroLabBox.
Introduction
Application Fields
Background Information: SCALEXIO Hardware

The SCALEXIO technology introduces completely new
hardware and software architectures. With SCALEXIOs
flexible component design, each system is precisely scalable to any desired size, completely software-configurable,
and versatile enough to be used in different test tasks.
n Real-time processor with the latest processor
technology
n IOCNET: serial I/O network
n I/O board types: HighFlex and MultiCompact
n User-programmable FPGA
n Flexible component design
n Powerful configuration software (ConfigurationDesk)
Hardware
Software
Access to dSPACE SCALEXIO

The SCALEXIO Platform Module is an optional software
module which provides access to a dSPACE SCALEXIO
system (p. 296).
Engineering
Access to a dSPACE SCALEXIO system.
Order Information
Product
Order Number
SCALEXIO Platform Module
1)
The SCALEXIO Platform Module includes the Standard Platforms Module (p. 125).
2015
127
CDNG_SCLX
SCALEXIO Multicore Module1)

Even More Flexibility
The SCALEXIO Multicore Module provides access to multicore applications running on dSPACE SCALEXIO. Three cores
can be used for computing models and I/O, resulting in more
available computation power.
Support of multicore applications

Support of multicore applications for dSPACE SCALEXIO.
Order Information
Product
Order Number
SCALEXIO Multicore Module
1)
128
CDNG_SCLX_MC
Add-on to the SCALEXIO Platform Module (p. 127).
2015
Introduction
SCALEXIO Multiprocessor Module1)2)

Module provides access to the multiprocessor (and multicore) features of a dSPACE SCALEXIO multi-processing-unit
system.
Software
Application Fields
More Power
SCALEXIO supports the coupling of two or more SCALEXIO
Processing Units to increase the computing power available for complex simulations. The SCALEXIO Multiprocessor
Hardware
Multiprocessor support for SCALEXIO.
Order Information
Product
Order Number
SCALEXIO Multiprocessor Module
1)
2)
Add-on to the SCALEXIO Platform Module (p. 127).

Includes the SCALEXIO Multicore Module (p. 128).
2015
129
Engineering
CDNG_SCLX_MP

Calibration and Measurement
The ECU Interface Module is an optional software module
for calibration and measurement access to electronic
control units.
n Support of ASAM A2L files (ASAM MCD-2 MC)
n Online and offline calibration
n Support of single-page and two-page concepts with
a working and reference page

n Automatic reconnect to unplugged ECUs for resuming
measurement
n Seed & key access to ECU for XCP and CCP
n Calibration of ECUs without dedicated data segments
On-chip
RAM
JTAG, AUD,
Nexus, ...
CAN
C
On-chip
Flash
FlexRay
Ethernet
Serial calibration
Generic Serial Interface
(DCI-GSI1, DCI-GSI2)
XCP on CAN, CCP
XCP on Ethernet
XCP on FlexRay
Overview of ECU interfaces and protocols of ControlDesk Next Generation.
Order Information
130
Product
Order Number
CDNG_ECU
2015
Introduction
n Compliance with the ODX database standard
n Support of ASAM MCD-3D v2.0.2 (COMPARAMs
n Support of ISO protocols for CAN and K-Line
according to PDU API v2.2, ISO 22900-2)

n NEW: Enhanced description of diagnostics variables in
the Variable Browser
n NEW: Fault Memory Instrument: displaying DTC
number and level
n Dedicated instruments to execute diagnostic services
and to read or clear the ECU fault memory

n ECU flash programming via diagnostic interfaces
n Support of ControlDesks application programming
Application Fields
ECU Diagnostics with ControlDesk Next Generation

The ECU Diagnostics Module is an optional software
module that facilitates the calibration and validation of ECU
diagnostic functions.
Hardware
Key Benefits
The ControlDesk Next Generation ECU Diagnostics Module
enhances ControlDesk Next Generation to a comprehensive,
integrated measurement, calibration, and diagnostics tool
(MCD tool). Additional instruments for working with an
ECUs fault memory, and diagnostic services and jobs, are
seamlessly integrated into ControlDesk Next Generation.
The easy generation of diagnostic variables from ODX allows
you to use DTCs, measurements and parameters with the
standard instruments and together with signals from other
sources. The integrated ECU flash programming support
lets you update the ECU with the latest software version or
calibration data via diagnostic protocols.
Engineering
Fault Memory Instrument

With the Fault Memory instrument you can read and display the fault memory of one or multiple ECUs, either on
demand or cyclically. Status and environment information
can be displayed for each diagnostic trouble code entry.
The fault memory can be cleared either completely or partially. The fault memory information can be saved to file
in an ASCII or XML format for documentation purposes.
ControlDesk Next Generation can also indicate any changes
in the number of diagnostic trouble code entries in the Plotter
instrument and also saves a list of all current entries to your
measurement file as a bookmark.
Integrated measurement, ECU calibration and diagnostics
in ControlDesk Next Generation.
2015
131
Application Areas
ECUs can be interfaced via the ISO-standardized diagnostic
protocols KWP2000 (ISO 14230), Diagnostics on CAN (ISO
15765), UDS (Unified Diagnostic Services) (ISO 14229-1),
OBD (ISO 15031), and Transport Protocol (TP 2.0) on CAN.
The ECU Diagnostics Module is fully compliant with ODX
(Open Diagnostic Data Exchange), the ASAM MCD-2D
standard (v2.0.1 and v2.2.0 (ISO 22901-1)). Combined
with the ControlDesk MCD3 Automation Module, a standard automation interface according to ASAM MCD-3 D
(v2.0.2) is provided for the remote control of diagnostic
tasks. Alternatively, many of ControlDesks diagnostics functions can be accessed by automation script via a dedicated
application programming interface (API) (p. 121).
Software
interface (API) for access to diagnostics functions

(p. 121)
Diagnostics Instrument
With ControlDesk Next Generations Diagnostics Instrument, you can work with diagnostic services and Java jobs
described in the ODX database. The available services and
jobs are presented concisely in a tree structure for easy
finding and selection. You can select a service or job,
parameterize and execute it, and monitor the associated
ECU responses and results. You can perform execution once
or cyclically. Diagnostic communication can be logged and
saved to file.
Instrumentation of Diagnostic Variables

With ControlDesk Next Generation you can handle diagnostic
identifiers from an ODX database in the same way as variables
from other sources such as the ASAM MCD-2 MC file. For
instance, diagnostic measurement identifiers can be displayed
together with signals from other sources on a common time
base in the same Plotter instrument and can be saved to
the same measurement file. Diagnostic parameter identifiers
can be adapted with ControlDesk Next Generations regular
calibration instruments such as the Alphanumeric Input
instrument. This makes it easy to handle measurement and
calibration, including the use of ECU diagnostics identifiers,
and you do not need to know the details of the diagnostics
protocol implementation on the ECU.
Flash Programming
To perform a flash programming task in ControlDesk
Next Generation, you simply select the logical link to be
flashed and the appropriate flash session, and then execute
it. Optionally, another flash data file, such as a HEX file
with the latest calibration data, can also be selected. Before
executing a flash job, you can adjust the input parameters.
The progress and status of the flash sequence can be monitored on screen.
Quick and easy ODX-based ECU flash
programming with ControlDesk Next Generation.
Remote Access via ASAM MCD-3 D API

or ControlDesks Automation API
A COM/DCOM implementation of the standard automation interface according to ASAM MCD-3 D (v2.0.2) is provided in conjunction with the MCD3 Automation Module
(p. 138). ControlDesk Next Generation experiments are used
as MCD-3 D projects, but MCD-3 D requires the experiments
to be preconfigured. Alternatively, many of ControlDesks
diagnostics functions can be accessed by automation script
via a dedicated application programming interface (API),

(p. 121). For example, ControlDesks tool automation feature
provides the complete configuration of experiments and
extended and improved functionality for MCD-3 D. This
allows ECU diagnostic tasks to be performed during test
automation, e.g., via AutomationDesk (p. 156), which has
separate libraries for the two remote access options.
Order Information
132
Product
Order Number
n CDNG_DIAG
2015
Introduction

n Compliant to ASAM HIL-API standard (stimulus part)
n Signals can easily be used by AutomationDesk
n Signal generators can be executed concurrently on
all nodes of a multiprocessor system

n Support of SCALEXIO
Application Fields
Graphical Stimulus Definition

The Signal Editor Module is an optional software module to
graphically define and execute signal generators for stimulating model variables of real-time applications running on
dSPACE real-time hardware1).
n Powerful editor for graphical stimulus definition
n Easy replay of measured data (incl. ASAM MDF)
n Dynamic stimulus options (e.g. segment switching,
properties)
n Independent execution of several signal generators
n Support of PC-based offline simulation with
dSPACE VEOS
n NEW: Stimulating VECU variables (A2L) in
a VEOS simulation
Software
Synthetic signal composed of different segment signals (repeated)
Measurement signal
imported from the
measurement data pool
than 50 km/h.). It is possible to use recorded signals from the

measurement data pool in the Signal Editor for real-time data
replay. The Signal Editor saves the specified signal behaviors
according to the ASAM AE HIL-API 1.0 standard.
Engineering
Defining Time-Synchronous Stimulus Signals

You can define several time-synchronous stimulus signals
such as sine, ramp and noise in the new graphical Signal
Editor, and couple changes in signal form to conditions (e.g.,
Generate a sine signal as long as the vehicle speed is lower
Hardware
Combination of the
synthetic signal and
the measurement signal
(multiplication)
Product
Order Number
n CDNG_SE
1)
Signal generation not supported for the DS1103, DS1104, DS1007, and MicroLabBox.
2015
133
Order Information

Overview of Bus Communication
The Bus Navigator is a ControlDesk Next Generation component that lets you handle several types of items for all
platforms in a project: CAN messages (incl. J1939), LIN
frames, and FlexRay PDUs that are configured by blocks
of the RTI CAN MultiMessage Blockset, blocks of the
RTI LIN MultiMessage Blockset, and settings in the dSPACE
FlexRay Configuration Package. You can manipulate
messages, frames, and PDUs before transmission, exclude
them from being transmitted, etc. The Bus Navigator Module supports dSPACE hardware and PC-CAN interfaces
(e.g. dSPACE DCI-CAN1). It also supports SCALEXIO.
n NEW: CAN FD support for dSPACE platforms
(DS1005, DS1006, DS1007, MicroAutoBox)
n NEW: Synchronizing monitoring/logging with
measurements
Features of the Bus Navigator

The Bus Navigator has numerous features and lets you perform many tasks:
n Support of CAN (incl. J1939), LIN and FlexRay buses
n Support of dSPACE hardware and PC CAN interfaces
(e.g., DCI-CAN1, Vector VN16xx)
n Dedicated bus instrument for handling entire
messages/frames/PDUs
n Create instruments to view RX messages/frames/PDUs
and configure and trigger TX messages/frames/PDUs
n Monitor and log bus data (CAN messages, LIN frames,
and FlexRay1) PDUs).
n (only for CAN) Replay logged CAN bus communications
n (only for CAN) Define user-defined databases (UDDB)
and handle messages in UDDBs
n CAN TX layouts for PC bus interfaces
n LIN monitoring for PC bus interfaces
n Automation support for creating Bus Instruments and
controlling bus monitoring, logging, and replay
n FlexRay monitoring without running measurement
The Bus Navigator

offers easy access to
CAN, LIN, and FlexRay
communication.
Handling CAN communication
134
2015
1)
FlexRay support for PC bus interfaces only.
Introduction
Support for dSPACE Hardware

PC CAN Interface Hardware
n DCI-CAN1 (USB-to-CAN interface)
n Calibration Hub (USB hub with two USB to-CAN interfaces)
Real-Time Bus Interface Hardware
Application Fields
n MicroAutoBox II
n DS1103 PPC Controller Board
n DS2202 HIL I/O Board
n DS4302 CAN Interface Board
n DS4330 LIN Interface Board
n DS4505 Interface Board1)
n DS2671 Bus Board
Software
n DS2680 I/O Unit (with bus support)
Support for Third-Party Hardware

PC CAN Interface Hardware
n Eberspcher FlexCard Cyclone II
n Eberspcher FlexCard Cyclone II SE
n Eberspcher FlexCard USB
n Kvaser LAPcan
n Kvaser LAPcan II
Hardware
n NEW: Kvaser Leaf Light HS interface

n Kvaser Leaf Professional
n Kvaser Memorator Professional
n Kvaser USBcan II
n Kvaser USBcan Professional
n Vector CANcardXL
n Vector CANCardXLe
n Vector CANcaseXL
n Vector VN16xx series
n Vector VN7600
1)
The DS4505 Interface Board requires additional DS4340 FlexRay Interface Modules.
2015
135
Engineering
n Vector VN89xx
PC LIN Interface Hardware

n Kvaser LAPcan
n Kvaser LAPcan II
n Kvaser Leaf Professional LIN (USB)
n Vector CANcardXL (PCMCIA)
n Vector CANCardXLe
n Vector CANcaseXL (USB)
n Vector VN16xx series
n Vector VN89xx
PC FlexRay Interface Hardware

n Eberspcher FlexCard Cyclone II
n Eberspcher FlexCard Cyclone II SE
n Eberspcher FlexCard USB
n Vector VN7600
n Vector VN89xx
Order Information
136
Product
Order Number
n CDNG_BNV
2015
Introduction

n Remote control of the failure insertion unit in dSPACE
Simulator Mid-Size or Full-Size

n Failure Simulation Navigator for access to all elements
of a failure simulation system

n Failure Pattern Window for setting pin failures
Application Fields
Key Benefits
The Failure Simulation Module is an optional software module for simulating failures in the wiring of an electronic control unit via a Failure Insertion Unit. You can simulate failures
in the wiring of an electronic control unit (ECU) such as an
ECU pin short-circuited to ground or the battery voltage, or
an ECU pin that is not connected (cable break).
n Import ECU pin description files

n Simulate loose contacts or switch bouncing for
DS793/ DS794 sensor FIU

n Supports the DS1450 Bus FIU Board
n Support of dSPACE SCALEXIO
Software
Hardware
Typical ControlDesk Next

Generation environment with
the failure simulation component
ECU
Failure insertion
unit
CAN or
RS232 connection
Bus / Ethernet connection
Overview of the hardware of

a failure simulation system
Order Information
Product
Order Number
CDNG_FS
2015
137
dSPACE Simulator
Engineering
ControlDesk
Real-time system
MCD3 Automation Module1)2)3)

Remote Control of ControlDesk Next Generation
The MCD3 Automation Module is an optional software
module that enables users to automate ControlDesk Next
Generation via the ASAM MCD-3 standard.
n Automation interface for measurement,
calibration, and diagnostics according to
the ASAM MCD-3 standard
n Continuous data acquisition in real-time raster
n Remote control of ControlDesk Next Generation
via COM/DCOM API
Application Areas
The MCD3 Automation Module makes it possible to auto
mate measurement, calibration, and diagnostic tasks with
ControlDesk Next Generation. It is typically used for:
n Validation of diagnostic functions

n ECU test automation
n Optimization of control strategies on
rapid control prototyping systems
n Automated optimization of calibration parameters
at test benches
n Data capturing, data analysis, and tuning of calibration
parameters in MATLAB or other COM/DCOM-capable

applications
Key Benefits
The MCD3 Automation Module features a COM/DCOM
interface based on the ASAM MCD-3 standard for automating measurement, calibration and diagnostic tasks. The
interface lets you perform tasks such as uploading variables
associated with a device in ControlDesk Next Generation
and capturing data in your automation system synchronously
to given real-time rasters. The MCD3 Automation Module
provides the same automation interface for access to rapid

control prototyping systems, ECUs and vehicle buses.
The diagnostic part of the automation interface lets you
access the ECU via its diagnostic interface. During test
automation, this allows verification of the ECU diagnostics
interface itself, besides providing assistance to comprehensive
ECU function testing.
Usage Without Graphical User Interface

You can use ControlDesk Next Generation without
a graphical user interface so that automation scenarios
can be remote-controlled completely by your automation
system. This way, engineers responsible for automation
do not have to get used to using the ControlDesk Next
Generation user interface.
1)
138
2015
2)
3)
The MCD3 Automation Module contains the activation for the automation interface, but not for the platform/device/
diagnostic access to the hardware. Other modules are needed for this.
Tool automation without ASAM MCD3 is included in ControlDesk Next Generation Basic Version (p. 110)
Please note: The MCD3 Automation Module is not supported by the ControlDesk Next Generation Operator Version.
Introduction
Select ControlDesk experiment

Select ECU
Select variable description
Upload available variables
Calibrate offline or online
Perform online/offline
transition
Switch calibration page
Capture data synchronously
to ECU raster or in polling
raster
Record data in measurement file
Automation and/or
optimization tool
COM / DCOM
ASAMMCD 3MC
ASAMMCD 3D
Select ODX project

Select vehicle
Select ECU (logical link)
Upload available services
and jobs
Perform online/offline transition
Execute diagnostic services
(send requests, receive
responses)
Execute jobs
Perform ECU flash programming
Application Fields
Software
Automation of measurement, ECU

calibration and diagnostics with the
ASAM MCD3 MC and ASAM MCD3 D
standard automation interfaces.
AutomationDesk
Remote
Calibration (COM)
Library
Remote
Diagnostics (COM)
Library
ASAM MCD-3 MC
ASAM MCD-3 D
MCD-3 Automation Module
Database
ECU
Diagnostics
Module

interfaces or protocols,
e.g., CCP, XCP, ...
1)
Database
Diagnostic protocol, e.g.

Unified Diagnostic Services (UDS),
KWP2000 on CAN,
KWP2000 on K-Line
Application example:
AutomationDesk and ControlDesk
Next Generation with the MCD3 Automation
Module, the ECU Interface Module, and the
ECU Diagnostics Module for ECU access via
calibration and diagnostic interfaces during
test automation.
Hardware
ECU
Interface
Module
ASAM MCD-2 D
(ODX)
Product
Order Number
MCD3 Automation Module
1)
Engineering
Order Information
CDNG_MCD3
It is also possible to access dSPACE hardware. In this case, the Standard Platforms Module (p. 125) or the SCALEXIO
Platform Module (p. 127) is also required.
2015
139
Basic
ASAM MCD-2 MC
(ASAP2)
Experiment and Visualization Software / MotionDesk
MotionDesk
3D online animation of simulated mechanical systems in real time
Highlights
n Tight integration to ModelDesk and ASM
n Intuitive graphical scene design
n Enhanced support for all aspects of advanced driver
assistance systems (ADAS)
n 3-D object library with objects in COLLADA format
n Powerful rendering engine guarantees detailed and
realistic visualization
n Integrated 3-D Scene Editor
n NEW: Animated characters
n NEW: International traffic signs
Application Area
When you develop a mechatronic control system such as an
advanced driver assistance system, you need to be certain
that it performs correctly. You can do this by running HIL
simulations. The best way to understand the behavior of a
simulated system is to use animated visualization in realistic
3-D scenes. Combining a simulation system with real-time
animation is the ideal way to get the whole picture. Since
animations can be recorded and replayed, it is easy to
compare different controller development strategies by using overlay techniques. MotionDesk enhances the dSPACE
tool chain by visualizing how mechanical objects move in
the 3-D world. MotionDesk is the perfect tool to visualize
any kind of vehicle dynamics development and driving
maneuvers, such as lane change, split-, and cornering.
Support of Advanced Driver Assistance Systems

MotionDesk provides enhanced support for all aspects of
advanced driver assistance systems (ADAS), where the complexity of an action has to be seen to be understood. When
an ADAS is tested, the visualization must be realistic enough
for object recognition, and a high frame rate is crucial.
140
Key Benefits
MotionDesk helps you get more out of your HIL simulator, visualizing your simulation in virtual worlds that exactly
represent the simulation scenarios. MotionDesk reads the
data from the HIL simulator and displays the animation of
the moving objects (vehicle, wheels, steering wheel, etc.)
in real time, using the perspectives and render modes that
you choose yourself, to give you a clear understanding of
how the simulated objects actually behave. You can store
the animations as experiment files and record video files to
document and illustrate your developments.
MotionDesks rendering engine guarantees detailed and

realistic visualization. Even complex scenes can be rendered
at a steady rate of 60 frames per second, and beyond.
2015
Introduction
Main Features and Benefits

Feature
Description
Benefit
Instant animation
n Powerful rendering engine
n Detailed and realistic visualization
Low latency between simulation and animation

n Intuitive motion model to accurately position the observer
in the scene
n Even complex scenes can be rendered at a steady 60
Multitrack mode
n Visual comparison of simulation run with reference data tracks
n Parameter behavior studies
Force vector visualization
n Forces represented graphically, e.g., by arrows
n You can easily see which forces influence motion and how
3-D scene building
n Graphical interactive scene design
n Easy, intuitive operation
n Scene creation integrated in MotionDesk
n Operation from one tool
n All done by drag & drop
n Fast scene creation and modification
n Automatic generation of guard rails, noise barriers and
n Synergy with other tools for optimized workflow
frames per second
Application Fields
n Realistic man-in-the-loop simulation
environment objects
n Automation API for remote-controlling MotionDesk
3-D Object Library
n 3-D object libraries based on standardized COLLADA file formats n Easy migration from older MotionDesk versions
n 3-D object libraries can be extended by user-defined
objects in COLLADA
n 3-D object search via keywords and names

n Grouping 3-D objects
n Better overview of all objects
n Steadily growing library of 3-D objects: cars, houses, trees, etc.
n Better scene structures
Software
n Imports and migrates VRML2
n NEW: Animated characters (optional)

n NEW: International traffic signs (optional)
Lossless, time-based data

acquisition
n Time-based simulation data acquisition with equidistant
Speed control
n Variable slow- and fast-motion replay
n Synchronized replay of recorded animations in real time
time stamps
n You can slow the animation to observe details and speed
it up during uneventful sections

Video file generation
n Animations exported into video files (AVI, MPEG-4, etc.)
n Archiving and distributing important animations
Multi-PC support
n Scalable visualization system for interactive driving
n More views increase realism during man-in-the-loop
simulation
Hardware
simulators via Multi-PC Interface Kit or directly with

SCALEXIO simulators (p. 296)
Product
Order Number
MotionDesk
(Offline simulation with Simulink and VEOS)
n MOTIONDESK_OFF
Add-on: MotionDesk Hardware Access
n MOTIONDESK_HWA
Add-on: MotionDesk Animated Characters
n MOTIONDESK_ANIM_CHAR
Add-on: MotionDesk Traffic Signs
n MOTIONDESK_TRF_SIGNS
MotionDesk Multi-PC Interface Kit
n MotionDesk Multi-PC Interface Kit
Engineering
Order Information

Order Number
Included
Blockset
n MotionDesk Blockset to extend Simulink
Required
Integrated development environment
n MATLAB/Simulink/Simulink Coder (formerly Real-Time
Workshop) from MathWorks

Optional
Operating system
n www.dspace.com/goto?os_compatibility
dSPACE Simulator interface
n Real-Time Interface
n RTI
SCALEXIO interface
n ConfigurationDesk
See p. 48
VEOS
n Platform for PC-based simulation
See p. 100
2015
141
Software
Hardware
Required
Optional
Order Number
Recommended PC system
n Please visit our website at www.dspace.com/go/mdhwrequ
dSPACE Simulator
(PPC board)
n DS1005 PPC Board (p. 352) or
n DS1005
n DS1006 Processor Board (p. 356) or
n DS1006
n DS1007
Single-board hardware
MicroAutoBox hardware
n DS1103 PPC Controller Board (p. 334)
n DS1103
n Support for MicroAutoBox I and MicroAutoBox II1)
See p.522
SCALEXIO
n Support for SCALEXIO
See p.296
MotionDesk
Multi-PC Interface Kit
n 10 megabit/s Ethernet card for each connected PC
n MotionDesk
Multi-PC Interface Kit
Various MicroAutoBox variants are available. Please contact dSPACE for advice on which variant you need.
1)
142
2015
Introduction
Functionality at a Glance
Everything You Need in One Tool

MotionDesk is easy to handle. You can perform all the important operations, such as 3-D scene creation, in one tool,
mainly by drag & drop.
n Scene Navigator
n 2-D scene view
n New rendering kernel
n 3-D library
n Property grid
n Instruments
Application Fields
Software
Preparation of HIL Tests via Offline Simulation

You can use VEOS, dSPACEs platform for PC-based offline
simulation, to set up models, layouts and tests in an early
phase before the HIL tests. With VEOS, you can configure
and validate models, layouts and tests on a standard PC,
without any HIL hardware.
MotionDesk, like all other dSPACE software for HIL simulation, interacts with VEOS just like with a HIL simulator.
MotionDesk is perfect for visualizing simulations, and as
soon as the HIL simulator is available, simulation runs can
be started without unnecessary delays.
Property
grid
2-D scene
view
3-D library
2015
143
Scene
Navigator
n Various rendering techniques (wire frame, flat shading,

Gouraud shading, textured)
n Render modes selectable for whole scene and for individual objects
n Driver camera with realistic viewpoint (smooth follow
behavior)
n Scene statistics
Hardware
Realistic Visualization
n Connection of objects and model data streams via drag
& drop
n Simulation of changing weather conditions like rainfall,
fog, and snow
n
Simulation of different light conditions and shadows
n Freely configurable observers that can follow movable
objects with different behaviors
n Intuitive operation
n Support of multichannel visualization with highest
graphical requirements (p. 153)
n Optional: Import of road networks and predefined
sceneries from dSPACE ModelDesks Road Generator
n Examples: country roads, tree-lined roads, and
urban areas
n Automatic 3-D scenery generation in MotionDesk,
including road embankment or border area, tree
spacing, reflector posts, street lights, building
types, etc.
n Fine adjustments in MotionDesks 3-D Scene Editor
Engineering
3-D Animation of Simulated Mechanical Systems

n Lossless, time-based data acquisition with time stamps
n Synchronized replay of different simulations in multiple tracks
n Replay function with faster/slower replay speeds
n Up to 500 movable objects
n Data acquisition from DS1005 PPC Board, DS1006 Processor Board, DS1007 PPC Processor Board, DS1103 PPC
Controller Board, MicroAutoBox I and MicroAutoBox II
n Data acquisition from running Simulink simulations
n Runs on the host PC (p. 152), separate PCs (p. 153), or
VEOS (p. 100)
n File-based recording and analysis of motion data
n Video file generation (e.g., AVI, MPEG-4) to export
MotionDesks animations to high-quality video files
Optimized for Driver Assistance Systems

MotionDesk provides enhanced support for all aspects of
advanced driver assistance systems (ADAS), where the complexity of an action has to be seen to be understood. When
camera-based ADAS systems are tested, the simulation must
NEW: Pedestrian Detection

A critical part of ADAS systems is the real-time detection of
pedestrians via camera. Pedestrians are hard to recognize,
especially in cities or obscure corners, where colors, forms,
and motion make precise detection much more difficult
than on a highway. ADAS pedestrian detection uses neural
networks which are trained on the basis of real data. This
NEW: International Traffic Signs

The new traffic sign add-on to MotionDesk lets you extensively test traffic sign recognition and visualization. It includes
the complete German traffic sign catalog and all the most
144
be realistic enough for object recognition, and a high frame

rate is crucial. MotionDesk can simulate changing weather
conditions, such as rain and snow, and offers highly realistic
shadow visualization.
means that pedestrian detection also recognizes road users through their motion behavior and draws important
conclusions on the road users possible motion trajectories.
To test pedestrian detection systems via simulation, MotionDesk provides the Animated Characters module which
includes animated pedestrian models that show realistic
human appearance, behavior and motion. Besides this, the
Animated Characters module also visualizes animals and
wheeled persons, such as wheelchair users and cyclists.
This way, sensitive pedestrian detection systems do not need
to be tested completely on test tracks. They can also be tested
in the laboratory through visualization with MotionDesk its
flexible and tests are fast to reproduce. Thus, MotionDesk
makes an important contribution towards achieving the next
level of required safety standards on pedestrian detection
(such as NCAP).
important traffic signs from China, Japan and the United

States, with more than 700 traffic sign models.
2015
Introduction
Application Fields
Outlook: Car2x Systems

Future versions of MotionDesk will continue to support
the development of Car2x systems, such as collision avoidance, intersection management, and other communicationsenabled vehicular safety systems.
n Numeric instrument, e.g., showing forces that affect

the vehicle
n Gauge instrument, e.g., speedometer or engine speed
n Bar instrument, e.g., showing the filling level
n LED instrument, e.g., selected gear or indicator
Software
Instruments
MotionDesk has several instrument types for observing the
values of simulation variables. In MotionDesks Scene Viewer
you can attach instruments to movable objects or give them
static positions in a scene. You can also specify several instrument properties such as the size, position and color. The
following instrument types are available:
2015
145
Engineering
Hardware
The instruments can be placed inside or outside the vehicle.
Hand-in-Hand with ModelDesk

ModelDesk and MotionDesk work together hand-in-hand in
a tool chain. ModelDesks Road Generator (p. 263) lets you
define scenes for the automatic generation of 3-D sceneries
in MotionDesk.
ModelDesks Road Generator is the graphical user interface
for defining road networks and sophisticated road features.
Roads can be assembled from geometric segments or imported. The road design interacts closely with MotionDesk
to define the environment. The Road Generator is ideal for
creating complex traffic scenarios for the development and

test of advanced driver assistance systems (ADAS).
For example, you can define country roads, tree-lined roads
and urban areas, and completely parameterize them with
a road embankment or border area, tree spacing, reflector
posts, street lights, building types, and so on.
Fine adjustments can be done afterwards in MotionDesk
and its integrated 3-D Scene Editor (p. 147).
A scene defined in ModelDesk and

automatically generated in MotionDesk.
3-D Authoring: Creating a Virtual World

Integrated Tools
MotionDesk gives you a complete 3-D authoring package
so that you can create virtual worlds easily. You can choose
objects from libraries and import 3-D data from 3-D CAD applications. The comprehensive library of 3-D objects lets you
set up scenes very fast by simply selecting and positioning
the objects. A 3-D Library Browser helps you find the objects
146
you need, for example, by keyword search. Expanding the

library is easy, as the 3-D object geometries are described
in the COLLADA standard. Road geometries for automotive
applications can be generated automatically, using vehicle
dynamics models such as the dSPACE ASM Vehicle Dynamics
Simulation Package.
2015
Introduction
Software
n 3-D editor for assembling a scene from 3-D objects

n Interactive graphical scene design
n Scenes observable from any viewpoint
n Easy, intuitive mouse navigation through scenes
n Open, extendable 3-D object library
n Geometry objects in COLLADA standard (VRML2
geometries imported into the 3-D object library by 3-D
Library Manager)
n dSPACE object library of miscellaneous objects for
building a virtual world: ground plates, sky domes,
houses, trees, etc.
n Library of generic objects and robotics objects

n Custom library of 3-D objects
n 3-D Library Manager for importing and coloring objects
n Object library management by grouping or by keywords
n Positioning, rotating and scaling 3-D objects in any
direction (graphically via mouse, or by editing the
property values)
n Wide range of textured, real-time-capable objects for
vehicle dynamics simulation: chassis, wheels, roads, etc.
n Each object can have its own render mode
Application Fields
Integrated 3-D Scene Editor

With the Scene Editor, you can create your own scenes for
running 3-D animations of simulated data.
Hardware
Assembling a Scene
To assemble a scene, just drag the
objects from the 3-D object library
to the scene and move them to the
correct positions. For very realistic
animations, you can use atmospheric settings such as light and
fog to reduce the visibility range and
obscure objects that are far away.
Automation API
MotionDesk can also be remote-controlled from other tools,
such as dSPACEs ModelDesk, via a publicly available automation interface. External tools can create a scene and
add objects to it, start or stop the simulation, and switch
to full screen mode.
Animation with MotionDesk

Once created, a 3-D scene comes to life in MotionDesk.
dSPACE Simulator provides the motion data, and MotionDesk moves the 3-D objects in the scene accordingly. For
example, when a car is simulated, the motion of the chassis
is displayed with four individually rotating wheels, including
force vectors visualizing the forces between road and wheel.
In MotionDesk, you can adjust the transformations, scalings,
colors, and render modes of the objects.
2015
147
Authoring at a Glance
n 3-D scenes assembled from 3-D library objects by
drag & drop
n Templates for complete sceneries
n Comprehensive automotive object libraries
n NEW: International traffic signs (optional)
n Import customized 3-D objects and graphics
Engineering
3-D objects, like the traffic signs shown here, are added to a scene by simple drag & drop.
Then you can edit them to modify their size, position, rotation, and other attributes.
Multitrack Mode
Three different strategies for a driving maneuver lead to three
different simulations. You can visualize the three simulations
together in one animation by using a different color for each
simulation.
Multitrack mode lets you replay several simulations synchronously.
Animations can be overlaid via rendering techniques.
148
Main Features
n Synchronized replay of several simulations
n Transparent overlaying of objects
n Equidistant time stamps
Typical Applications
n Parameter behavior studies
n Reference comparisons
Comparisons
The multitrack mode in MotionDesk is a smart way to visualize simulations, allowing you to integrate several simulations
in one single animation. The method is ideal for reference
comparisons and in all cases where strategies for a particular
maneuver need to be assessed. For example, different vehicle
dynamics strategies can be compared with one another in
the specification phase, and later, actual results can be tested
against a reference. This is also an ideal way to document
results visually.
Technology
To replay several simulations synchronously, MotionDesk
offers two important features:
n Time stamps for simulation data
n Several replay tracks
You can synchronously replay any simulations that are recorded on the same time basis. The animated objects can
be cloned as required and assigned to different tracks. You
can also give the objects different colors and render modes
so that the individual simulations are clearly distinguishable.
Track Generation
The tracks are created in MotionDesks Scene Navigator.
Track generation automatically creates clones of the movable objects and observers in the scene.
Data Sources
Tracks can receive their data from different sources.
n Online simulation
n Simulink offline simulation
n Stored simulation (MDF files)
If simulations from different sources need to be compared,
they all must use the same time basis.
2015
Introduction
Maneuver Comparisons
Application Fields
replays data from previous simulation runs. These tracks also

contain clones of the moving objects defined for reference.
Synchronized replay makes it easy to pick the best strategy
for your control application.
Braking on a Split- Surface

The same maneuver is shown with and without Electronic
Stability Program (ESP). MotionDesk displays the two different simulations in one animation.
Software
The red car and the yellow car are on track at the beginning of the
maneuver. The red car is equipped with ESC, the yellow car is not.
Hardware
Both cars brake on a partially slippery surface (split).

The yellow car starts skidding and turning.
Engineering
At the end of the maneuver, the red car is still on track,

but the yellow car turned around the yaw axis.
2015
149
MotionDesks multitrack mode makes maneuver comparisons easy and clear. It synchronously replays multiple simulations that have been assigned to different tracks. One
track acts as the reference, playing either online, offline, or
stored simulations. Each of the other tracks synchronously
MotionDesk Blockset: Model and Animation

Prepare for Animation
This blockset lets you run animations as early as the control
design stage. You can perform the usual ECU-based simulation and animation, and also check behaviors very early
The Blockset at a Glance

n Interface between simulation platform and MotionDesk
n Visualization of PC-based Simulink simulations
n Visualization of real-time simulations
n Support of simulation platforms: DS1005, DS1006,
DS1007, DS1103, SCALEXIO, MicroAutoBox, VEOS,
and Simulink
n Transformation blocks for easy description of the 3-D
objects positions and orientations
and create references. MotionDesk is therefore the ideal

tool to visualize certain features and their results at the very
beginning of a project.
n Single communication block with dialog pages to

easily configure data transfer
n Fast model initialization in Simulink
n Fast computation for real-time execution
n Kinematic chains (e.g., robot kinematics or wheel
motion in relation to the vehicle) created by connecting transformation blocks in Simulink
n Ready-to-use demo models for vehicle and robotics
n Easy connection of existing vehicle models via
kinematics block
Special blocks collect the motion data and time-stamp it in MotionDesk.
150
2015
Introduction
Connect 3-D Objects and Models
Application Fields
Transform State Variables

The MotionDesk Blockset provides Simulink blocks that
prepare the real-time model for 3-D animation and make
the data streams available in MotionDesk. During Simulink
simulations and real-time simulations, the Simulink blocks
directly transform state variables into the required 6 degrees
of freedom. This graphical form of programming obviously
makes the interconnections between the real-time model
and the 3-D objects extremely tangible, and modifications
are easy to carry out.
Hardware
Software
Coordinate Transformation
n Simulink blocks for 3-D coordinate transformation
n Convenient setup of kinematic chains
n Euler or Cardan angle interpretation
n Transformation from rotation to translation, and vice
versa
Connection to 3-D objects, data collection and transfer to MotionDesk:

all done in the Simulink blocks and dialogs.
can also synchronize animations to certain events which is

useful if you want to watch the animation only at a certain
speed or milestone.
Special blocks collect the motion data and time-stamp it
in MotionDesk.
2015
Engineering
Maneuver Synchronization with Multitrack Support

The blockset supports maneuver synchronization with all
data sources (dSPACE real-time hardware, VEOS, and Simulink simulation). At the beginning of a maneuver, you can
reset time stamps used for the animation to zero without affecting the current simulation time. This provides convenient
handling when new maneuvers start. In MotionDesk, you
151
Six Degrees of Freedom

Real-time models in Simulink use state variables, such as a
wheels steering angle or position in relation to the suspension. In contrast, 3-D animation requires a system with 6
degrees of freedom to determine the objects positions and
orientations in the 3-D world. The MotionDesk Blockset
lets you transform the state variables into these 6 degrees.
Typical Application: Automatic Driving Maneuvers

Control and Visualize
One typical application scenario is the visualization of automatic driving maneuvers calculated by dSPACE Simulator.
ControlDesk is used to control and monitor the simulation. ControlDesk and MotionDesk can run on the same
PC, since there is no need for interactivity with low latency
requirements.
ControlDesk
Next Generation
SCALEXIO
152
MotionDesk
Data Transfer
MotionDesk visualizes the simulation results in a 3-D scene.
dSPACE Simulator calculates the absolute positions and orientations of the movable objects for the visualization. Data
for ControlDesk and MotionDesk is transmitted from dSPACE
Simulator to the host PC via dSPACE link boards. To display

ControlDesk and MotionDesk on two separate monitors,
the graphics board must have two connectors (dual head).
Further Application Fields

MotionDesk supports a broad variety of applications. All
simulations can be visualized elegantly by importing the
appropriate 3-D objects. Outside of the automotive field,
further typical applications for 3-D animation include robotics

and flight simulation.
2015
Introduction
MotionDesk on Multiple PCs

ent views of the same scene at the same time. ControlDesk
and MotionDesk run on separate PCs, which improves the
visualization performance and provides the full functionality
and performance of both tools. Moreover, you can add any
number of MotionDesk PCs to set up a driving simulator with
several screens for the most realistic visualization.
Application Fields
Improved Visualization
MotionDesk is ideal for applications in which a human driver
controls a virtual car. Such tests are important if you want to
run not only a suite of automated tests, but also interactive
tests. The driver feedback obviously has to be highly realistic,
which requires a high frame rate and low latencies.
For even greater realism, MotionDesk provides scalable visualization for interactive driving, for example, displaying differ-
A typical multiPC setup (SCALEXIO) with MotionDesk: The human driver can see different views of the same scene simultaneously for greater realism.
2015
153
Engineering
Hardware
Software
Typical Application:
Interactive Tests by Man-in-the-Loop
A typical application example is man-in-the-loop simulation,
where the human driver sees multiple screens in an interactive driving simulator.
The same multiPC setup with a PHSbus system (for example, dSPACE Simulator). This requires the MotionDesk MultiPC Interface Kit.
MotionDesk MultiPC Interface Kit

Scalable Performance
n Required only for systems based on peripheral highspeed (PHS) bus technology
n Extension to MotionDesk for highest graphical
requirements
n ControlDesk and MotionDesk run independently on
different PCs
Connect Multiple PCs

The MotionDesk Multi-PC Interface Kit is an extension to
MotionDesk that enhances visualization performance and
allows the same experiment to be visualized from different
points of view and from different PCs. A typical application is man-in-the-loop: You cannot get the most realistic
impression of the simulation unless the driver sees different
perspectives of the scene, such as the front view, side view,
and rear view.
154
n Full ControlDesk functionality and maximum MotionDesk performance at the same time
n Scalable number of MotionDesk PCs for multichannel
visualization (e.g., for interactive test drives)
n Smart solution for setting up driving or flight simulators
n Synchronized animation start/stop on all MotionDesk PCs
Network Connection
The MotionDesk Multi-PC Interface Kit allows multi-faceted
visualizations by letting you connect any number of MotionDesk PCs in the real-time data stream. The hardware
is installed in your dSPACE Simulator. The connection to
the MotionDesk PCs is via Ethernet, so you only need an
Ethernet card in the PCs for high-speed data transfer and
minimum latencies.
2015
Software Details
n
Programmable via a network sender block
(included in MotionDesk Blockset))
System Requirements for

Same as MotionDesk, plus
n dSPACE Simulator (DS1005 or DS1006)
n 10 Mb/s Ethernet card for each connected PC
Software Requirements for

n MotionDesk for each PC
2015
155
Engineering
Hardware
Software
Hardware Details
n ISA bus board for providing the real-time data
(DS1005 and DS1006 supported)
n Ethernet connection between PCs
Application Fields
Introduction
Test Automation Software / AutomationDesk
AutomationDesk
Powerful test authoring and automation tool
Highlights
n
Graphical description of test routines
n
Advanced custom library concept
n
Automatic report generation
n
Support of HIL API-based simulator access
n
Remote control of calibration, measurement, and
diagnostic tools such as ControlDesk Next Generation

n
Offline test execution and development
n
NEW: Certified for ISO 26262 and IEC 61508
Application Areas
AutomationDesk is a powerful test authoring and automation tool for hardware-in-the-loop (HIL) testing of electronic
control units (ECUs). AutomationDesk users can create and
edit test routines in graphical format without requiring expert
knowledge.
Key Benefits
AutomationDesk provides libraries containing a large number of predefined test steps (e.g., for easy access to the HIL
simulator, to a Failure Insertion Unit (FIU), or to calibration
or diagnostics software). With AutomationDesk, tests can
be executed 24 hours a day, seven days a week, letting engineers increase test coverage and improve ECU software
quality while saving time and costs. AutomationDesk lets you
describe test routines graphically without expert knowledge
in programming.
Functionality
Description
Advanced Sequence Builder
Graphical test development

Test development via drag and drop
n Access to simulation platforms and tools from within the automation sequences
n
Test project management and execution
n
n
n
n
n
n
156
Structured project overview

Navigation in complex projects
Managing test projects, data, results and reports
Configuring test executions
Debugging graphical tests
Consistency checks before test execution
2015
Introduction
Functionality
Description
Automation libraries
n
n
n
Open architecture
n
n
n
n
n
n
Test documentation
Open COM API to remotecontrol test execution

Calling Python scripts from within AutomationDesk
Extendable libraries
Support of Microsoft Source Code Control (SCC) Interface to integrate version control systems
Robust implementation of interfaces to thirdparty tools via COM/DCOM supported by VirtualCom feature
XML import/export of projects, folders, tests, and custom libraries
Automated generation of test reports in PDF or HTML

Report library to define the contents of the generated report
Test Builder library
Highly customizable framework for test development
Evaluation library
Application Fields
ASAM HIL API library to access HIL simulators via the ASAM HIL API standard
Realtime stimulus, including replay of measurement data
Access to calibration tools like ControlDesk Next Generation, ETAS INCA and Vector CANape via the
ASAM MCD3 MC automation interface
Access to diagnostics tools like ControlDesk Next Generation and Softing DTS 7 via ASAM MCD3 D
(Version 2.0.2)
Access to MATLAB
Convenient access to tools in the dSPACE tool chain
n ControlDesk Next Generation
n Electrical failure simulation systems
n RealTime Test Manager
n RTI CAN MultiMessage Blockset
n ModelDesk
Software
Powerful evaluation of measured signals

n Automatic report generation including plotted signals
Product
Order Number
AutomationDesk
AUD_BASIC
AutomationDesk Automation Server
AUS_BASIC
PLATFORM_API
FAILURE_SIM_API
RealTime Testing
RTT
Hardware
Order Information
Order Number
Required
Operating system: www.dspace.com/go/os_compatibility
Optional
See p. 106
See p. 272
VEOS
See p. 100
AutomationDesk RTI CAN MultiMessage Library
RTICANMM_AUD_LIB
ModelDesk
See p. 261
2015
157
Software
Engineering
Relevant Software
NEW: Certified for SafetyRelated Applications According to ISO 26262 and IEC 61508
The latest version of dSPACE's test automation software,
AutomationDesk, has been certified by TV SD for testing safety-related systems according to ISO 26262 and IEC
61508. The TV SD certificate confirms AutomationDesk's
suitability for the development and testing of safety-related
systems in automotives, commercial vehicles, aerospace and
many other industries. It also confirms the high quality of
the development process and extensive quality assurance
performed for AutomationDesk 4.1.
AutomationDesk is the first hardware-in-the-loop test automation software product to be awarded such a certificate.
Together with the new AutomationDesk Safety Manual,
the certificate gives users a valuable support for validating and qualifying safety-related systems according to ISO
26262 and IEC 61508 and for using AutomationDesk 4.1
for developing and testing them.
IEC 61508 and ISO 26262

IEC 61508 is the internationally recognized generic standard
for the development of safety-related electronic systems.
ISO 26262, the standard for functional safety in passenger
vehicles, replaces IEC 61508 for the automotive industry.
AutomationDesks User Interface
Ribbons
Work-phase-related sets of
differently sized tool bars.
Start Page
New start page with links to
valuable information and
often-used commands
Favorites
Define your view of important
blocks in a separate view.
158
2015
Introduction
Module Overview
Application Fields
The modular packaging of AutomationDesk lets you select

the packages you need for your automation tasks, and add
other modules later on if necessary.
AutomationDesk
AutomationDesk
Basic Version
Versions
Platform
support
AutomationDesk
Automation Server
Basic Version
Software

Additional
functionality
Failure Simulation API Package (p. 178)
Real-Time Testing (p. 170)
n HIL API EESPort (Electrical Error Simulation port) in .NET
n
Python-based real-time test automation
(for dSPACE SCALEXIO)

n
Failure simulation API based on tool automation of

n
NEW: XIL API EES Port in .NET: Programming all
dSPACE and third-party failure insertion units in compliance with the ASAM XIL API EESPort standard
Engineering
Platform API Package (p. 176)

n
HIL API MAPort (Model Access port) implemented in
Python: Interface to ASAM HIL API-compliant simulation platforms
n
HIL API MAPort implemented in .NET: Interface to
ASAM HIL API-compliant simulation platforms
n
RTPLIB2: Interface to dSPACE HIL platforms
n
Platform Management API: Interface to configure
dSPACE platforms
n
NEW: XIL API support in .NET: Programming interface
that complies with the new ASAM XIL API standard
n
100% reproducible real-time tests executed synchro-
nously with simulation model

n
Easy integration into user-defined test frameworks
(AutomationDesk or others)
n
Support of VEOS, dSPACEs platform for PC-based
simulation
2015
159
AutomationDesk Automation Server (p. 169)

The AutomationDesk Automation Server, an alternative to
the full version of AutomationDesk:
n
Tool variant without a graphical user interface
n
Parameterization and execution of existing tests
n
Example client applications are SYNECT, batch scripts
in Python, and customized operator UI applications
Hardware
Real-Time Testing
AutomationDesks Sequence Builder

Graphical and Python-Based Test Development
AutomationDesks Sequence Builder provides a graphical,
UML-compliant environment for developing automation
sequences. The Sequence Builder and its overview panel help
you keep track of even very large sequence structures. AutomationDesk combines and integrates graphical and Python-
based test development. Typically, graphical development

is used to describe the control flow and to access devices
like hardware or other software. Python scripts are used
for implementing algorithms or for user-specific extensions.
Editor for
Pythonbased
test steps.
Developing and managing automation

sequences with AutomationDesk.
Reusing Automation Tasks

If a test sequence or single test steps need to be reused for
similar automation tasks in other projects or sequences, they
can be stored in custom libraries. Custom libraries gradually
grow to contain more and more reusable elements, so you
benefit from accumulated know-how in future projects.
This method speeds up the test development process and
increases efficiency. Different custom libraries can be shared
between different AutomationDesk installations via the file
system or via a version control system.
Create your own custom libraries for
tests and basic test steps.
Test Builder and Framework Builder

Test Builder is a highly customizable test framework custom
library. It offers a ready-to-use test framework with test and
test step templates, including exception/verdict handling
and reporting. The Test Builder elements are implemented
using the Framework Builder library.
160
n
Ready-to-use test framework
n
Test and test step templates
n
Implicit reporting
n
Standard HTML and PDF style sheets for detailed and
brief reports
n
Exception and verdict handling
n
Based on Framework Builder
n
Highly customizable and transparent
2015
Introduction
Test Debugging and Data Comparison

Debugging Test Sequences
If an error occurs during test execution, AutomationDesks
Debugger makes it easy to find its source. You can insert
breakpoints into your test sequence and make the test execution stop automatically at these points in debug mode.
You can then go through the test case step by step, analyze
complex hierarchical test steps in depth or execute them as
a whole. The current variable values are always visible and
can be changed during the debugging process to ensure
that the tests run with correct variables. Step-by-step execution supports fast, efficient error-finding because you can
investigate specific potential error sources.
Breakpoint
Application Fields
Current position of
the Debugger
Breakpoint
Software
The Debugger lets

you go through your
test sequence step
by step.
The toolbar of AutomationDesks Debugger.
Hardware
Disabling Tests and Test Steps

AutomationDesk considerably simplifies the verification of
test sequences during their development. You can disable
single test steps or sequences by commenting them out.
This is extremely helpful in identifying errors.
The recorded data can be compared to the reference data.
2015
161
Evaluating Data with the Evaluation Library

With AutomationDesk's Evaluation library, you can analyze
recorded data and compare it with reference data. This helps
you to find values that exceed or are below the defined limits. For example, you can specify upper and lower bounds to
evaluate whether a specific signal is above or below them,
outside a gap or inside a corridor. The signal, the reference
signal, the bounds and the evaluation result are plotted and
reported automatically.
Many other kinds of signal manipulation are also possible:
n Binary operations (addition, multiplication, less than, etc.)
n
Calculating gradient and integral
n
Shifting, cropping, and resampling signals
n
Calculating minimum value, mean value, minimum
delta x, etc.
Engineering
Disabling test steps.
Test Project Management in AutomationDesk

Managing Project Data
AutomationDesks Project Manager is the ideal way to organize the sequences, data, and results of test projects.
Tests are reproducible so they can be executed repeatedly
to perform regression testing, for example. Tests can be arranged according to the functions under test, the ECUs in
a network, the development stages, and the users involved
in a project.
Project Manager in AutomationDesk.
Offline Test Execution & Development
AutomationDesks libraries can be set to offline mode, so
that tests that use them are executable even if required external software or hardware is not available. The test steps
then use default behavior to enable test execution. For example, tests can be executed when no hardware-in-the-loop
simulator is connected to AutomationDesk. You can define
the return values for the default behavior yourself, or record
them in an online test execution run.
Automatic Report Generation

AutomationDesk can automatically generate report documentation based on the test results. You can select from
a library of report test steps (such as AddText, AddTable,
or AddPicture) to specify the report's contents. The report
begins with statistics on all the test results. You can produce
a detailed report, or a brief report that helps you judge the
current quality of an ECU at a glance. Additionally, there
are various options for controlling the level of detail and the
format of the reports. Reports are usually generated in HTML
or PDF format, but almost any kind of output format can be
generated with user-defined XML style sheets.
Version Control of Projects and Custom Libraries

With the AutomationDesk version control interface, you
can integrate version control systems that have the Microsoft Source Code Control (SCC) interface, such as MKS
Source Integrity, Apache Subversion (SVN)1), or IBM Rational
ClearCase, etc.
162
2015
1)
Libraries in AutomationDesk.
The Test Builder report provides a clear and structured

overview of all test cases.
Version control interface.
Requires an installation of the SCC API plug-in from PushOk Software.
n
ODX-based diagnostics
n
Calibration and diagnostic functions based on
ControlDesk Next Generation tool automation

n
ControlDesk Next Generation Access Library
n
Convenience blocks for diagnostics
n

Convenient access to fault memory, e.g., Direct
Application Fields
n
Complies with ASAM MCD-3 MC
Diagnostics and hardware-in-the-loop (HIL) testing are

brought together in AutomationDesk. You can use it to
remote-control and automate the diagnostics functionality of ControlDesk Next Generation, dSPACEs universal
experiment software. This means you have a completely
integrated tool chain for HIL testing, ECU calibration,
measurement tasks, and diagnostics from a single source.
Compatibility problems are a thing of the past.
Read DTCs, Direct Clear DTC, Direct Clear All DTCs
Hardware
Software
AutomationDesk can be used to automate

AutomationDesk
and remote-control ControlDesks ODXRemote
Remote
ControlDesk
based diagnostic functionality, and to auCalibration (COM) Diagnostics (COM)
Next Generation
Library
Library
Access
tomate measurement and calibration tasks.
It accesses ControlDesk via the ASAM MCDASAM MCD-3 MC
ASAM MCD-3 D
Tool Automation
3 automation interface or, far more conveMCD-3 Automation Module
niently, via ControlDesk Next Generation's
Basic
ASAM MCD-2 MC
ASAM MCD-2 D
tool automation library. You can build test
(ASAP2)
(ODX)
ECU
ECU
sequences graphically in the familiar way in
Interface
Diagnostics
Database
Database
AutomationDesk, using the Remote DiagnosModule
Module
tics (COM) library or the Remote Calibration
Diagnostic protocol, e.g.
interfaces or protocols,
Unified Diagnostic Services (UDS),
e.g., CCP, XCP, ...
KWP2000 on CAN,
(COM) library. These are AutomationDesk
KWP2000 on K-Line
libraries of test steps for automating access
to ControlDesks diagnostics, measurement,
and calibration functionalities.
Application example: AutomationDesk and ControlDesk Next Generation with the
It is increasingly important to successfully inMCD3 Automation Module, the ECU Interface Module, and the ECU Diagnostics
Module for ECU access via calibration and diagnostic interfaces during test automation.
tegrate ECU diagnostics into the hardwarein-the-loop (HIL) testing of ECU software.
AutomationDesk is a standard solution for automated HIL
solutions) DiagRA from RA Consulting; and measurement
testing that can address a variety of software tools. These
and calibration tools like INCA from ETAS or CANape from
include ControlDesk Next Generation and DTS from Softing
Vector, which comply with the ASAM MCD-3 MC standard.
(standard AutomationDesk), but also (based on engineering
All Tools from One Source

By using ControlDesk Next Generation and AutomationDesk,
you avoid the compatibility problems that often arise when
tools from different vendors have to be integrated. dSPACE
offers you HIL systems plus measurement, calibration, and
1)
Engineering
1)
diagnostic tools from a single source, with no complications.

The smooth interaction between AutomationDesk and ControlDesk gives you maximum convenience and functionality
for successful HIL testing.
It is also possible to access dSPACE hardware (this requires the Standard Platforms Module,
Please see product information "ControlDesk Next Generation").
2015
163
n
Complies with ASAM MCD-3 D (Version 2.0.2)
Introduction
Automated HIL Testing, Diagnostics & Calibration

from a Single Source
Test Automation
Well-Planned Libraries for Reusability
To run HIL test systems efficiently in terms of time and cost,
test automation has to be planned carefully. Sometimes
thousands of relevant tests have to be defined and handled,
possibly even years before start of production in the case
of safety-critical systems.
Building a Good Library Concept for Test Automation

dSPACE Engineering Services have years of experience in
creating library concepts.
So when you build your library concept, you can call on our
Engineering Services to help you get started in test automation. The dSPACE engineers will help you set up a test
automation infrastructure, including the library concept.
You will benefit from their knowledge of the hardware and
software and accumulated project experience.
The objective is to create basic test steps, save them to

libraries and reuse them for other tests.
This is achieved by generic, nonredundant basic test steps,
combined with a suitable library concept. These can be
reused for example, for subsequent vehicle generations
with only few modifications.
The services include:

n
Defining test processes
n
Project implementation
n
Resident engineers
n
Creating the test template
n
Creating the library concept
n
Example test implementation
n
Data and result management
n
Integrating third-party software
n
Connecting the test software to existing tools
Number of tests
Test creation with

library concept
Test creation without
library concept
New simulator
or new vehicle
Work time
Create basic
blocks
Create tests
Create tests
164
Adapt
library
Adapt all tests
Create tests
Create tests
Adapt
library
Create ttests
Adapt all tests
Create tests
Adapt
library
Adapt all tests
Create tests
st
Create tests
Working without a library

concept gives you quick
results but is not efficient
enough in the long term.
The initial investment for a
good library concept pays for
itself in terms of efficiency
and cost-savings.
2015
Introduction
Tool Interfaces
Support of HIL API Standard
Application Fields
Software
HIL API/XIL API Support in Failure Simulation API

Package
n
XIL API EES Port in .NET: Programming all dSPACE
failure insertion units in compliance with the ASAM
XIL API EESPort standard
Hardware
HIL API/XIL API Support in Platform API Package

AutomationDesks Platform API Package supports the MAPort implementation of the HIL API standard to access a
simulation platform:
n
Configure the simulation platform
n
Read and write to scalar and vector type variables
n
Capture data by using complex trigger conditions
n
Stimulate variables of a real-time application using a signal description set, such as the Signal Editor Module in
n NEW: XIL API support in .NET: Access the simulation model
via a programming interface that complies with the new
ASAM XIL API standard
Engineering
The HIL API standardizes the following aspects:

n
Access to HIL simulators
n
Access to electric failure simulation
n
Access to ECUs for measurement and calibration tasks
n
Access to diagnostics
Advantages for Users

The Platform API Package for
AutomationDesk supports Version 1.0.2 of the HIL API standard. The dSPACE test automation software makes it easier to
use tests with any HIL simulator.
This increases test reuse, helping to protect investments and
reduce development costs and
time. Moreover, you only have to
buy one program and learn how
to operate it even if you want
to access different simulators.
HIL API Vendor Switch
HIL API Convenience Library
n
Easy switching between vendor-specific HIL API imple-
n
Quick, convenient HIL-API-based operations detailed
mentations
n
Convenient exchange of object models from different
vendors
HIL API background information not required

n
Easy handling of read/write/capture/signal generator
actions
2015
165
Independence from Specific Simulation Hardware

In July 2009, ASAM (Association for Standardisation of Automation and Measuring Systems) released the new HIL API
standard, defining an interface to connect test automation
tools like AutomationDesk with any hardware-in-the-loop
(HIL) system. The standard enables truly platform-independent test development.
Interfaces to dSPACE Tools

Convenient, comprehensive access to all ControlDesk Next
Generation features for:
n
n
Diagnostics
n
Failure simulation / failure insertion
Real-Time Testing
n
Real-Time Testing library for convenient script management
n
RTI CAN MultiMessage Custom Library
n
Solution to access RTI CAN MultiMessage Blockset functions from within AutomationDesk
n
Convenient access to RTI CAN MultiMessage Blockset parameters (ECU name, message name, signal name, etc.) and
manipulation options
n CAN bus configuration via AutomationDesk blocks: save,
restore and manipulate RTI CAN MultiMessage properties
ModelDesk
n
ModelDesk access library available on request
n
ModelDesk tool automation as preparation for ADAS
tests
n
Remote control of ModelDesk to handle parameters,
roads, maneuvers and traffic
n
Open project/experiment
n Activate parameter set
n
Access to parameter handling, e.g.:
n
Modify parameters
n Download parameters
n
Access to road and maneuver handling , e.g.:
n
Activate and download roads
n Activate and download maneuvers
n
Modify road and maneuver parameters (surface
conditions, velocities)
Interfaces to Third-Party Tools

AutomationDesk can also integrate third-party tools, such as
CANscope, CANstress, and CANalyzer from Vector. Please
contact dSPACE for details on supported third-party tools.
dSPACE also has experience in connecting AutomationDesk
to third-party hardware-in-the-loop systems, provided they
support the HIL API standard properly, and offers engineering support on request.
ASAM interface
n
Access to calibration tools like ControlDesk Next
Generation, ETAS INCA, and Vector CANape, via
ASAM MCD-3 MC
n
Access to diagnostics tools like ControlDesk Next
Generation, and Softing DTS 7 via ASAM MCD-3 D
MATLAB
n
Access to the MATLAB Command Window
n
Data exchange between AutomationDesk and MATLAB
n
Remote execution of MATLAB commands
n
Use of M and MAT files
166
2015
Introduction
Integration of AutomationDesk in Typical Tool Chains

Connection to dSPACE SYNECT
test results, etc.) it also handles data dependencies, versions
and variants, as well as links to the underlying requirements.
SYNECT Test Management is a SYNECT module which gives
you a convenient connection to AutomationDesk.
Application Fields
SYNECT is data management and collaboration software

that focuses on model-based development and ECU testing.
Designed to help you manage data throughout the entire
development process (models, signals, parameters, tests,
Test specification and management

in SYNECT Test Management
Input

Execute
Test
Steps
Software
Requirements
Results
Test implementation and execution

in AutomationDesk
Hardware
Tests
AutomationDesk
2015
Engineering
Importing Requirements, Specifications, and Tests

You can import existing tests into SYNECT Test Management
to define your tests. You can source data from several tools:
n
Test lists from Microsoft Excel
n
Test implementations from AutomationDesk,
BTC EmbeddedTester, MATLAB, or Python
Test Planning and Execution

SYNECT Test Management easily integrates with test automation tools such as AutomationDesk from dSPACE and
BTC EmbeddedTester. It does this via adapters that control
the test automation tool.
To carry out tests, you can set up execution plans containing test cases and add tests to them. An execution plan is
a list of tests that have to be executed. It can be based on
various criteria: For example, it can include all your tests for
one variant or for one ECU function.
167
Off-the-Shelf Integration with AutomationDesk

You can use implemented test cases in AutomationDesk
projects or libraries as a source for test cases in SYNECT
Test Management.
RemoteControlled Test Runs

COM/DCOM Interface
AutomationDesk has a COM-based application programming interface (API) for remote-controlling and automating
selected AutomationDesk functions. These are some of its
typical use cases:
n Programming batch processes (with Python, Visual Basic,
C++, etc.): You can program flexible control structures
which skip single test sequences if necessary or execute
test projects successively.
n Designing interactive user interfaces: You can create your
own test UIs, for example, to reduce complexity.

n Connecting other tools to AutomationDesk: For example,
parameterize your test data, in Microsoft Excel, and call

the AutomationDesk test sequences from Excel.
Example of a client application for test execution via

the COM/DCOM interface.
XML Test Exchange Format

AutomationDesk supports the import and export of projects,
folders, tests, and custom libraries as XML files. Using XML
to import and export test descriptions means that tests can
be exchanged between different test tools. For example, to
be imported from a third-party tool or from a proprietary
test description, a test simply needs to be converted into
AutomationDesk's XML format.
Use Cases
XML files open up numerous new application options, such as:
n
Reading and reviewing tests without AutomationDesk
n
Converting tests into different file formats
n
Migrating tests that were created with proprietary tools
into AutomationDesk
n Generating tests from third-party tools, such as Microsoft
Excel, and integrating them into AutomationDesk
Excel
AutomationDesk
Third-party or
proprietary test
description
Converter/XSLT
style sheet
Excel-to-AutomationDesk
converter
Export
Import
168
AutomationDesk
XML
2015
Introduction
AutomationDesk Automation Server
AutomationDesk
Automation Server Basic Version
Development environment for tests
Tool variant without graphical user interface
Developing libraries
Test execution
Planning, parameterizing and executing

existing tests
Note: To access a platform, you need

the Platform API Package
Client applications: batch scripts, Excel,

operator UI, test management tools like
SYNECT Test Management, etc.
Hardware
Software
AutomationDesk
Basic Version
Application Fields
AutomationDesk Automation Server, an alternative to the

full version of AutomationDesk, is a server variant without a
graphical user interface. The Automation Server is accessed
and remote-controlled via the COM/DCOM interface, so
the same functions are available as for the full version of
AutomationDesk. This run-time version has the advantage
of reduced license costs, making it useful wherever the comprehensive functions of the full version are not required, for
example, in automated test execution on hardware-in-theloop simulators.
2015
169
Engineering
AutomationDesk
AutomationServer
Test Automation Software / RealTime Testing
RealTime Testing
Pythonbased realtime test automation
Highlights
n
100% reproducible real-time tests executed synchro-
nously with simulation model

n
Several independent test scripts can be executed
concurrently
n No model modification necessary for real-time testing
n
n
Support of VEOS, dSPACEs platform for PC-based
offline simulation
Key Benefits
Automated testing is usually performed by executing tests
on a standard PC connected to the hardware-in-the-loop
(HIL) system. However, this method often cannot cope where
greater timing precision is required for example, if ECU
interaction has to be captured and responded to in a range
of milliseconds. Real-Time Testing with its Python scripts for
real-time testing is the answer. The scripts run on the processor
board of the HIL system in real time, i.e., synchronously with
Example Use Cases for Real-Time Testing

n
Testing reactivity in a range of milliseconds
n
Time-precise stimulation of several model signals
n
Time-precise measurement of model changes
n Reliable determination of minimum and maximum values
of model variables
n
Python-based CAN restbus simulation
n
Exact replay of recorded bus communication
(for example, CAN data replay)
n
Parallel execution of several ECU tests independently
the model, so all test actions are performed on a real-time

basis 100% reproducibly. This opens up expanded test options with dSPACE Simulator. Reactive tests which respond to
changes in model variables within the same simulation step
can be implemented. Time measurements in tests are also
far more precise, as there are no latencies in communication.
Simulation step size is now the only limit to the maximum
time resolution of measurements.
MicroAutoBox
HIL Simulator
*.py
*.py
*.py
170
Realtimecapable Python interpreter

for processor board and MicroAutoBox.
Simulation Model
Real-Time Scripts
2015
Introduction
Test Automation Software / Real-Time Testing
Functionality
Description
Real-Time Testing
n Real-time test management by scripting and dedicated graphical user interface

n Real-Time Testing library in AutomationDesk for convenient script management
n Model variables can be observed and changed in every simulation step
n No model modification necessary for real-time testing
100% reproducible real-time tests
n Executed synchronously with simulation model
Application Fields
n Real-time tests implemented in Python 2.5 (user-extensible via libraries)

n Several independent test scripts can be executed concurrently
n Dynamic test loading during model and test execution
n Easy integration into user-defined test frameworks (AutomationDesk or others)
Easy integration
n CAN support of real-time tests (based on RTI CAN MultiMessage Blockset)

n Use of MAT file data located on host PC for real-time stimulation of model variables
n Python objects can be easily exchanged between real-time tests and the PC Python script
n Available for DS1005 PPC Board and DS1006 Processor Board, SCALEXIO (for single-processor and
multiprocessor systems), and MicroAutoBox

n Support of VEOS, dSPACEs platform for PC-based offline simulation (p. 100)
n NEW: Support of multi-model scenarios in VEOS (see p. 100)
Real-time testing with Python scripts
n Python tests executed synchronously to simulation model
Software
n Read and write access to model variables in every simulation step

n Concurrent execution of several independent test scripts
n No need to modify the simulation model
Relevant Software
AutomationDesk
Real-Time-Capable Python Interpreter

A real-time Python interpreter, running on the processor
board along with the model, allows the script to execute
synchronously with the model. The interpreter can execute
several real-time tests simultaneously and independently of
one another. The tests can interact with the simulation model
in real time via the memory on the processor board. You can
therefore observe and influence the ECUs connected to the
HIL simulator in each individual simulation step.
The Python interpreter is added to the application during the
translation process via a Simulink CoderTM (formerly RealTime Workshop) build option. You can formulate real-time
tests using standard Python scripts from the real-time testing
libraries (for example, for accessing model variables and
executing several test branches within one real-time test in
parallel). You can also create your own Python libraries and
reuse them in several tests. The tests you have created can
be loaded from the PC to the simulators processor board or
See p. 100
See p. 156
Hardware
VEOS
MicroAutoBox and executed regardless of whether another

a real-time test is already running. Even though executing
the real-time tests requires additional memory capacity and
computing time, it is no problem to implement typical test
scenarios. On HIL processor boards, they even run in parallel
to complex engine and vehicle dynamics models, at simulation step sizes of 1 ms.
Managing real-time tests with the Real-Time Test Manager.
2015
Engineering
Optional
Order Number
171
Software
Real-Time Observer
A common test case is the detection of an event generated
by the real-time model. An event is specified by a condition
referencing one or more real-time model variables. As soon
as the event has been detected, a test action is triggered in
the same sample step. In this example, the real-time script
observes the speed of a simulated vehicle and reacts by
performing an emergency stop maneuver immediately when
the vehicle speed exceeds 80 km/h. This test case can be
easily implemented by a real-time Python script. The condition is observed continuously within a While loop. The yield
command pauses the test execution, which resumes in the
next simulation step. This means the script can easily be
time-controlled. When the speed exceeds 80 km/h, the While
loop is left, and the brake maneuver is initiated by setting
the associated model parameter in the same simulation step.
velocity
80
60
40
20
0
t
t detect
brake_pedal
100
75
50
25
0
t
t detect
from rttlib import variable

velocity
= variable.Variable(rModel Root/Velocity/Out1)
brake_pedal = variable.Variable(rModel Root/Brake/Value)
def MainGenerator():
while(velocity.Value <= 80.0):
yield None
brake_pedal.Value = 100.0
Implementing a real-time test in Python.
172
2015
Introduction
Application Fields
The script links data vectors in the file to the target parameters in the model. For example, if the real-time test
requires data to be replayed exactly 50 ms after a specific
CAN message is received, a simple replay command in the
Python script triggers the real-time-capable data transport
from the PC to the real-time so that the data is replayed in
time. The automatic load mechanism supports the replay
of large data volumes, such as test drive log files that are
several hundred MB in size. Several replay processes can run
simultaneously, and they can all be controlled independently
of one another. In a multiprocessor system, it is even possible to stimulate on several subnodes time-synchronously.
Software
Implementing Real-Time Stimulus

In many test scenarios, recorded data for ECU stimulation
has to be replayed with correct timing. For this, Python
real-time scripts can perform precisely timed stimulus generation on predefined model variables. One example is a
sine generator that can be implemented by means of the
standard sine functionality of Pythons math module (see
scripting example).
implemented by means of the standard sine functionality of
Pythons math module (see scripting example).
Recorded measurement data can also be replayed via an intelligent load mechanism, in which the Python real-time script
references a recorded file (MAT file) on the PC's hard disk.
2015
173
Engineering
Hardware
Example of a real-time script that triggers a sine

generation.
Implementing CAN Restbus Simulation

To program CAN restbus simulation, Real-Time Testing is
conveniently integrated with the RTI CAN MultiMessage
Blockset. The blockset contains an option for preparing
CAN access for Real-Time Testing, so that real-time scripts
are able to send and receive CAN messages with freely
definable CAN IDs and contents. This makes it very easy to
test case-specific restbus simulation. These dynamic restbus
parts (like ECU-specific CAN test messages) can be loaded
and executed on the real-time hardware as required and
no longer need to be a static part of the simulation model.
An example test scenario (see picture below) is the monitoring of an analog input signal. When a defined trigger threshold (for example, 14.7 V) is exceeded, a predefined CAN
message is sent cyclically every 50 ms until the value goes
below the threshold again. Another application example is
taking CAN communication that was recorded during a test
drive and replaying it in the laboratory with correct timing.
Input_Voltage [V]
20
15
14.7 V
10
5
50 ms
50 ms
0
CAN-Msg #1 CAN-Msg #2 CAN-Msg #3
t = 500 ms
t = 550 ms
t =600 ms
A real-time script continuously evaluates a model variable

and reacts by sending cyclic CAN TX messages.
1. Import real-time testing libraries (CAN MultiMessage Library, etc.)

2. Generate the variable object of the voltage to be monitored
3. Select the CAN send controller
4. Define the send message with the real-time test
5. Help function for precise time measurement (for later
transmission of CAN messages at exact time intervals)
6. Real-time test sequence: Check the voltage once per simulation step and react by sending a cyclic CAN message.
Implementation of a CAN test scenario.
174
2015
by the Python test scripts during model run time, instead

of being created statically in advance by the modeler. Local
and remote variables can both be accessed during testing:
It is sufficient to specify the unique MP variable path. This
ensures that the real-time tests can be executed on different
MP nodes without modifications. They are implemented
once and run everywhere.
Application Fields
Implementing Real-Time Tests for Multiprocessor

Systems
Today, HIL integration tests are executed on multiprocessor
(MP) systems where submodels for the engine, transmission,
restbus simulation, etc., are distributed across several processor boards to ensure real-time capability. Real-Time Testing
provides transparent variable access in the MP system so that
real-time scripts can be implemented independently of the
structure of the HIL model. The communication channels
needed between the processor boards are set up dynamically
Introduction
Hardware
Software
Real-Time Test Library in AutomationDesk

AutomationDesk includes a block library for convenient
handling of real-time test sequences. The library lets you
automate your management of Real-Time Testing (RTT) tasks
with the data objects and test steps of the AutomationDesk
Real-Time Testing library. This is the key to integrating RealTime Testing into your existing graphical test environment.
2015
175
Engineering
Real-Time Testing library in AutomationDesk.
Test Automation Software / Platform API Package

Application programming interfaces for connecting to dSPACE platforms
Highlights
n Package containing automation libraries for accessing
dSPACE systems
n
High-level libraries for convenient platform manage-
ment and simulation model access

n
Access to dSPACE real-time platforms and
dSPACE VEOS
n
Support of Python or any .NET-compliant language
n
Complies with ASAM HIL API standard
n
NEW: Support of ASAM XIL standard
Key Benefits
n
The Platform API Package is a set of libraries to access dSPACE real-time platforms and dSPACE VEOS
(p. 100). It provides a convenient way to download and start/
stop models and also gives high-level access to the model
variables for reading, writing, stimulating, capturing, etc.
HIL API MA (Model Access) Port Implemented

in Python or .NET
n
Programing interface compliant with the ASAM HIL
API 1.0 standard
n Reading, writing, stimulating and capturing model variables
on dSPACE real-time platforms and dSPACE VEOS (p. 100)
n
Capturing functions with highly flexible start and stop
trigger conditions
n
Direct access from Python (HIL API MA (Model Access)
Port Implemented in Python)
n
Direct access from C#, C++/CLI and MATLAB via the HIL
API MA (Model Access) Port Implementation in .NET
176
n Create your own test scripts and test automation applica-
tions to access parameters and signals in your simulation.
NEW: XIL API support in .NET

n Programming interface that complies with the new ASAM
XIL API standard for accessing the simulation modell
n MAPort support including read, write, and capture access
plus stimulus support for most dSPACE platforms
n Port management, e.g., for loading applications and setting the simulation state
2015
Introduction
Test Automation Software / Platform API Package
RTPLIB2
n
Reuse of existing RTPLIB scripts for dSPACE SCALEXO
n
Programming interface to dSPACE HIL platforms
(SCALEXIO, DS1005, DS1006); new platforms are not
supported
n
Supports reading, writing and easy capturing of model
variables on dSPACE real-time platforms
n
Successor of RTPLIB
n
Direct access from Python
Application Fields
Platform Management API

n
Programming interface for downloading, starting and
stopping a model running on a dSPACE real-time platform
or on dSPACE VEOS
Software
MATLABLIB2
n Remote control MALTAB to use its powerful mathematical
function, e.g., for signal processing
Order Information
Order Number
n PLATFORM_API
Hardware
Product
Relevant Software
Software
n AUD_BASIC
Engineering
n AutomationDesk
2015
177
Optional
Order Number
Test Automation Software / Failure Simulation API Package

Application programming interfaces for accessing dSPACE Failure Insertion Units
Highlights
n
Package containing automation libraries for accessing
dSPACE FIU systems

n
High-level libraries for convenient failure simulation
n
Support of Python or any .NET-compliant language
n
NEW: Support of ASAM XIL API EESPort standard
Key Benefits
The Failure Simulation API Package provides automation
libraries for accessing dSPACE FIU systems.
NEW: XIL API EES Port in .NET

n
Programming interface to access Failure Insertion Units
n
Support of all dSPACE Failure Insertion Units
Failure Simulation Module (see p. 137)

n
Failure simulation on all dSPACE hardware platforms
n
XIL API EESPort server to access Failure Insertion Units of
PHS-based (p. 496) and SCALEXIO HIL systems (p. 269)
178
2015
Introduction
Test Automation Software / Failure Simulation API Package
Product
Order Number
n FAILURE_SIM_API
Application Fields
Order Information
Relevant Software
Software
n AUD_BASIC
Engineering
Hardware
Software
AutomationDesk
2015
179
Optional
Order Number
Production Code Generation Software / TargetLink
TargetLink
Automatic production code generator
Highlights
n High-quality production code generation directly
from Simulink/Stateflow
n Built-in simulation and testing
n Powerful AUTOSAR support
n Certified for IEC 61508 and ISO 26262
180
Application Area
Model-based design has become the established development method across many industries, and production
code generation is the logical step for turning models
into efficient, production-ready code. TargetLink generates production code (C code) straight from the MATLAB/
Simulink/Stateflow graphical development environment.
The C code generation options range from plain ANSI C
code to optimized fixed- or floating-point code for AUTOSAR platforms. Versatile code configuration options ensure
that the production code copes with processor constraints.
Key Benefits
Converting graphical models directly into production code
ensures perfect consistency between model and code. With
deterministic code generation by TargetLink, the same model
always results in the same proven code to guarantee the
highest software quality. Every step can be tested against the
specification via the built-in simulation features. This allows
early verification and translates directly into cost savings,
for example, by avoiding expensive ECU software errors.
Efficient Coding
Efficiency is the key to production-quality code. Efficient code
requires a minimum of execution time and resources to run
on a cost-efficient embedded processor. Code generated by
TargetLink is proven to be as efficient as handwritten code.
Other factors also make TargetLink such a useful tool: code
readability, traceable model/code dependency, and last but
not least, the ability to configure the code generation to
produce exactly the kind of code that is required.
Seamless Tool Chain

TargetLink seamlessly connects function development
and code generation for the control unit or prototyping
hardware. It also automatically closes the gap between
the design and verification phases. The result: transparent,
well-defined development processes for conventional and
AUTOSAR ECUs. Calibration files, AUTOSAR software component descriptions, and comprehensive documentation are
generated in addition to the production code.
2015
Introduction

Feature
Description
Benefit
Code efficiency
n Efficient fixed-point or floating-point production code
n Your specifications models and diagrams
Code reliability
n Consistent, deterministic translations of models into
Human readability
n Concise, yet readable code
n Code reviews are easy to perform
Automatic scaling
n Intelligent scaling based on worst-case propagation of
n Shortens the time-consuming and error-prone scaling
stress-tested C code
signal ranges and simulation-based scaling

Test mechanisms
n Various test levels to test the production code against
Code coverage analyses
n Dynamic analyses of program execution to find areas
are directly translated into efficient C code

n Errors such as typing mistakes, oversights,
Application Fields
directly from MATLAB/Simulink/Stateflow
misunderstandings are avoided
process
n Malfunctions are found at earliest stage
the specification (MIL, SIL, PIL)

n Untested code and untested model parts are detected
that have not been run through

Incremental code generation
n Modular code generation, i.e., for specific subsystems
n Faster code generation, preserving approved code
Model referencing support
n Developing models on a modular/component basis
n Distributed development by large teams is much easier,
Multirate code
n Full support of multirate systems with intertask
n You can already define tasks at block level
TargetLink Data Dictionary
n Central container to handle variables, data structures,
Software
and large models can be handled more efficiently.

communication
scaling formulas, tasks, functions
Code generation straight from the
Data Dictionary
n Generation of code files and A2L files for Data
TargetLink Blockset
n The free TargetLink Blockset Stand-Alone can be used
Dictionary variables independently of their use in

TargetLink models
without having the Base Suite installed
Compliance with standards
n Compliance with relevant standards such as ASAM-
n You can manage complex data to plan and structure
your projects
n Simplified software integration and integration testing
for code from multiple TargetLink models/subsystems

and legacy variables
n Large workgroups can work with TargetLink models
without the need for additional TargetLink licenses

n Quality and interoperability guaranteed
n Support for modeling and code generation for
AUTOSAR software components (SWC), and generation

of SWC descriptions
n TargetLink bridges the gap between model-based
design and AUTOSAR-compliant software development
Support of OSEK/VDX-compliant
operating systems
n Support for the standardized OSEK/VDX interface and
Calibration data generation
n Calibration data exported as ASAM-MCD 2MC (ASAP2)
Documentation
n Automatic model and code documentation
n Your projects are transparent and trackable
AUTOSAR software component

(SWC) container exchange
n Exchanging AUTOSAR SWC containers between
n Safe and convenient round trips for AUTOSAR software
features
file for calibration tools
TargetLink and SystemDesk (p. 40)
n You can design multirate software that is compliant
with OSEK operating systems

n Automated and complete process with perfect
consistency between model and calibration data
development
Engineering
AUTOSAR support
Hardware
MCD 2MC (ASAP2), AUTOSAR, MISRA, and OSEK
n Access to SystemDesk simulation for proper software
integration testing
Modular development
n Innovative interface concept for ports, measurement
Connection to dSPACE VEOS
n Export virtual ECUs from TargetLink and run them in
n Easily increase software reuse across different projects
signals and calibration parameters

n Easy testing and experimentation with TargetLink code
2015
181
VEOS (p. 100) in combination with other virtual ECUs

and standard dSPACE tools like ControlDesk Next
Generation (p. 106).
Order Information
Classification
Type
Order Number
TargetLink Base Suite1)
Base Suite
n TBS
Target Optimization Modules

for certain processors/compilers
(further details see p. 202, p. 203)
Infineon C16x Tasking
n TOM_C16x/Tasking
Infineon TriCore Tasking
n TOM_TriCore/Tasking
Renesas SH-2/Renesas
n TOM_SH2/SHC
Other modules
Target Simulation Module (for all supported processors)
n TSM
TargetLink Module for Operating Systems OSEK
n TMOS_OSEK
TargetLink AUTOSAR Module
n TAS
TargetLink Data Dictionary Manager (included with

TargetLink Base Suite)
n DSDD_MANAGER
TargetLink is available as a 64 bit as well as a 32 bit version to be used in combination with 64 bit or 32 bit MATLAB.
1)
Relevant Software
Software
Included
Required
Stand-alone blockset for free model exchange
n TargetLink Blockset Stand-Alone
Data dictionary
n TargetLink Data Dictionary
n MathWorks MATLAB/Simulink/Stateflow
n Compiler for host simulation included in MATLAB
Optional
Operating system
n www.dspace.com/go/os_compatibility
Compilers for processor-in-the-loop tests
n Target-specific compiler for processor-in-the-loop tests
with Target Simulation Module
182
2015
Introduction
NEW: TargetLink 4.0

Feature Area
Improvement
Modeling in Simulink/Stateflow
n General matrix signal support across the board in TargetLink, i.e., for TargetLink blocks, TargetLink
Stateflow data, all AUTOSAR signals, etc.

n Matrix code generation options for high code efficiency for matrix signal code
Application Fields
n Support for new access functions in combination with matrix signals

n Permute Dimension, Reshape, and Matrix Concatenation as additionally supported blocks
n Simplified modeling of adaptive controllers through support for 1-D and 2-D dynamic look-up tables
n Specification of Data Dictionary struct variables/types at bus-capable blocks such as BusInports,
BusOutports, Merge, etc. to simplify code generation for C structs

n New Data Dictionary Function Block object to store properties of a TargetLink function block
n Automatic creation of subsystems with ports based on new Data Dictionary Signature objects describing
subsystem interfaces
n Support for Starting index (dialog) and Starting index (port) options in Assignment blocks and
Selector blocks
n Date property for Stateflow data to simplify the detection of changes
AUTOSAR
n Support for AUTOAR 4.1.3, 4.1.2 and 3.2.3 as the major new versions while maintaining compatibility
Software
with previous AUTOSAR releases

n General matrix signal support for AUTOSAR interfaces
n Support for CompuMethods of category IDENTICAL
n Support for port initialization values stored locally at ports
n Support for global constants (CONSTANT SPECIFICATION) with references to other global constants
n Simplified creation for PerInstanceCalPrm in the Data Dictionary Manager
n Use of $(Component) name templates for Data Dictionary variables to simplify the use of AUTOSAR
memory mapping
n Improvements in SWC container exchange with SystemDesk
n Use of model-linked code view files in combination with AUTOSAR-compliant code generation
Data Dictionary and Data Management
n Filtering mechanism/views for the Data Dictionary Manager to hide certain Data Dictionary objects
Hardware
and/or properties
n Embedded help functionality for the Data Dictionary Manager along with extended and improved help texts
n Improved message pane for Data Dictionary messages
n Data Dictionary API explicitly allows string type for Set operation
n Replace operation within the Data Dictionary Diff&Merge functionality to simplify engineering round-trips
n Consolidated Data Dictionary XML import to increase robustness
against XML files with minor defects
and support for XML file import from older TargetLink versions
Miscellaneous
n Consolidation of simplified roll-out of TargetLink for large workgroups

n Improved documentation generation features such as Japanese characters, proper function hierarchies, etc.
n Support for Stateflow variables for online parameter update to simplify testing
n Simplified update of variable values before SIL/PIL simulation for testing purposes
n More flexibility for modeling scaling-invariant systems in combination with feedback loops and by using
block handles in scaling-invariant scripts
TargetLink Product Support Center

The TargetLink Product Support Center is the primary online
resource for TargetLink users, providing information about
releases, compatibility, application notes, additional utilities, TargetLink Known Problem Reports, etc. The address is
www.dspace.com/tlpsc
2015
183
Engineering
n Specification of plot channels for TargetLink Sink blocks
How Do I Get the TargetLink I Need?

TargetLink Modules
TargetLink is available as a base suite plus additional modules,
so that you can adapt it to your needs.
TargetLink Module Overview

ANSI C
coder
TargetLink
Base Suite
TargetLink
1)
Blockset
TargetLink Data
2)
Dictionary
Document
Generator
ASAM-MCD 2MC
file generation
Autoscaling
TargetLink Base Suite License
Target Simulation
3)
Module
Target Optimization
Modules
AutomotiveSpecific
Modules
Freescale
MC56F83xx
Freescale
HCS12
Infineon
TriCore
Freescale
S12X
Freescale
MPC55xx
Freescale
MPC560xB
Infineon
C16x
Infineon
C16x
Infineon
TriCore
OSEK /VDX module
Renesas
M32R
Infineon
XC2000
Renesas
SH-2
Renesas
V850
Renesas
SH-2
AUTOSAR module
Usable in stand-alone mode without license.

The Data Dictionary Manager is also available as a stand-alone license, e.g., for use with the stand-alone blockset.
3)
Selection of major microcontroller families supported. For a complete list, please refer to www.dspace.com/goto?tlpil
1)
2)
TargetLink Base Suite

n Highly efficient ANSI C code generation from Simulink/
Stateflow
n For all microcontrollers with ANSI C compiler
n Fixed-point code, floating-point code or a mixture of both
n TargetLink Data Dictionary (p. 213)
n TargetLink blockset (p. 189)
n Autoscaling (p. 197)
n Code coverage analysis (p. 199)
n Modular development and code generation (p. 200)
TargetLink Module for Operating Systems (optional)

n Support of OSEK/VDX-compliant operating systems
(p. 211)
184
Target Simulation Module (optional)

n Test your generated code on the target microcontroller (for supported processors and evaluation boards
see p. 185)
TargetLink AUTOSAR Module (optional)
n Support for the development of AUTOSAR software
components (SWC) (p. 206)
Target Optimization Modules (optional)

n For target-specific, optimized code generation
n Uses compiler-specific language extensions and assembly
macros
2015
Introduction
Compiler Supported by Target

Simulation Module
Evaluation Boards
Supported by TargetLink
Freescale 56F83xx
Metrowerks CodeWarrior compilers
Freescale MC56F8367EVM
Freescale HCS12
Cosmic compilers and Metrowerks

CodeWarrior compilers
MCT HCS12 T-Board and

Freescale M68EVB912DP512
Freescale S12X
Cosmic and Metrowerks CodeWarrior

compilers
MCT S12X T-Board
Freescale MPC55xx
Green Hills, Metrowerks CodeWarrior,

GNU and Wind River compilers
Axiom MPC5554DEMO and

Freescale MPC5561EVB
Freescale MPC560xB
Green Hills and Wind River compilers
Freescale MPC5604BEVB
Infineon C16x
Tasking compilers
i+ME eCAN C167 CR
Infineon TriCore
Tasking and GNU1) compilers
Infineon TriBoard TC1766,

TC1767, and TriBoard TC1796
Infineon XC2000
Tasking compilers
SK-EB XC2287
Renesas V850
Green Hills and Renesas compilers
Renesas V850FX3 CAN-IT
Software
Processor Family
Application Fields
Supported Processors and Evaluation Boards

For processor-in-the-loop simulation, TargetLink supports
the most common processors for embedded applications,
especially in the automotive field.
Renesas AB_050_
Fx4_70F4012
Renesas M32R
GAIO and Renesas compilers
Renesas M3A2154
Renesas SH-2
Renesas compilers
Renesas CDK7058, and

SDK72513
Hardware
Only for TC1796.
For more information on software compatibility with

target compilers and evaluation boards, please refer to:
www.dspace.com/go/tlpil
TargetLink Engineering Services

Our engineering portfolio includes special TargetLink
customer services, for example:
n Hands-on support during introduction of TargetLink
n Support during evaluations and pilot projects
n Customer-specific TargetLink training
n Integrating TargetLink into your development
processes
n Model analysis and advice

n Support for developing and integrating AUTOSAR-
compliant software components
n Support for integrating the generated code in the ECUs
software environment
n Tool chain development and maintenance
n Process consulting
Engineering
Some of the evaluation boards need to be modified (loader,

external RAM, etc.). Please order them through dSPACE to
ensure a correct board setup.
2015
185
1)
How Do I Work with TargetLink?

Typical Steps in Generating Production Code
This diagram illustrates the workflow from
model design to code implementation.
It also shows that code verification based
on simulation is an iterative process.
The workflow is described in greater
detail on the following pages.
Modeling Approach
Reference
Single-Rate and
Multi-Rate
Modeling
Prepare Simulink
Model for
TargetLink
Model Simulation and

Code Specification
Model Exchange via

TargetLink Blockset
Typical Task
Behavior Validity Checks
Code Generation Settings
Scaling1)
Simulink
Model Exchange
in Workgroups
MIL
Production Code
Host Simulation
Typical Task
Host-PC
Scaling/Discretization Analysis1)
1)
Saturation and Overflow Detection
Code Coverage Analysis
SIL
Software-in-the-Loop
Validation / Verification
Precision
Model-in-the-Loop
Optimization
Achieving Production Quality
Analyzing Simulation Behavior and Optimizing Production Code
Create
TargetLinkModel
from Scratch

Definitions/Declarations
Variables
Data Structures
Scaling Formulas
Production Code
Target Simulation
Evaluation Board
Typical Task
Memory Measurement
Execution Time Profiling
Target Code Verification
PIL
Code Information
Function Calls
Tasks
...
Processor-in-the-Loop
Calibration
Generating
ASAM-MCD 2MC
Descriptions
Automatic Model
and Code
Documentation
Calibration Tools
Generating
AUTOSAR Software
Component
Descriptions
Integrating Generated Code on ECU

Generated Code
OIL File Generation
for OSEK
Operating Systems
RTOS
HandWritten
Code
Legacy
Code
I/O
Code
ECU
1)
186
valid only for fixed point software
2015
Introduction
Workflow
Application Fields
Using the TargetLink Block Library

To implement the control algorithms in C code, you need the
TargetLink block library. TargetLink blocks contain additional
data for code generation, such as the scaling information
for fixed-point variables, variable classes, variable names,
etc. A utility automatically replaces your Simulink controller
model with blocks from the TargetLink block library. The
process is reversible without any data losses. If you use the
free TargetLink Blockset Stand-Alone during control design,
conversion is not necessary.
Model-in-the-Loop Simulation on Host PC

Model-in-the-loop simulation (floating-point) serves as a
reference for subsequent steps and provides the minima and
maxima of variables as a basis for subsequent fixed-point
scaling if required.
2015
187
Engineering
Hardware
Software
Control Design and Function Prototyping

Control design starts with creating a control model in the
integrated design environment MATLAB/Simulink/Stateflow.
Before production code generation with TargetLink, you
can use dSPACE prototyping systems to carry out convenient function prototyping and validation of your new ECU
control algorithms.
Automatic or Manual Scaling

If you want to generate fixed-point code, the scaling has to
be specified. You can use manual scaling, simulation-based
autoscaling or worst-case autoscaling. You can choose from
a broad range of scaling options (p. 197) for each TargetLink
block individually.
Code Generation
The TargetLink Base Suite generates highly efficient ANSI C
code for a controller model at the click of a button.
Verification on Host PC via

Software-in-the-Loop Simulation
By means of software-in-the-loop simulation on a host PC,
you can compare the behavior of the generated code with
the reference data obtained in model-in-the-loop simulation.
TargetLink offers an graphical user interface, where you can
select the signal histories of blocks for detailed analysis.
188
Verification on Target Processor via

Using the optional Target Simulation Module (p. 192),
you can execute processor-in-the-loop simulation to verify
the generated code on an evaluation board equipped with
the same target processor as your final ECU. Successful verification of processor-in-the-loop simulation with model-in-theloop simulation and software-in-the-loop simulation ensures
the software quality of the generated code. TargetLink also
provides information on the code size, the required RAM/
ROM, and the stack consumption as it evolves over time.
The execution time can be displayed as well.
2015
Introduction
TargetLink Block Library for Implementation
TargetLink block dialog for entering implementationspecific

information like the data type, variable name, scaling data, etc.
Software
Implementation-Specific Information
The Simulink block library is very powerful in simulation
tasks, where it provides all the necessary specification features. When it comes to code generation, however, additional information is needed for each block. The TargetLink
blocks significantly extend the functionality of the supported
Simulink blocks. TargetLink blocks have an extended dialog
for you to enter the implementation-specific information
necessary for code generation. Each block also provides a
means of data logging and overflow detection. A special
routine automatically prepares Simulink models for code
generation with TargetLink by enhancing the Simulink
blocks to TargetLink blocks.
Application Fields
Extended Block Functionality
Engineering
Linking Control Design, Prototyping, and

Implementation
You can use the free TargetLink Blockset Stand-Alone
to design and prototype your controller without a full
TargetLink installation. The TargetLink blocks can be used for
rapid control prototyping on dSPACE hardware. Although
the added functionality of the TargetLink blocks is not avail-
Its features include:

n Free TargetLink model exchange in workgroups
n Controller design and simulation in Simulink
n Prototyping with MathWorks Simulink Coder
able in that case, the TargetLink Blockset Stand-Alone allows

you to use the same models for rapid control prototyping
and production code generation. Development iterations
are thus easier to perform and less prone to error.
2015
189
Function Development with TargetLink Blocks

The TargetLink Blockset Stand-Alone is a license-free version
of the TargetLink blockset which allows function developers
to design their controller models directly with TargetLink. It
can be used on any computer that has MATLAB/Simulink
installed. With the TargetLink Blockset Stand-Alone,
TargetLink models can be exchanged freely without the
need for extra TargetLink licenses.
Hardware
TargetLink Blockset StandAlone
Software Development
Function Development
1
in
1
in
same model
pictrl
plant model
Simulink Coder
MicroAutoBox
Real-time hardware
pictrl
plant model
TargetLink
ECU
Function development (including rapid control prototyping) with the TargetLink Blockset StandAlone and
software development with a full TargetLink installation.
Block Overview
TargetLink Block Library
These TargetLink blocks extend corresponding blocks in

the Simulink block library.
190
2015
Introduction
Application Fields
NEW: Matrix Support

The matrix support, included as of TargetLink version 4.0,
lets you combine data sets into matrices and specify matrix
signals in the model. The new TargetLink-supported blocks
then give you many different options to create, manipulate,
or split these matrix signals. You can use matrix code generation options to translate the modelings into efficient, readable matrix signal code in your model. Additionally, you can
now implement new algorithms, such as ADAS applications,
state-space controls, and sensor fusion like dead reckoning,
while benefiting from model-based development.
Software
TargetLink directly supports

these Simulink blocks.
Hardware
TargetLink Utility Blocks

TargetLink utility blocks provide access to specific features
of TargetLink or further specify the code generation process
for the model.
AUTOSAR Blocks
Model-based design for AUTOSAR ECUs (p. 209) is supported by blocks for structural elements such as runnables,
ports, and certain communication elements.
2015
191
Engineering
Multirate Blocks
The TargetLink multirate blocks make multirate operating
system objects available in block diagrams. There are even
OSEK-specific blocks like the CounterAlarm.
Block Configurations
Handling Large Models with the Property
Manager
If you need to change the properties of a large
model, TargetLinks Property Manager is a quicker
alternative to changing the properties in the block
dialogs manually. It is a graphical user interface
that displays the properties of TargetLink blocks
and Stateflow objects in your model, and lets you
view, filter, and modify several properties simultaneously. For Stateflow objects this includes charts,
events, states and data. The Property Manager
provides a tree view of the models subsystem
hierarchy, a list of blocks in each subsystem, and
a configurable list of properties for each block.
The Property Manager for handling models with numerous blocks.
Three Simulation Modes for Testing

Confirmation by Simulation
Comparing Simulation Results
Although code generators produce virtually flawless results
when compared to manual programming, the generated
code still needs to be tested as well as the underlying specification. TargetLink provides powerful and easy-to-use
means to verify the generated code. The code tests are
performed in the same simulation environment that was
used to specify the underlying simulation model. Functional
identity has been achieved when simulation results match.
The comprehensiveness of tests can be assessed using code
coverage analysis.
192
Test Against Specification

Verification means checking the implementation against the
specification. The specification is the simulation model, as
executed by Simulink and Stateflow. The executable and
approved specification is used as a reference. The implementation is the generated and compiled C code, as executed by
the target processor. TargetLink provides a 3-step verification
process which shows at a click whether the specification and
implementation are functionally identical. On the basis of
a controller model, TargetLink performs simulations of the
model, the generated code on the host, and the generated
code on the target, without additional model modifications
or preparations.
2015
Introduction
ThreeStep Verification Process
Model-in-the-Loop
Controller model
plots act as the reference for the next verification steps.

Model-in-the-loop simulation also serves other purposes.
It is used for detecting overflows of integer variables, and
its results are used for simulation-based autoscaling.
Software-in-the-Loop
Application Fields
Model-in-the-Loop Simulation
The first step is to record data for reference plots from the simulation model. Signals from selected blocks and state variables
are automatically logged by TargetLink. The model-in-the-loop
simulation captures the specified behavior of the model that
is to be implemented in C code later on. The recorded signal
Processor-in-the-Loop
C code on host PC
C code on target processor
Software
Evaluation
board
Plant model or stimulus signals
the host PC instead.The signal plots should be largely identical when compared to the results of model-in-the-loop
simulation. If they are not, they can be analyzed to get a
better understanding of the cause of the deviation and to
fine-tune the fixed-point settings.
Finally, the generated code runs on an embedded processor. Code that runs correctly on the host PC can still cause
trouble on the target processor. To check that this does not
happen, TargetLink offers processor-in-the-loop simulation.
An off-the-shelf evaluation board is connected to the host
PC, and the generated code is compiled with the target com-
piler and downloaded to the evaluation board. TargetLink

manages the communication between the host PC and the
evaluation board. All these activities are automated and need
no user interaction. Simulation on an evaluation board just
takes two mouse clicks.
2015
193
Engineering
Software-in-the-Loop Simulation
Software-in-the-loop means the code is generated and
replaces the controller blocks in the simulation model (for
example, the same plant and stimulus signals). TargetLink
does this automatically in the background. You still set the
controller blocks, though it is the code that is executed on
Hardware
TargetLink performs the three different simulation modes without any changes to the model or the generated code.
Display Results
Compare Plots
The simulation results are automatically plotted in the same
plot window that was used by the other simulation modes.
This is a convenient way to compare the results of simulations in different modes directly. For example, if plots from
processor-in-the-loop simulation deviate from software-inthe-loop simulation, the most likely cause is a bug in the
target compiler or a problem with the processor.
Efficient Approach
This 3-step approach, using model-, software- and processor-in-the-loop simulation, is easy, intuitive, and quick. As
a result, tests can be carried out more frequently, which
increases software quality.
Unparalleled Simulation Concept

Complete Simulation Support
TargetLink systematically utilizes all the available simulation
options to give users a powerful simulation environment.
MIL, SIL, PIL Simulation at a Click

Switching from MIL to SIL or PIL simulation requires just a
click. There is no need for a separate test model or generating S-functions or manual insertion into a test harness
model. TargetLink has built-in simulation and logging intelligence in all simulation modes.
Integrated Data Logging

TargetLink blocks come with integrated data logging functionality. In the block dialogs, you can specify whether to
log the block output signals. No changes to the model are
necessary, i.e., you do not have to insert scope blocks or
suchlike. Most importantly, data logging is not limited to
MIL simulation but available for all simulation modes without
further user interventions.
The TargetLink block dialog lets you specify whether to log signal
histories regardless of the simulation mode.
194
2015
Introduction
rent colors. Detailed signal analysis can be performed via

additional plot windows that include details about deviations
in individual simulation runs. This is also available at a click,
and you do not need to write your own plotting scripts.
Application Fields
Result Plotting
TargetLink directly visualizes the simulation results of
logged signals. Simulation results from different simulation
runs, no matter which simulation mode, are plotted on
top of each other in the same plot window, using diffe-
Software
Signal Analysis
In the Detailed Signal Window, you can zoom signals to
inspect deviations visually and get a clear picture of the signal
behavior. Constraints can be displayed to show immediately
whether signals are within defined ranges, which is especially
important for scaling. You can use a cursor to scroll through
the signal histories and display signal values numerically. The
Signal Deviation Window gives you a graph of the deviation
between two signals. These tools are all available at a click
for convenient analysis.
The Signal Deviation Window displays a graph of the deviation

between two signals.
2015
195
Engineering
Hardware
The Detailed Signal Window lets

you inspect signals and displays
their values numerically.
Benefits of the Simulation Concept

Advantages of Built-in Logging and Simulation
n MIL/SIL/PIL simulation at a click
n Built-in data logging and result plotting for all simulation
modes
n No changes to the model necessary
n Direct comparison of MIL/SIL/PIL results
n Detailed signal analysis and deviation plots
n Direct feedback whether code matches model simulation

n Especially useful for conversion from fixed point to floating point
In brief: very easy to use, with unmatched simulation
flexibility.
Run-Time Analysis
Profiling the Code
Processor-in-the-loop simulation can also be used to profile
the generated code. During simulation, TargetLink automatically measures execution time and stack consumption
directly on the target processor. A code summary lists RAM
and ROM usage for each function. These features allow you
to evaluate design alternatives, such as selecting different

search routines of a look-up table block. You can immediately measure the impact of the change on code efficiency.
Sound implementation decisions based on accurate benchmarks become a matter of a few clicks.
The results of code profiling: execution time measurement, stack

size measurement, and code summary of generated code.
Model-Code Traceability
For improved traceability and simplified code reviews, code files
can be optionally generated in HTML format, with hyperlinks
for navigation from model to code and vice versa at a click.
196
2015
Introduction
Scaling Variables
Fixed-Point Accuracy
Application Fields
Overflow Detection
Another big advantage: fixed-point overflows no longer
entail hours-long debugging sessions. With TargetLink, scaling can be checked during simulation. If an overflow occurs,
TargetLink shows the exact location in the block diagram.
The problem can be corrected right away.
Hardware
Software
Quick and Accurate Scaling

If TargetLink is to generate only floating-point code, scaling is
not necessary. However, when fixed-point code is generated,
autoscaling can be a huge time-saver. It takes away the tedious and error-prone task of manually scaling each variable
and each operation in the software. What took days and
weeks in the past can now be done in minutes and hours.
Plot overview window indicating an overflow of an outport block.
Automatic Scaling
These scaling properties give ample choices to fine-tune
fixed-point code to the conflicting requirements of low
execution time, high computational precision, and overflow
avoidance. Fixed-point scaling can be done manually by a
software engineer, but in most instances it is left to the
autoscaling tools from TargetLink.
2015
197
Scaling Properties
TargetLink offers a two-coefficient linear scaling method, which
is widely used in embedded control applications. The properties
for specifying fixed-point scalings in TargetLink are:
n Data type
n Power-of-two scaling factor or arbitrary scaling factor
n Offset value
n Constraint values
n Bit safety margins
n Saturation options
Engineering
Scaling Choices
Efficient Scaling Methods

Simulation-Based Autoscaling
Simulation-based autoscaling requires that the model can be
simulated. This necessitates either a plant model or stimulus
data for all inports. During simulation, TargetLink records
the signals from each Simulink block and determines the
value range in order to calculate optimum scaling for each
block. The advantage of this scaling method is maximum
computational precision.
Worst-Case Autoscaling
When simulation is not possible or deemed unfeasible,
TargetLink can perform autoscaling based on a worstcase range calculation. This method requires value range
information for inports and some specific blocks inside the
model. TargetLink propagates these value ranges through
the model and calculates the best scaling. The advantages
of this scaling method are that it does not require a plant
model and prevents overflows.
Dialogs to carry out automatic scaling.
Scaling with Scaling Formulas and Type Definitions

Using scaling formulas is not actually an autoscaling
method, but it is a way of scaling a model quickly. After defining a complete set of scaling properties under one name in
198
the TargetLink Data Dictionary, you can select them in block

dialogs or in the Property Manager to quickly scale signals of
one kind or subsystems with the same scaling parameters.
2015
Introduction
Code Coverage Analysis

Code branches that have never been executed are easily
identified, and test strategies can be adjusted accordingly.
Thus, coverage analysis increases software quality.
Application Fields
Run-Time Analyses
TargetLink offers C0 and C1 coverage analysis, also
called statement coverage and decision coverage.
During simulation on host or target systems, counters record
the frequency of execution for each branch of code. After
simulation, a code coverage analysis report is generated with
a coverage overview table and a detailed, annotated code
listing with the execution count for each block. This report
tells you immediately whether the tests cover everything.
Total Branches
Reached Branches
Unreached Branches
61.87%
139
86
53
Fuel rate controller
58.91%
129
76
53
Fuel rate calculator
56.56%
122
69
53
Correction redundancy
100%
Airflow controller
100%
10
10
Airflow calculation
100%
Airflow subsystem
100%
Software
Code Coverage
Fuel system
Annotated code listing with execution count for each code block.
2015
199
Engineering
Hardware
Example of the information provided by code coverage.
Modular Development and Code Generation

Handling large models and software integration
Incremental Code Generation
Incremental code generation is available for Simulink subsystems which contain a TargetLink Function block. Each
member of a development team can work on a subsystem
individually and just generate code for that. TargetLink performs the necessary consistency checks when building the
overall application from all the parts.
Benefits
Incremental code generation has several advantages:
n Code for individual subsystems in a model can be tested,
reviewed, and frozen, while development in other subsystems continues.
n Team members can work independently on different
subsystems.
n Code generation time can be significantly reduced by
generating code only for subsystems that have been
modified.
Specifying incremental code generation properties for a subsystem.
Model Referencing Support

TargetLink supports model referencing. Functionalities can be
flexibly partitioned into several model files, versioned separately, and developed on a modular basis. Parts of models
can be simulated separately and implemented individually
by means of incremental code generation.
200
Code can be generated incrementally

for referenced models.
2015
Introduction
Dictionary. Variables with global relevance that are shared

by separate models and subsystems are specified and generated from the Data Dictionary.
Code Generation Straight from the TargetLink

Data Dictionary
The Data Dictionary supports the generation of both code
and A2L files for Data Dictionary variables independently
of their use in TargetLink models. Variables with global
relevance that are shared between different models, subsystems and referenced models should be specified in the
Data Dictionary and implemented from there. Generating
code files with definitions and declarations, and also A2L

files for variables from the Data Dictionary, makes software
integration and software integration testing easy. Moreover,
all the calibration parameters for an entire ECU project can
be created in one file, no matter whether they are from
legacy code or used in TargetLink models.
Diff&Merge mechanisms via TargetLink

Data Dictionary
TargetLink Data Dictionary has the mechanisms needed to
compare different versions and display changes, e.g. old/new.
You can then trace modifications back to the model to analyze
their effects on it. Diff&merge mechanisms let you update

interface definitions simultaneously to ensure consistency
when changes are made making your work much easier.
2015
201
Engineering
Hardware
Software
Application Fields
Simplified Software Integration

TargetLink code from separate (incrementally generated)
subsystems and (referenced) models can be easily integrated
and tested by means of code generation from the Data
Code Optimization
Highly efficient production code
Optimized ANSI C Code
TargetLink generates highly efficient ANSI C code. This is
achieved by various optimization techniques, which roughly
fall into 3 categories:
n Standard optimizations
n Interblock optimization
n Code pattern libraries
Interblock Optimization
Interblock optimization combines the code of several blocks
in one C code line. TargetLinks interblock optimization gives
the generated code a human touch, because it combines
code in a very similar way to what a skilled software engineer
would do. For instance, a string of arithmetical, logical, and
relational blocks is usually combined in one expression. Code
Standard Optimizations
TargetLink uses many of the optimization techniques that are
also used by C compilers: constant folding, algebraic transformations, dead code elimination, and lifespan analysis of
variables, to name just a few. They are standard optimization
techniques and are used by TargetLink whenever applicable.
for calculating the inputs of a switch block is moved inside

the If-Else instruction.
The example shows interblock optimization at work. This
technique saves execution time and ROM size, but most
importantly, it reduces stack size significantly and enhances
code readability considerably.
Example of interblock optimization.
Code Pattern Libraries

A powerful block such as the 2-D Look-Up Table block or
the FIR Filter block needs several lines of code. TargetLink
takes them from an internal code pattern library during the
202
code generation process, ensuring that the code for complex

blocks is also highly efficient.
2015
Introduction
TargetOptimized Code
ANSI-C
Optimized Assembly Code
Cycles
1232
45
Code size
100 byte
54 byte
specific instructions and even inline assembly macros are

used to deliver top-notch code performance. Some features
of a processor core can be used only by applying these
coding techniques. This sometimes makes the difference in
meeting hard real-time requirements and ROM size limits.
Application Fields
Optimized Assembly Code

With the optional target optimization modules (p. 202),
processor- and compiler-specific language extensions can
also be used for code optimizations. This further increases
the efficiency of the generated code. There is a library containing highly optimized code patterns for every processor/
compiler combination supported by TargetLink. Compiler-
Software
64tap FIR filter, measured with Infineon TriCore/Tasking Compiler:

Optimized code is 27 times faster than ANSIC.
Customized Code
Engineering
Variable Classes
You also have full control of how TargetLink generates variables and and therefore of how the RAM and processor stack
are utilized. You can specify the scope and storage class
of a variable, as well as other C attributes like volatile or
const. Even PRAGMA directives can be generated before
and after each declaration or block of declarations. To keep
things simple, TargetLink bundles all these properties into
variable classes. You can select these in block dialogs to
save a lot of repetitive specification work.
Variable class specification for

a Gain block.
2015
203
Readability
TargetLink code is easily readable and has many comments.
Unnecessary macros, function calls, cryptic naming, etc. are
avoided. Comprehensive configuration options give you full
control over variable, function, and file naming, as well as
the flexibility tof partition the code into functions and files
to keep the structure logical and manageable.
Hardware
Code According to Customer Standards
External Code Integration

TargetLink offers a wide variety of specification options on
the block diagram level for easy interfacing with external
code such as device drivers, or with any other routine written in C or assembler.
These are:
n Including external header files
n Using external global variables
n Using externally defined macros
n Calling imported functions
n Calling access functions or macros
n Defining a Custom Code block containing handwritten
C code
Code Output Formatting

TargetLink can generate code in a format that exactly matches
company-specific C code templates. Code output can be
formatted via an XML configuration file and an XSL style
sheet. You can define the format of file and function headers, the format of code comments, and the inclusion of
specific header files. Comments can even contain Unicode,
for example, for Japanese characters.
Documentation Generated Automatically

Consistent Documentation and Model
TargetLink not only generates code, it also documents
what it does keeping perfect consistency with the model
and the code. An automatically generated document provides information about function interfaces and global
variables, and a list of all measurable and adjustable variables, scaling parameters, code generator options and much
more. Screenshots of models, subsystems, and simulation

plots can also be included. Links to the generated C code
are provided. You can specify the documentation you
require,for example, the level of detail. Documentation
can be generated in the HTML, RTF (for word processing)
and PDF formats.
Production code documentation in HTML.
204
2015
Introduction
Automation and Process Integration

Full Access to TargetLink
mated, while at the same time providing options for intervention in the individual process phases. For example, hook
functions allow user tasks to be performed at all stages of
the build process.
Application Fields
Comprehensive TargetLink API

TargetLink is easy to integrate into existing development
environments, because it comes with a comprehensive and
fully documented API. This grants full access to all TargetLink
properties and settings and allows processes to be auto-
Calibration File Generation
Software
Since the C code and the ASAM MCD-2 MC file are generated with the same data basis, they are always consistent.
This eliminates another error source, and streamlines the
development process.
TargetLink offers several predefined variable classes for
calibratable and measurable variables. You can also specify
your own classes, ensuring that each class holds suitable
attributes for calibration and/or measurement.
Hardware
ASAM MCD-2 MC File Format

Another important requirement for a code generator is close
links with calibration systems. ECU code must be prepared
for parameter fine-tuning by making calibratable or measurable variables accessible to a calibration system. TargetLink
supports the generation of the standardized ASAM MCD-2
MC file format (formerly ASAP2) via the Data Dictionary to
make the variables and parameters available for ECU calibration. All major calibration tools support this standard.
TargetLink
TargetLink
ASAM MCD-2 MC file
Code files
/beginn MODULE
/begin CHARACTERISTIC
...
/begin MESUREMENT
...
/begin RECORD_LAYOUT
...
*.a2l
Engineering
controller(vod)
{
...
}
External
ASAM MCD-2 MC files
*.a2l
*.C
ECU
/include module
ASAM MCD-2 MC Project File
2015
205
Calibration
System
Model-Based Design for AUTOSAR Software Components

The TargetLink AUTOSAR Module
The optional TargetLink AUTOSAR Module makes TargetLinks
modeling, simulation and code generation features available
for designing AUTOSAR software components (SWCs).
Developers can specify AUTOSAR structure elements, such
Functionality
n Model-based design for AUTOSAR software components
(SWCs)
n Code generation for AUTOSAR SWCs
n Importing, exporting and merging software component
descriptions
n Simulating and testing SWCs
n AUTOSAR frame model generation
n Round trips with other AUTOSAR tools based on
SWC description files
n Convenient round trips with SystemDesk based on
SWC container exchange
TargetLink AUTOSAR Block Library

To design AUTOSAR SWCs, TargetLink offers the TargetLink
AUTOSAR library:
n AUTOSAR runnables and operation calls are modeled
using the TargetLink Function/Runnable block.
n AUTOSAR communication mechanisms like sender/
receiver or client/server communication are specified in
TargetLink Inport and Outport blocks.
n Specific AUTOSAR features like signal acknowledgement,
signal invalidation and status signals are modeled using
special ComSpec blocks.
n Optional SWC sender/receiver blocks can be used to represent AUTOSAR ports in a Simulink/TargetLink model.
206
as runnables, ports, and communication interfaces, simply

at model level. Hence model-based designs are directly
implemented in the form of AUTOSAR-compliant production code.
Benefits
n Efficient and easy modeling using proven workflows
for AUTOSAR
n AUTOSAR-compliant code generation
n Easy migration of existing TargetLink models to
AUTOSAR
n Testing and verifying SWCs in early design phases
n No tedious manual creation of software component
description files
n Easy integration of TargetLink in an AUTOSAR tool chain
(p. 202)
In brief: You go from model to AUTOSAR-compliant code
faster.
TargetLink blocks for modeling AUTOSAR SWCs.
2015
Modeling AUTOSAR SWCs
Hardware
Software
Designing AUTOSAR SWCs

To define an AUTOSAR runnable, the Function/Runnable
block is applied to a modeled subsystem just as for normal
TargetLink functions. This can be done either for new models
designed from scratch or for legacy models with established
control functions. To define how data is exchanged between
the runnables of one or more SWCs, TargetLink Inports and
Outports are used just as in non-AUTOSAR applications.
TargetLink supports sender-receiver, interrunnable and synchronous client-server communication. Property specifications are made both on block level and via the TargetLink Data
Dictionary. The same model can be used to generate both
AUTOSAR-compliant code and standard TargetLink code.
Application Fields
Introduction
2015
207
Engineering
Referencing AUTOSAR objects specified in the Data

Dictionary from dedicated block dialogs
AUTOSAR-Compliant Code Generation

TargetLink generates production code for AUTOSAR software
components and provides all the code generation options
for optimization. Modeled runnables are implemented as
C functions and AUTOSAR communication mechanisms
specified in TargetLink Inports/Outports are implemented
as run-time environment (RTE) macros according to the
AUTOSAR standard.
The generated C code

for a runnable with
three included RTE
macro calls.
Simulating and Testing AUTOSAR SWCs

With TargetLink, SWCs can be simulated in all three simulation modes:
n Model-in-the-loop (MIL)
n Software-in-the-loop (SIL)
n Processor-in-the-loop (PIL)
Multiple SWCs can be simulated in one simulation run.
Communication between SWCs is simulated to the extent
supported by the Simulink design environment; for example,
there is no asynchronous client-server communication.
208
2015
Introduction
work, TargetLink creates the component descriptions and

exports the descriptions in AUTOSAR XML format. The
TargetLink Data Dictionary also lets you import and merge
existing component descriptions to achieve a seamless
AUTOSAR development process with a tool like SystemDesk.
a complete AUTOSAR software component. This procedure

makes it much easier to migrate existing models to AUTOSAR
or to start modeling from scratch.
Migrating Standard TargetLink Models to AUTOSAR

Existing, non-AUTOSAR TargetLink models can easily be
migrated to AUTOSAR using the TargetLink AUTOSAR
Migration Tool. It converts individual subsystems to
AUTOSAR runnables and supports flexible specification of
AUTOSAR properties by means of hook functions. You can
configure the tool to produce precisely the kind of AUTOSAR-compliant code you require. The TargetLink AUTOSAR
Migration Tool is available for download free of charge from
www.dspace.com/goto?tl_ar_migration
TargetLink in an AUTOSAR Tool Chain

For AUTOSAR software development, TargetLink is typically
combined with an AUTOSAR architecture tool like SystemDesk. A software architecture with multiple components is
specified in the architecture tool, while TargetLink is used
to fill and implement the individual SWCs. The two tools
exchange data on the basis of AUTOSAR XML files. A topdown approach (starting with the software architecture) and
a bottom-up approach (starting with a TargetLink function
model) can both be used for AUTOSAR round trips.
2015
209
Engineering
Hardware
Software
AUTOSAR Frame Model Generation

Using a software component description, TargetLink automatically generates a frame model containing the relevant
AUTOSAR ports and runnables. The developer can then
insert the control algorithm into this model frame to obtain
Application Fields
Importing and Exporting SWC Descriptions

To integrate the code generated for SWCs in the overall
AUTOSAR software architecture, software component
description files are required. These describe the structural elements such as runnables or ports that are used
in an SWC. To save function designers tedious manual
TargetLink and SystemDesk

TargetLink and SystemDesk are the ideal combination for
developing AUTOSAR-compliant software. The two tools
exchange SWC containers that hold not only ARXML files, but
also source files for implementation, A2L files, and other helpful meta information. This is a reliable, transparent way to perform AUTOSAR round trips with minimum user intervention.
In addition, TargetLink users have convenient, direct access to

SystemDesks V-ECU generation (p. 40) and VEOS simulation
capabilities (p. 100) for evaluating and testing the behavior of
TargetLink components as parts of complex systems in early
development stages with constant interfaces during the
different development stages.
SWC Container
...
SWC Container Export
SWC Container Import
.arxml .doc
Container
Manager
SystemDesk
SWC Container Import
SWC Container
.arxml .doc .a2l

...
.c
210
.h
TargetLink
SWC Container Export
Developing AUTOSAR
software with SystemDesk
and TargetLink based on
the exchange of SWC
containers.
2015
Introduction
Integration with OSEK/VDX Operating Systems

Taking Advantage of Standards
Benefits
This combination of TargetLink and the OSEK/VDX standard gives you huge advantages. A whole real-time system
can be described in one environment. Control algorithms
and operating system objects are specified entirely on the
block diagram level. This means you can specify real-time
properties in your familiar environment. Consistency checks
Application Fields
on user inputs and OSEK-aware automatic code generation

prevent common mistakes and shorten the installation and
testing phases for ECU software. This all reduces development time significantly. Finally, and importantly: the same
code is reusable on other OSEK/VDX-compatible operating
systems.
OSEK
Configurator
Hardware
import/
export
edits
edits
*.mdl
generates
*.oil
OSEK System
Generator
generates
Engineering
input to
TargetLink
Legacy Code
OSEK: Offene Systeme und deren Schnittstellen fr

die Elektronik im Kraftfahrzeug (Open systems and
their interfaces to automotive electronics), VDX:
Vehicle Distributed Executive; more details at
www.osek-vdx.org
1)
*.C
*.C
Make-Tool or Compiler IDE
*.C
2015
211
TargetLink
Model
intertask communication without leaving the block diagram.

TargetLink lets you create multirate models containing
blocks with different sample times. Multirate systems are
very flexibly mapped to periodic or event-driven operating
system tasks.
Software
The TargetLink OSEK Module

TargetLink equipped with the OSEK module is compliant
with the OSEK/VDX1) standard and can generate code
for real-time multitasking applications. OSEK operating
system objects are available on the block diagram level once the TargetLink OSEK module is installed. For
instance, you can set up alarms, define tasks, or specify
Interaction with the OSEK Operating System

Task Specification
You can specify all the OSEK attributes of a task in dialogs. The options available include selecting an existing task
and creating new tasks, along with specifying the priority,
number of activations, preemptability, resources used, and
associated events. TargetLink also adds customer-specific
OSEK options (for example, stack size specification) to the
task dialog.
Intertask Communication
TargetLink InPort and OutPort blocks allow you to completely specify communication between different tasks.
Data can be exchanged via OSEK messages or global variables. The code optionally works with local copies of global
variables. Critical code sections can be protected from being
preempted. If you do not specify intertask communication
manually, TargetLinks intelligent interblock optimization
finds the best setup automatically.
OIL File Generation

As part of the operating system standard, the specification
and generation process involves defining system services
and their attributes via the OSEK Implementation Language
(OIL). TargetLink gives full freedom to use either TargetLinks
built-in graphical user interface or the operating systems
dialog-based OSEK configurator for editing the OIL file. The
generated code and operating system are automatically
consistent.
Specifying task properties on block

diagram level.
212
2015
Introduction
Managing Data with the TargetLink Data Dictionary

Central Data Container
Application Fields
Tight integration with TargetLink

Full access to code specifics
Various import and export formats
Full access to all TargetLink Data Dictionary objects via
powerful MATLAB API
declarations. Scaling formulas can be entered and used to

uniformly scale fixed-point signals and parameters in the
model. You can import and export standardized or proprietary data and share it data with the calibration system.
Hardware
Description
The TargetLink Data Dictionary is a central data container
holding the relevant information for a models design, code
generation, and implementation on an ECU. Data dictionary
objects can be referenced from TargetLink models. You can
define and manage variables and their properties, and you
can specify structured data types and use them for variable
n
n
n
n
Software
Key Features
n Central container for managing all data required for
designing a model and implementing it on an ECU
n Convenient administration of parameters, constants,
signals, variables, structures, variable classes, typedefs,
scaling formulas, etc.
2015
213
Engineering
To specify the properties of the code to

be generated, Data Dictionary objects are
referenced from block diagrams of the
model, in this case for a specific variable.
Benefits
The TargetLink Data Dictionary is the perfect tool for defining
and handling project-related code specifics, even for workgroups. It provides access to a wealth of additional information: specifics on C modules, function calls, tasks, variable
classes, data variants and so forth. The data is presented in
Subsystem A
Subsystem B
Model X
Subsystem C
Model Y
a well-organized tree and can also be accessed via an application programming interface (API). The Data Dictionary
also supports common import and export formats, so that
existing and proven definitions, for example, a calibration
file, can be used as templates.
Subsystem D
Model Z
ASAM-MCD 2MC
XML
Data Dictionary Manager
Data
Dictionary
API
Data Dictionary Manager

The Data Dictionary Manager provides the user interface
to the Data Dictionary for convenient administration of the
data required for designing models and implementing them
on an ECU. Elements such as type definitions, variables, and
scaling formulas are organized clearly. Typical user interface
functions are available, like copying and pasting objects,
loading and saving individual data branches, and searching the entire dictionary. With its multi-edit capabilities,
the Object Explorer pane provides an overview of multiple
objects and selected properties, and allows the properties
of multiple Data Dictionary objects such as variables to be
modified simultaneously. This greatly simplifies the handling
of large data volumes. The tool can be customized by using
the M-script plugin mechanism for menus, context menus,
and properties. Additional panes can be used for outputs
generated from user scripts.
214
OIL
AUTOSAR SWC
descriptions
.....
The data and the model are kept

separate.
Data Dictionary Manager with tree view and Property Value List.
2015
Introduction
Application Fields
Data Structure
The TargetLink Data Dictionary has specific main areas where
you can set the configuration data, the pool data for models
(pre-code generation data), and the subsystem and application data (post-code generation data). Selected branches of
the Data Dictionary can be loaded from separate include
files, which are maintained centrally for a whole workgroup.
Share Data
Software
Data Dictionary API

The TargetLink Data Dictionary MATLAB API gives you full
access to the TargetLink Data Dictionary via MATLAB. All
the functions necessary for managing data are available, for
example, for creating Data Dictionary objects and defining
their properties. Open API interfaces make it easy to integrate the TargetLink Data Dictionary into your companys
environment. To connect your own database to the Data
Dictionary, you can develop your own export or import
functionality.
Engineering
Hardware
Import and Export

The TargetLink Data Dictionary supports various import/
export formats, including
n Variables and Simulink data objects from/to MATLAB
workspace and files
n XML (Extensible Markup Language)
n ASAM MCD-2 MC (Standardized Description Data,
formerly ASAP2)
n AUTOSAR software component descriptions
n OIL (OSEK Implementation Language)
2015
215
Exporting Data Dictionary variables into the MATLAB

workspace.
Prepare for Calibration

After generating code, TargetLink writes a detailed description of it to the TargetLink Data Dictionary, including lists of
generated C modules, functions, variables, type definitions,
scalings, variable classes, etc. This information is used for
A2L generation when you export data to calibrate ECU
parameters.
Export of A2L files from the TargetLink Data Dictionary.
TargetLink Data Dictionary Connection to SYNECT

The file-based TargetLink Data Dictionary is easy to connect to SYNECT, dSPACEs data management software
(p. 270), which acts as a central data base with multi-user
support and integrated variant management.
Define project global data

Manage and reuse data across projects
Share data in your development team
SYNECT
Project 1:
Parameters
Signals
Data types
Scalings
Connecting the TargetLink Data Dictionary to SYNECT

for signal and parameter management.
216
Fcn1.mdl
Project 2:
Parameters
Signals
Data types
Scalings
TL DD
TL DD
Fcn1.dd
Fcn2.dd
Fcn2.mdl
Project N:
Parameters
Signals
Data types
Scalings
TL DD
FcnN.dd
FcnN.mdl
2015
Introduction
Application Fields
This provides the following benefits for TargetLink users:

n Early simulation of TargetLink code in large systems
consisting of multiple virtual ECUs and plant models,
including buses if required
n Convenient experimentation and testing with
ControlDesk Next Generation and other dSPACE Tools
The approach shown in the figure below is intended for TargetLink users who do not work on AUTOSAR projects. For
AUTOSAR projects, it is recommended to exchange AUTOSAR
software components between SystemDesk and TargetLink,
and generate the V-ECU from SystemDesk (p. 40).
Software
TargetLink Connection to VEOS

TargetLink code can run not only in SIL/PIL simulations in
the Simulink environment, but also on dSPACEs PC-based
simulator VEOS (p. 100 and figure below). This is done by
wrapping code in an executable unit called a virtual ECU (VECU), which is generated from TargetLink models. TargetLink
code can then be executed along with other V-ECUs as well
as plant models on VEOS. To capture signals and adjust or
test parameters, A2L files exported from TargetLink are used
with dSPACE ControlDesk Next Generation, which provides
access to VEOS. Thus, the standard dSPACE tools used for
real-time simulation are also used for offline simulation and
experimentation with TargetLink-generated code.
Plant Model
TargetLink Model
V-ECU build
ControlDesk
Next Generation
Hardware
V-ECU
AutomationDesk
Virtual ECU wraps
code generated
from a TargetLink
subsystem
2015
217
Engineering
Connection of TargetLink to VEOS for nonAUTOSAR users.
Software Quality and Standards

As a company committed to software quality, dSPACE
applies a variety of methods to ensure the highest standards
for its software products.
TargetLink Certified for ISO 26262 and IEC 61508
TargetLink is certified by TV SD (German certification
authority) for use in the development of safety-related
systems. TV confirmed that TargetLink is suitable for software development according to ISO 26262, IEC 61508 and
derivative standards (such as EN 50128, which governs
safety-related software on the railways). The certification
was based on several areas:
n Software development process and software modification
process of TargetLink
n Problem handling procedures
n Fitness for purpose in safety-related development
according to IEC 61508 and ISO 26262
TV SD also approved a reference workflow providing
guidance for the model-based development of safety-related
software with TargetLink.
IEC 61508 is the internationally recognized generic standard

for the development of safety-related electronic systems.
The automotive standard ISO 26262, which is derived from
IEC 61508, is the new standard for the development of
safety-related systems in road vehicles.
ISO/IEC 15504-Compliant Development Process

ISO/IEC 15504 (also known as SPICE1)) is an international
standard for software processes. Its underlying concept is
that a mature software product requires a mature development process. dSPACE has dedicated itself to an ISO/IEC
15504-compliant development process.
Internal Software Quality Management

An internal quality department, the dSPACE quality management team, proactively manages software quality at
dSPACE. The team leads software improvement activities,
sets internal standards, conducts internal assessments, and
provides consultation services to all software groups. It acts

independently and ensures that the highest product quality
goals are consistently achieved and sustained.
SPICE: Software Process Improvement and Capability Determination
1)
218
2015
Introduction
1)
Application Fields
Software
Facts About TargetLink and DO-178C/DO-331 in Brief

n Simulink/TargetLink models for specifying high-level
requirements
n TargetLink design models for specifying low-level
requirements
n Generation of high-quality, easy-to-read, and traceable source code from TargetLink models
n Comprehensive simulation support for models and
code according to the established MIL/SIL/PIL verification concept
n Powerful tool chain with tools from BTC Embedded
Systems for requirements specification, automatic test
vector generation, requirements verification and
formal verification via model checking
Hardware
Certified Code
With the DO-178C as the future relevant standard for the
development of software in aviation, model-based design
and automatic code generation will have a solid base for
use in the aerospace sector. The document DO-331, ModelBased Development and Verification Supplement to DO178C and DO-278A, which is also part of the standard, was
written specifically for this. dSPACE takes this into account
by providing a workflow document that explains how to
use TargetLink in a model-based tool chain for DO-178Ccompliant projects. The workflow document describes how
to meet the individual requirements or objectives of
DO-178C/DO-331. It focuses not just on TargetLink itself
but also on a complete model-based tool chain that can
contain further third-party tools, for example, from TargetLink cooperation partners such as BTC Embedded Systems,
AbsInt and Model Engineering Solutions. The workflow
document is thus an important contribution towards simplifying the certification of TargetLink-generated code in
DO-178C-compliant applications, addressing all criticality
levels up to Level A.
You can obtain the approximately 60-page document from
TargetLink.Info@dspace.de.
formulate requirements for modeling in TargetLink with

regard to functional safety and are particularly relevant
to safety-critical projects. The MISRA TargetLink modeling
guidelines (MISRA AC TL) can be obtained from the official
MISRA website www.misra.org.uk
Engineering
MISRA Modeling Guidelines for TargetLink

MISRA has published official MISRA modeling guidelines for
TargetLink. TargetLink is the first production code generator for which such guidelines have been issued. With these
guidelines, function and production code developers have
an official standard that gives them support for the design
and implementation of vehicle functions. The guidelines
TargetLink-generated code respects the vast majority of

MISRA C rules. If deviations from the MISRA C standard are a
technical necessity, they are identified and well documented.
dSPACE makes this document available to all TargetLink
customers.
MISRA: Motor Industry Software Reliability Association (www.misra.org.uk)
2015
219
MISRA C
The British MISRA1) C standard is a widely accepted C subset
for projects in the automotive industry. Its aim is to define
rules for avoiding common software errors that can occur
when software engineers write software by hand. Most of
these rules also make sense for machine-generated code.
TargetLink Partner Program

The TargetLink Partner Program was designed for companies that develop and promote products for complementing and expanding TargetLinks functionalities. It supports
customers when they launch a model-based development
process and a tool chain around TargetLink.
There are two kinds of TargetLink partners:
TargetLink Partner
This kind of partnership offers a company or organization
the possibility to cooperate closely with a market leader in
embedded software development.
TargetLink Strategic Partner
A TargetLink Strategic Partner is a company or organization
that develops and promotes a complementary product which
supports TargetLink in such a manner that it goes above and
beyond the normal support for comparable tools.
Up-to-Date List of TargetLink Partners:

n www.dspace.com/go/tlpartnerprogram
Current TargetLink Partners

TargetLink Strategic Partners
BTC Embedded Systems AG
www.btc-es.de
Model Engineering Solutions GmbH
www.model-engineers.de
TargetLink Partners
220
AbsInt Angewandte Informatik GmbH
www.absint.com
Emerge Engineering GmbH
www.emerge-engineering.de
PikeTec GmbH
www.piketec.com
Reactive Systems Inc.
www.reactive-systems.com
Schaeffler Engineering GmbH
www.schaeffler-engineering.com
2015
Introduction
Third-Party Tools and Services for TargetLink
Topic
Product
Company
Requirements tracing
TargetLink in combination with

n Simulink Verification and Validation
n MES Model Examiner MXAM
n StyleChecker
Model analysis and review
Model coverage analysis
Test vector generation
BTC EmbeddedTester
n Simulink Verification and Validation
www.btc-es.de
www.mathworks.de
BTC EmbeddedTester
Reactis
BTC EmbeddedTester
MES MTest
n TPT
n
n
Model-based testing
MES M-XRAY
www.dspace.de
www.mathworks.de
n www.model-engineers.de
n www.schaeffler-engineering.de
n
www.btc-es.de
www.reactive-systems.com
www.btc-es.de
n www.piketec.com
BTC EmbeddedSpecifier
BTC EmbeddedValidator
www.btc-es.de
www.btc-es.de
Code coverage analysis
BTC EmbeddedTester
www.btc-es.de
Run-time error analysis
Astre
n Polyspace Code Prover
n
n
www.absint.com
www.mathworks.de
Formal verification
Software
Guideline checking
Application Fields
Up-to-Date List of Third-Party Tools

n www.dspace.com/go/tlpartnertools
aiT WCET Analyzer
www.absint.com
Stack usage analysis
StackAnalyzer
www.absint.com
Requirements coverage analysis
BTC EmbeddedTester
www.btc-es.de
Training and development platform
MEDKit on ARM Motor Control Education Kit
www.emerge-engineering.de
ISO 26262 consulting services
MES ISO 26262 Consulting Services
2015
221
Engineering
Timing analysis
Hardware
This page provides an overview of complementary products

and services that support you in establishing a model-based
development process and tool chain built around TargetLink.
Production Code Generation Software / Model Compare
Model Compare1)
Comparison of Simulink, Stateflow, and TargetLink models
Highlights
n Graphical display of differences
n Generation of difference reports
n Built-in support for TargetLink
n Flexible difference filters
n Review support
n Merge support for models
n Command line interface for tool automation
n 32/64-bit MATLAB support
Key Benefits
Model Compare finds all the changes in a model. Even
large models can be compared in minutes, which would
be practically impossible without tool support. You can use
filters to focus on relevant differences and ignore unimportant ones such as layout changes or simulation settings. The
support for review sessions also enables reliable, safe, and
controlled reviews of model changes. The merge support
simplifies the synchronization of changes in different versions of a model.
Application Areas
Automatic comparison is a must whenever you work with
multiple versions of a model. Model Compare from dSPACE
can be used with any TargetLink, MathWorks Simulink or
Stateflow model, and also supports libraries. There is a
broad range of use cases for Model Compare, for example:
n Managing different model versions or model variants
n Merging parallel development branches
n Verifying and reviewing model changes
TargetLink Support
Model Compare has built-in support for all TargetLink blocks
and properties. They are displayed and handled like ordinary
Simulink/Stateflow elements, so you do not have to bother
with TargetLink implementation details. Since the semantics
of TargetLink properties are known, they are also intelligently
handled by the predefined filter options.
222
2015
Review Sessions and Merge Support

You can associate review comments to block and property
differences found by the tool, including date/author tracing.
Complex reviews with multiple participants are supported.
Detected changes can be transferred from one model to
another to merge parallel development branches or manage different model variants. With easy-to-use commands,
merging models this way is much less error-prone than it
would be by hand. The remaining differences between the
models are constantly kept up-to-date, so that you always
see the current state of your work.
1)
Introduction

Feature
Description
Benefit
Support for TargetLink
n Model Compare recognizes TargetLink blocks and
n There is no need to bother with TargetLink
Powerful comparison algorithm
n Models from different MATLAB versions are compared;
block correspondences are detected even if the names

of the blocks have changed; parameter values are
compared either in unevaluated form (e.g. Kp) or
in evaluated form (e.g. 5.4).
Flexible filter configuration
Convenient result display
n Model
Compare can be configured to filter out

unimportant differences, e.g., layout changes or
simulation options, according to a variety of criteria.
A comparison can be restricted to selected subsystems.
n The comparison results are displayed in synchronized
tree views, with differences indicated by customizable

color schemes. A statistics window displays the number
of changed, added and removed elements.
implementation details.
n Conversion and upgrade problems can be addressed.
Application Fields
properties, and handles them just like built-in blocks.
You get concise comparison results even if blocks were

renamed. Different workspace settings can be taken
into account.
n You can focus on the differences and model parts that
are relevant to you. This greatly improves the efficiency

of a comparison.
n You can easily see which elements correspond to each
other. Added, removed and modified elements as well

as the number and type of changes can be seen at
a glance.
properties or with the complete comparison session.
safe way. You can also use the comment function to

structure your own working process.
Traceability from Model Compare

to model
n You
Traceability from model back to

Model Compare
n You
n This
Merge support
n The
can easily highlight Simulink and Stateflow

n It is easy to view the context of a change and all the
elements by selecting them in Model Compare, and
differences in a subsystem.
show any differences directly in the compared models.
n You can merge parallel development branches and
n Comparison results and associated comments can
is helpful to identify blocks and lines in Model

Compare
transfer changes between distinct model variants.
Hardware
can trace model elements in Simulink back to

Model Compare
commands copy to right, copy to left, and
delete can be used to transfer changes from one
model to another.
Report generation
Software
n Comments can be associated with individual blocks and n Reviews are performed in a reliable, controlled and
Review support
n The information can be archived and published.
be saved as HTML, PDF and XML reports, model

screenshots can be integrated in the difference reports.
Tool automation
n Comparisons
can be started by command line, and

reports can be generated automatically. Reports can
be saved in XML format for easy processing by
external tools.
n You can process multiple models automatically and
incorporate Model Compare into your own tool chain.
Product
Order Number
Model Compare1)
n MOC
Engineering
Order Information
Relevant Software
Optional
1)
Operating system
n www.dspace.com/goto?os_compatibility
n MathWorks MATLAB/Simulink/Stateflow
Production code generator TargetLink
n See p. 180
2015
223
Software
Required
NEW: Model Compare 2.5

Improvement
Detailed Description
Fulltext search of hierarchy items
Finding items in the model hierarchy by a given name or part of a name.
Improved display of comparison results for

bussupporting blocks
Comparison of the individual bus signals to detect differences at a glance.
Improved display of LSB values
Additional display of LSB values as power of two, if possible.
Optional support for HIL model comparisons
Clear view of the important and relevant differences in dSPACE HIL models via dSPACE addons.
Graphical Display of Differences

Model Compare shows all model differences clearly arranged
in two synchronized tree views, where changed, added and
removed elements are indicated by customizable colors.
While navigating through the model hierarchy, all property
differences can be inspected in the Property Inspector. Predefined and flexible filter configuration improve the efficiency
of comparison and allow adaptation to individual needs.
Differences can be traced from Model Compare directly to

the Simulink/TargetLink models, where the corresponding
elements are indicated by customizable colors. Thus, the differences can be easily inspected in the context of the models.
In addition, elements of Simulink/TargetLink models can
also be traced back to Model Compare to inspect all their
differences at a glance.
Graphical display of differences in Model Compare and directly in Simulink/TargetLink models
224
2015
Introduction
Software
Application Fields
Merge Support
With Model Compare you can eliminate differences between two Simulink/TargetLink models by merging the two
models. Changes of model elements as well as individual
properties can be transferred from one model to the other
by commands copy to right, copy to left or delete,
if it exists in only one model.
A smart line handling mechanism automatically adjusts signal
lines of copied or deleted blocks. If a block is copied, the
related signal lines are copied as well. If a block is deleted,
the related signal lines are automatically deleted or reconnected. All merge operations are logged in the merge log
window.
Model Compare merge support
Hardware
Since Model Compare 2.4, there are new configuration options for customizing the report to individual preferences.
You can specify the subsystem level up to which screenshots
are provided and how comprehensive the report should be.
Difference reports in different file

formats for publishing and / or
archiving the comparison results
2015
225
Engineering
Report Generation
Comparison results and associated comments can be saved
as difference reports in HTML, PDF and XML format. The
generated reports also include all the comments that were
created during a review. Thus, Model Compares difference
reports are also a means of filing review results.
ECU Interface Software / ECU Interface Manager

Bypassing without ECU source code modifications
Highlights
n Quickly integrates bypass hooks in ECU HEX file
n No ECU source code and build environment required
n Visualizes function calls, read/write accesses to ECU
variables and conditional branches in ECU code

n Supports internal and external bypassing
n Automation API for MATLAB/Simulink
Application Areas
Service-based bypassing with the dSPACE RTI Bypass Blockset is an established model-based approach for developing
new controller strategies for electronic control units (ECUs).
Once the bypass service and bypass hooks are integrated
in the ECU code, control engineers can flexibly choose the
hooks for triggering their new control strategy and select
the ECU variables to be read and written by their new functions. Service-based bypassing also provides mechanisms to
ensure data consistency and safe operation.
The integration of bypass hooks in the ECU software typi-
Key Benefits
The ECU Interface Manager is an easy-to-use tool for quickly
integrating bypass services and hooks directly into the ECU
software. You can individually prepare the ECU HEX and
A2L files for controller strategy development by means of
the RTI Bypass Blockset and internal or external bypassing
via the DCI-GSIs. This does not require ECU source code
modifications by the ECU supplier or access to the ECU build
environment. Bypass projects can be implemented quickly
and development costs are minimized.
The ECU Interface Manager graphically visualizes the positions of function calls, read/write accesses to ECU variables
and conditional branches in the ECU program flow. This lets
you insert bypass hooks at appropriate positions in the ECU
226
cally requires iterative discussions between the automobile

manufacturer (OEM) and the ECU supplier. Often multiple
software versions have to be provided in the course of a
bypass project, which might result in project delays and
increased costs.
This is where the ECU Interface Manager comes into play. It
allows control engineers to implement bypass hooks
directly in the ECU HEX code themselves without requiring
the ECU supplier to deliver a special ECU software version.
code without needing to know ECU software details. To

minimize the influence of internal bypass functions on the
ECUs run-time behavior, you can deactivate the execution
of original ECU functions by means of a dedicated control
logic. You can even delete entire ECU functions and reuse
their memory for new control functions that you are developing. All this can also be done automatically through an
m-API from within MATLAB/Simulink.
The ECU Interface Manager is based on a configuration file
which allows ECU suppliers to configure what ECU software
details are to display. The configuration file can be encrypted
so that ECU suppliers keep full control of the information
provided to the end user.
2015
Introduction
Product
Order Number
n
EIM_BASIC
ECU Interface Manager option for TriCore microcontrollers and internal bypass
n
EIM_TRICORE_INT
ECU Interface Manager option for TriCore microcontrollers and external bypass
n
EIM_TRICORE_EXT
ECU Interface Manager option for Freescale MPC5xxx and ST Microelectronics SPC56/57 microcontrollers and internal bypass
n
EIM_MPC5xxx_INT
ECU Interface Manager option for Freescale MPC5xxx and ST Microelectronics SPC56/57 microcontrollers and external bypass
n
EIM_MPC5xxx_EXT
ECU Interface Manager option for Renesas V850 and RH850 and internal bypass
n
EIM_V850X_INT
ECU Interface Manager option for Renesas V850 and RH850 and external bypass
n
EIM_V850X_EXT
Application Fields
Order Information
For support for further microcontroller families, please inquire.
Optional
Order Number
n
RTI Bypass Blockset
Software
Software
n
RTIBYPASS_BS
n
Internal Bypass Plug-In for RTI Bypass Blockset supporting the Infineon TriCore microcontroller families n RTIBYPASS_BS_INT_TRICORE
n
Internal Bypass Plug-In for RTI Bypass Blockset supporting the Freescale MPC5xxx and
n
RTIBYPASS_BS_INT_MPC5XXX
ST Microelectronics SPC56 and SPC57 microcontroller families

n
Internal Bypass Plug-In for RTI Bypass Blockset supporting the Renesas V850 and RH850
n
RTIBYPASS_BS_INT_ V850X
microcontroller families
Hardware
Order Number
n
Generic Serial Interfaces DCI-GSI1 and DCI-GSI2
Workflow with the ECU Interface Manager

Apart from the original ECU HEX and A2L files, the ECU
Interface Manager requires a bypass service and a configuration file to be imported. The necessary configuration
settings include the free ECU RAM and flash resources,
entry points for the HEX file parser and the code check
mechanism used by the ECU. It is also possible to define in
detail which ECU functions and variables actually to display.
For example, top-level functions serve as a kind of display
filter. Read/write accesses to ECU variables, ECU function
n
See p. 575/p. 573
calls and conditional branches below these top-level functions are visualized without any extra settings. In addition,
there are options in the configuration file to mark individual ECU functions or variables as hidden and to define new
ECU variables which are not described in the A2L file. The
ECU supplier typically delivers the original ECU HEX and A2L
files plus the configuration file, which can be encrypted, to
the OEM. A graphical configuration tool with access to the
build process simplifies setting up the configuration file.1)
Requires an ELF file that is generated during the ECU software build process.
1)
2015
Engineering
Optional
Hardware
n
DSPACE_ECU_FLASH
227
n
dSPACE ECU Flash Programming Tool
Software Engineers (ECU Supplier)

ECU software development
A2L
Control Engineers (OEM)
A2L file
HEX file
Configuration file
(encrypted)
Config.
encrypted
MAP/
ELF
ECU
Integration of:
Bypass services
Bypass hooks
Control logics
HEX
Controller development
Bypass configuration
Bypass
service
RTI Bypass Blockset

for MATLAB/Simulink
Bypass Service
Workflow with the ECU Interface Manager.

The bypass service is provided by dSPACE. It has to be patched
into the original ECU HEX file by means of the ECU Interface
Manager, so it is supplied as binary code which is specific to
certain microcontroller families (p. 227) such as Infineon
TriCore, Freescale MPC5xxx, or Renesas RH850. dSPACE offers
bypass services for internal and external bypassing.
The configuration file usually contains a link to the associated ECU HEX and A2L files. Thus, when starting a new
bypass project, users of the ECU Interface Manager just
have to import the configuration file and the binary code

of the bypass service.
During import, the ECU Interface Manager parses the ECU
HEX file and the A2L file and determines and visualizes the
program flow with respect to the sequence of function calls,
read/write accesses to ECU variables and conditional branches in the ECU software.
After importing the configuration file and the bypass service,
User interface of the ECU Interface Manager. In this example bypass hooks have been placed around an ECU function, and a control logic has
been integrated so that the execution of the function can be switched on or off during run time.
228
2015
Introduction
Automation with the ECU Interface Manager

The ECU Interface Manager provides two options for automation: function developers working with the RTI Bypass
Blockset can stay in the MATLAB/Simulink development
environment and easily integrate bypass services and hooks
in the ECU software via a MATLAB m-API. Software engi-
Application Fields
function, you can generate a new ECU HEX and A2L file at
the push of a button. If you do not want to merge the
contents of the original A2L file and the bypass-related
information in a single new file, you can also specify output
a separate A2L file with information on bypass hooks. Finally, the new ECU HEX file has to be flashed onto the ECU,
and control engineers can continue developing new controller strategies with the RTI Bypass Blockset.
neers or tool experts can use a command line interface to

automate workflows and integrate the ECU Interface Manager into an existing tool chain, all without the need for an
additional MATLAB license.
Software
you are ready to insert bypass hooks. You can simply insert
service calls (bypass hooks) at any appropriate position in
the ECU software. To reduce run-time overhead, the execution of individual ECU functions can be deactivated by
adding a control logic. In order to have as much free ECU
memory as possible, you can also delete ECU functions that
you do not need for a specific development task. You can
then use the freed memory for the new control function
that you are developing. When you have developed the new
Engineering
MATLAB/Simulink
Integrate
bypass service
and hooks
MATLAB automation interface of the ECU Interface Manager
2015
229
Remote control
via MATLAB m-API
Hardware
Automation interface of
the ECU Interface Manager
ECU Interface Software / dSPACE Calibration and Bypassing Service
dSPACE Calibration and Bypassing Service

ECU service for measurement, calibration, bypassing, and ECU flash programming
Highlights
n Measurement, calibration, and ECU flash
programming via DCI-GSIs

n Function bypassing via DCI-GSIs and DPMEM PODs
n Highly scalable service code
n Security and data consistency mechanisms for bypassing

Application Areas
ECU calibration based on on-chip debug interfaces typically requires a special service implementation on the ECU
to measure data consistently and synchronously according
to given ECU rasters. In addition, for function bypassing it
is usually necessary to implement service calls (bypass
hooks) in the ECU code to establish synchronized communication between the ECU and the prototyping system.
Key Benefits
The dSPACE Calibration and Bypassing Service allows you
to perform measurement, calibration, and bypassing tasks
in parallel. Flexible configuration options make it possible
to tailor the service implementation on the ECU with regard
to functionality and resource consumption. Special mechanisms for bypassing guarantee minimal latencies, data
Using the dSPACE Calibration and Bypassing Service, you

can run measurement, calibration, and ECU flash programming tasks via DCI-GSIs. The service is also designed for
bypassing ECU functions by means of the RTI Bypass Blockset in connection with DPMEM PODs and the DCI-GSIs.
consistency and automatic failure checking. The dSPACE

Calibration and Bypassing Service can be integrated into
the ECU software either by inserting it into the source code
manually or by using the ECU Interface Manager. dSPACE
provides consulting and engineering services to help you
integrate the service into your ECU.

Software
Optional
Order Number
n
dSPACE ECU Flash Programming Tool (p. 235)
n
DSPACE_ECU_FLASH
n
ECU Interface Manager (p. 226)
n
See p. 227
n
RTI Bypass Blockset (p. 62)
n
RTIBYPASS_BS
Hardware
Optional
230
Order Number
n
Generic Serial Interfaces (DCI-GSIs)
See p. 573/p. 575
n
Customer-specific DPMEM PODs
See p. 576
2015
ECU Interface Software / dSPACE Internal Bypassing Service
Introduction

Using an existing ECU for function development
Application Fields
Highlights
n ECU service for internal bypassing and on-target
prototyping
n Compatible with Internal Bypass Plug-In for
also provides mechanisms to ensure data consistency and

safe operation. The dSPACE Internal Bypassing Service
requires a few bytes in the ECU RAM, and with typical
applications, only about 2 kB in the ECU flash. The dSPACE
Internal Bypassing Service can be integrated into the ECU
software either by inserting it into the source code manually or by using the ECU Interface Manager.
Hardware
Key Benefits
The dSPACE Internal Bypassing Service supports servicebased bypassing on the target ECU. Once the bypass service
and the associated bypass hooks are integrated in the ECU
code, control engineers can perform controller design in
the Simulink model, flexibly defining which ECU variables
are to be read or written as input or output variables for
the internal bypass functions and which bypass functions
are to be triggered by the hooks. Service-based bypassing
Engineering
source code and referenced later on during function development in the Simulink model. Free areas in the ECU RAM
and flash memory are used to implement internal bypass
functions.
Order Information
Product
Order Number
n
Please inquire
Relevant Software
Software
Optional
Order Number
n
ECU Interface Manager (p. 226)
n
See p. 227
n
RTI Bypass Blockset (p. 62)
n
RTIBYPASS_BS
n
Internal Bypass Plug-In for RTI Bypass Blockset
n
RTIBYPASS_BS_INT
2015
231
Application Areas
Internal or on-target bypassing allows new functions to be
prototyped and tested directly on the ECU. The ideal tool
for this is the Internal Bypass Plug-In for the RTI Bypass
Blockset, which is based on the dSPACE Internal Bypassing
Service. Associated bypass hooks can be placed in the ECU
Software
RTI Bypass Blockset

n Only tiny footprint in the ECU RAM and flash
ECU Interface Software / dSPACE XCP Service
dSPACE XCP Service

ECU service for measurement, calibration, bypassing, and ECU flash programming via XCP
Highlights
n Support of transport layers for CAN and Ethernet
n Highly scalable service code
n Calibration, measurement and bypassing in parallel
n Safety and data consistency mechanisms for bypassing

Application Areas
The Universal Measurement and Calibration Protocol (XCP)
is the successor to the well established CAN Calibration
Protocol (CCP). XCP is standardized by the Association for
Standardisation of Automation and Measuring Systems
(ASAM).
The dSPACE XCP Service supports transport layers for CAN
and Ethernet (UPD/IP and TCP/IP). It is designed for various
Key Benefits
Depending on the transport layer, the dSPACE XCP Service
covers various aspects of XCP, from measurement and ECU
calibration to bypassing and ECU flash programming.
Flexible conguration options make it possible to tailor the
service implementation with regard to functionality and
resource consumption in the ECU.
use cases during ECU development such as measuring ECU

variables and calibration, and also for ECU flash programming in connection with CAN.
The dSPACE XCP Service implementation is also dedicated
to bypassing ECU functions using the dSPACE real-time
prototyping platforms MicroAutoBox II1) and AutoBox.
For bypassing, dedicated mechanisms are provided to guarantee minimal latencies, data consistency, and automatic
failure checking. In addition, you can run measurement,
calibration, and bypassing tasks in parallel on the same ECU.
dSPACE provides consulting and engineering services to help
you integrate the dSPACE XCP service into your ECU.
Order Information
232
Product
Order Number
dSPACE XCP Service
n
DSPACE_XCP_SERVICE
2015
1)
ECU Interface Software / Variable Editor
Introduction
Variable Editor
Visualize, edit, and create ECU description files
Application Fields
Highlights
n Create and edit ECU description files (A2L files)
n Update address information of ECU variables from
map files
n Automate address update and A2L file generation
widely adopted the A2L file format as a de-facto standard.

The dSPACE Variable Editor is a stand-alone tool especially
tailored to the ECU software development phase. New A2L
files can be created from scratch or existing ones can be
imported and modified. The editor is fully compatible with
the ASAM MCD-2 MC standard.
Hardware
Application Areas
An A2L file according to the ASAM MCD-2 MC standard
(formerly ASAP2) contains all the information about measurement and calibration variables in the ECU. This includes
information on the variables memory addresses and conversion methods, the memory layout and data structures in the
ECU and communication parameters for the measurement
and calibration interface. The automotive industry has
Software
via a command line interface
Engineering
In addition, the Variable Editor allows selected variables to

be exported and imported and new or modified variables
to be exchanged between users.
2015
233
Key Benefits
The Variable Editor serves to visualize, edit, and create ECU
description files. Any number of A2L files can be imported
into the editor, making it easy to copy and paste selected
variables and groups into an existing or new description file.
This makes it possible to generate subsets of existing A2L
files and to merge the contents of multiple files.
With the integrated map file manager, linker map files can
be assigned to an ECU description file to update address
information at a click.
ECU Interface Software / Variable Editor
Main Features
n Import of any number of A2L files
n Export of ECU description files according to the
ASAM MCD-2 MC standard
n Visualization, editing, and creation of A2L files
n Export and import of selected variables
n Option to copy and paste variables and groups
between A2L files and to create subsets
n Map file manager to assign any number of map files
to a variable description
n Option to automatically create variables from symbols
in map files
n Address updates from map files at a click
n Dialog-based configuration of variables
n Convenient filter and search mechanisms
n Command line interface to automate address update
and ECU description file generation

Variable Editor and configuration dialog for measurement variables.
Multiple A2L (ASAM MCD-2 MC) files imported in Variable Editor.

A new variable description can be created by copying and pasting
variables or groups from existing A2L files.
Order Information
234
Product
Order Number
Variable Editor
n
DSPACE_VAR
2015
ECU Interface Software / dSPACE ECU Flash Programming Tool
Introduction

ECU flash programming via measurement and calibration interfaces
Application Fields
Highlights
n Fast ECU flash programming during development
n Stand-alone tool or integrated in ControlDesk
Next Generation
n Safety mechanisms against misoperation
and programming errors
Hardware
Key Benefits
The dSPACE ECU Flash Programming Tool can be seamlessly integrated into ControlDesk Next Generation (p. 106)
or used as a stand-alone device. The tool lets you configure
user rights for different roles, such as calibration engineer
or flash programming expert. Reliable ECU flash programming is guaranteed by flash data identification and consistency mechanisms. Very fast ECU flash programming can
be implemented by using the DCI-GSI1 or the DCI-GSI2.
dSPACE provides consulting and engineering services to help
you to set up a flash programming solution for your ECU.
Engineering
Application Areas
The ECU development process frequently requires new
software versions and data sets to be programmed for the
ECU. This can be done conveniently via the existing measurement and calibration interface. With the ECU Flash
Programming Tool you can program control units via XCP on
CAN, XCP on Ethernet, or via the dSPACE devices DCI-GSI1
and DCI-GSI2.
Software
Order Information
Product
Order Number
n
DSPACE_ECU_FLASH
2015
235
ECU Flash Programming Tool.
RealTime Models / Automotive Simulation Models
Automotive Simulation Models

Simulating the engine, vehicle dynamics, electrical system, and traffic
Highlights
n
Open MATLAB/Simulink models
n
For ECU testing and function development
n
Intuitive graphical parameterization, and road,
maneuver, and traffic creation in ModelDesk
236
Application Areas
The Automotive Simulation Models (ASM) are open Simulink
models for the real-time simulation of passenger cars and
trucks as well as their components. They are used as plant
models for the development and testing of engine controls,
vehicle dynamics controls, on-board power electronics and
driver assistance systems.
The ASMs typically run on a dSPACE Simulator/SCALEXIO
for hardware-in-the-loop (HIL) testing of electronic control
units (ECUs) or during the design phase of controller algorithms for early validation by offline simulation.
Key Benefits
All the Simulink blocks in the models are visible, so it is easy
to add or replace components with custom models to adapt
the properties of modeled components perfectly to individual requirements. The ASMs standardized interfaces
make it easy to expand a single model such as an engine
or body, or even create a whole virtual vehicle. Roads and
driving maneuvers can be easily and intuitively created using
graphical tools with preview and clear visualization.
Modular Concept
The ASM concept consists of coordinated, combinable models
of automotive components. There is a vehicle model with
a trailer, plus other ASMs for gasoline, diesel and hybrid
engines, exhaust systems, turbochargers, brake hydraulics,
electrical systems, electric motors, environment sensors,
roads and traffic. The ASMs support a whole range of
simulations from individual components to complex virtual
traffic scenarios.
Offline and Online Simulation

The ASMs can be used in combination with real controllers
in a hardware-in-the-loop environment (HIL or online mode),
or for model-in-the-loop simulations (PC or offline mode).
The same model configurations and parameters can be used
seamlessly throughout all the steps from function development to ECU testing.
2015
Introduction
Real-Time Models / Automotive Simulation Models

Feature
Description
Benefit
Open Simulink models
n
Almost all models are open down to the Simulink block level
n
Custom models can easily be added or used to
ModelDesk
n
Graphical user interface with parameter and simulation
n
Easy, intuitive parameterization and seamless
Online simulation
Offline simulation
ASMSignalBus
Online tunable parameters
Model interoperability
n
Real-time simulation on real-time hardware
n
Hardware-in-the-loop simulations with ECUs
n
Simulations as early as the design phase
n
Controller validation in early development stages
n
Simulation signals are part of a structured Simulink signal bus
n
Standardized and fast access to model variables
n
Direct parameter access during real-time simulations
n
Online parameter optimizations and behavior studies
n
ASM models are easy to combine to create a virtual vehicle
n
An entire virtual vehicle can be simulated
replace model components

simulation handling
Application Fields
management
Order Information
Classification
Type
Order Number
Packages
ASM Gasoline Engine Basic Simulation Package

ASM Gasoline Engine Simulation Package
ASM Diesel Engine Simulation Package
ASM Gasoline Engine InCylinder Simulation Package
ASM Diesel Engine InCylinder Simulation Package
ASM Vehicle Dynamics Simulation Package for VEOS
ASM Vehicle Dynamics Simulation Package
ASM Truck and Trailer Simulation Package
ASM Turbocharger
ASM Electric Components
XSG Electric Components
XSG Electric Components Solution Simulink Blockset (FPGA part)
XSG Electric Components Solution Simulink Blockset (processor part)
ASM Brake Hydraulics
ASM Diesel Exhaust System
ASM Traffic
ASM Pneumatics
ASM KnC
n
Please inquire
n
Please inquire
Software
n
Please inquire
n
Please inquire
n
Please inquire
n
Please inquire
n
Please inquire
n
ASM_L_TC
n
ASM_L_EC
n
Please inquire
n
FPGA_XSG_EC
n
FPGA_XSG_EC_IF
n
ASM_L_BH
Hardware
Libraries
n
Please inquire
n
ASM_L_DEXH
n
ASM_L_TRF
n
ASM_L_PNEU
n
ASM_L_KNC

Software
Required
n
MATLAB/Simulink from MathWorks
Engineering
n
Simulink Coder (formerly Real-Time Workshop)2)
n
Simulink Accelerator1)
dSPACE implementation software

dSPACE experiment software
Additional software
Operating system
n
Real-Time Interface (RTI) 2)
n
ControlDesk2) Next Generation
n
Microsoft Excel
n
Required
Minimum system
n
Pentium4 processor, 1.4GHz or higher
n
Memory = 2GB RAM
n
Graphics accelerator card matching the requirements of MotionDesk3)
Recommended system
n
Intel Core i5 Processor, 3 GHz or higher
n
Memory 4GB RAM
n
Dual-head graphics accelerator card matching the requirements of MotionDesk3)
SCALEXIO or dSPACE Simulator (equipped with DS1005 PPC Board or DS1006 Processor Board)4)
Offline simulations only
Online simulations only
3)
Graphics accelerator required for MotionDesk which is part of the ASM Vehicle Dynamics Simulation Package.
More details on graphics card requirements and compatibility at www.dspace.com/go/mdhwrequ
4)
ASM Traffic, ASM Truck, ASM Trailer, and ASM Engine InCylinder Models support the DS1006 only.
1)
2)
2015
237
Hardware
Introduction
Why Use Simulation? Why Use Models?
In model-based design (MBD), simulation is a widely used
and proven method. It is applied to test and validate control
algorithms in a virtual world instead of on the real controlled
device. For automotive applications this ranges from simulated individual components, such as engines, to complete
virtual vehicles, up to virtual environments consisting of a
vehicle and its surrounding traffic, traffic signs, and so on.
Virtualized controlled device (vehicle)
and controller (ECU) in a control loop.
ASM Simulation Tool Suite

The Automotive Simulation Models (ASM) from dSPACE are
a simulation tool suite covering four application areas:
combustion engines, electric components, vehicle dynamics
and the traffic environment. These ready-to-use simulation
models exactly represent the behavior of the controlled devices. The ASM tool suite is designed to fully comply with the
MBD approach. All models are implemented with MATLAB/
Simulink.
Tool suite for simulating engines, electric
components, vehicle dynamics and traffic.
Simulation Platforms
The support of multiple platforms allows for seamless
simulation processes from model-in-the-loop (MIL) to software-in-the-loop (SIL) to hardware-in-the-loop (HIL). The
ASM tool suite can be executed on different simulation
platforms: SCALEXIO, dSPACE Simulator, VEOS, or a PC
running MATLAB/Simulink. Depending on the platform,
simulations can be performed either with the controller
software or the controller hardware (ECU) in the control
loop. In either case the simulation model stays the same.
The ASM simulation tool suite supports mutiple simulation platforms.
238
2015
Introduction
Philosophy
Application Fields
Supports Model-Based Design

n
Real-time-capable Simulink models
n
Provides access to internal modeling details, down to
block level
n
Supports all stages of controller software development
(MIL, SIL, HIL)
n
Soft-ECU network
n
Signal interfaces for automotive applications
Ready-to-use Commercial-off-the-Shelf (COTS) Models

n
One integrated tool chain for parameterization,
validation and test automation

n
Open documentation, including mathematical equations
Software
n
Supports migration, including between MATLAB releases
n
Worldwide customer base and mature models
Comprehensive Engineering and HIL Knowledge

n
The one-stop supplier for all HIL-relevant tasks
n
Customer training and worldwide support
n
Combination of COTS models and custom specific
model engineering
2015
239
Engineering
Hardware
Complete ASM Product Portfolio

n
Supports all automotive-relevant modeling areas
n
Easily combinable models for building virtual vehicles
n
Different levels of model complexity (e.g. mean value,
physical) for all controller design and test use cases
Combustion Engine Simulation

Realtime models for diesel and gasoline engine simulation
Simulation Packages and Models
n
Diesel and gasoline engines
n
Mean-value and physical plant models
n
Physical turbocharger
n
Diesel aftertreatment system
Graphical parameterization of the

engine model for precise simulations.
Example Use Case: Engine Model Parameterization

Task
Parameterizing combustion engine models.
Challenge
To parameterize real-time-capable engine models by using
engine test bench data in combination with system parameters.
Solution
ModelDesk now provides a sophisticated processing feature
which enables a flexible data handling, function definition
and parameter organization for combustion engines.
240
2015
Introduction
ASM Gasoline Engine Basic

Basic mean-value engine model with combustion torque modulation
Simulation Model Characteristics

The actual physical engine characteristics are represented
by a mean-value engine model with crank-angle-based
torque generation, dynamic manifold pressure, temperature
calculation, and an injection model. To simulate the engine
in an automotive system (car or truck), the engine model
incorporates a longitudinal drivetrain model with manual
and automatic transmission, a clutch, a torque converter, a
starter, and a test bench mode. Models for the environment
and driver complement the virtual powertrain.
AirPath
TurboCharger
Throttle
IntakeManifold
Software
Application Fields
Features at a Glance
n
Unrestricted number of cylinders
n
Intake manifold with calculation of intake manifold
pressure and temperature
n
Map-based turbocharger for boost pressure
calculation
n
Fuel injection system with fuel tank model
n
Wall film evaporation taken into account
n
Longitudinal driver for standard cycles (FTP75, NEDC,
J10-15, )
n
NEW: Graphical preprocessing support in ModelDesk
n
Simulation with real ECU in hardware-in-the-loop (HIL)
system and simulated soft ECU in model-in-the-loop
simulation
n Start/stop system support
FuelSystem
Hardware
Main Model Components

n
Air system
n
Fuel system
n
Piston engine
n
Turbocharger
n
Drivetrain (basic)
n
Vehicle dynamics (longitudinal)
n
Environment (basic)
qinj
Engine- EngineCooling Combustion
nEngine
Trqeng
Engineering
More detailed information available

n
www.dspace.com/asm
2015
241
Schematic of the air system.
ASM Diesel/Gasoline Engine

Mean-value engine models with combustion torque modulation
n
Air system
n
Fuel system
n
Piston engine
n
n
Turbocharger
n
Drivetrain (basic)
n
n
Environment (basic)
n
Up to 20-cylinder diesel/gasoline applications
n
Map-based turbocharger for boost pressure
calculation
n
Gasoline fuel injection system: common-rail system
including direct injector, intake-manifold injector and
tank model
n
Gasoline engine with homogenous and stratified
combustion modes
n
Diesel fuel injection systems: common rail injector,
unit injector, unit pump and tank model
n
Diesel exhaust system including diesel oxidation catalyst (DOC) and diesel particulate filter (DPF)
n
Exhaust-gas recirculation (EGR) of exhaust and unburned
air with EGR cooler

n
Low pressure EGR
n
Longitudinal driver for standard cycles (FTP75, NEDC,
J10-15, )
n
Simulation with real ECU in hardware-in-the-loop (HIL)
systems and simulated soft ECU in model-in-the-loop

simulation
n NEW: Graphical preprocessing support in ModelDesk
n Start/stop system support

The physical engine characteristics are represented by a
mean-value engine model with crank-angle-based torque
n
www.dspace.com/asm
modulation, dynamic manifold pressure, temperature calculation, and several fuel injection models. A soft ECU is
included for scenarios where a real ECU is not available, for
example, in offline simulation.
AirPath
Intercooler
Throttle
IntakeManifold
To simulate the engine in an
q
automotive system (car or truck),
the engine model incorporates
Pos
TurboCharger
a longitudinal drivetrain model
EGR
Compressor
with manual and automatic
Pos
EGR
transmission, a clutch, a torque
Valve
n
Engine- EnginePos
Cooling Combustion
converter, a starter, and a test
VTG
bench mode. Models for the
Turbine
EGR
environment and driver compleCooler
ment the virtual powertrain.
inj
Thr
EGR
TC
Wastegate
242
FuelSystem
Manifold
Injection
FuelSystem
Direct
Injection
qinj
VGT
PosWGT
ExhaustManifold
2015
neng
Trqeng
Introduction
ASM Diesel/Gasoline Engine In-Cylinder

Real-time engine models with in-cylinder pressure and temperature simulation
n
Air system
n
Fuel system
n
Valve system
n
Piston engine
n
n
Turbocharger
n
Drivetrain (basic)
n
n
Environment (basic)
n
Diesel applications with up to 12 cylinders with common
real time: for example, in response to injection or

variable valve timing
Application Fields
Software
n
Simulation of in-cylinder pressure and temperature in
rail and turbocharger for real-time simulation. Unlimited

number of cylinders for offline simulation
n Gasoline applications with up to 12 cylinders with direct
or port injection and turbocharger for real-time simulation.
Unlimited number of cylinders for offline simulation
n
Diesel: multiple injection patterns such as pre-, main
and post-injection
n
Gas exchange simulation related to the lift of the intake
and exhaust valves
n
Fuel injection systems: common rail injector (Diesel),
direct or port injection (Gasoline)
n
Exhaust-gas recirculation (EGR) of exhaust and fresh air
with EGR cooler
n
Start/stop system support

The ASM Diesel Engine In-Cylinder Simulation Package and
the Gasoline Engine In-Cylinder Simulation Package are
open Simulink models for developing and testing electronic control units (ECUs) with engine management based
on the in-cylinder pressure. The models simulate in-cylinder
pressure in real time by means of a zero-dimensional thermodynamic approach. The diesel combustion process simulation can handle multiple injection patterns such as pre-,
Air path
Intercooler
Throttle
Hardware
main and post-injection. In the combustion process, gas

exchange simulation is related to the lift of the intake and
exhaust valves. The gas-dynamical behavior of the air path
and exhaust path is implemented as a mean value system
with manifold pressure, temperature, and mass calculation.
The inlet and exhaust valves are modeled as isentropic orifices.
They can handle variable valve timing (VVT), variable valve
lift (VVL), and the simulation of engines without a camshaft.
To simulate the engine within
an automotive system (car or
FuelSystem
Intake manifold
q
Manifold
Injection
truck), the engine model incorporates a basic longitudinal
Intake valve FuelSystem
Direct
drivetrain model. Models for
Injection
the environment and driver
q
complement the virtual power
Engine
Engine
combustion
cooling
train.
PosThr
Turbo charger
EGR
PosEGR
nTC
PosVGT
EGR
Valve
VTG
Turbine
inj
neng
Trqeng
EGR
Cooler
Exhaust valve
PosWGT
Wastegate
Exhaust manifold
More detailed information

available
n
www.dspace.com/asm
2015
243
Compressor
Engineering
inj
ASM Turbocharger
Physical turbocharger model
n
Compressor
n
Turbine
n
Wastegate valve
n
Calculates air path with the precision of a physical model
n
Wastegate valve and variable turbine geometry (VTG)
n
Turbine power and turbine output temperature
n
Temperature calculated according to isentropic
efficiency
n
Turbine mass flow and efficiency in maps
n
Compressor power and output temperature
n
Compressor pressure ratio and efficiency in maps
n
Alternative to map-based model
n
Switching between the two models
n
Support of diesel and gasoline engine models
n
Support of SAE J922 turbine model data format
n
Double stage turbocharger
n
Heat loss calculation

The Turbocharger Model is an extension for the diesel and
gasoline engine models. It provides a more realistic model
of turbocharger components and the engine air path
than the map-based turbochargers models. It simulates an
exhaust gas turbocharger that consists of a compressor, a
turbine, and a turbocharger shaft. Turbochargers with
variable turbine geometry (VTG) and wastegate can be
simulated.
The turbine model calculates the mass flow, the output
temperature, and the resulting power output according to
wastegate or VTG position. The compressor and turbine are
connected by a shaft, and the model provides the shaft
speed. The compressor model calculates the boost pressure
and the temperature in the compressor, using the equations
for compressor power and compressor output temperature.
n
www.dspace.com/asm
244
TurboCharger
Compressor
nTC
PosVGT
VTG
Turbine
Wastegate
PosWGT
Schematic of the turbocharger system.
2015
Introduction
ASM Diesel Exhaust System
Components and Characteristics

n
Lumped parameter model
n
One-layer approach
n
Filter regeneration support
Diesel Oxygen Catalyst Model

The diesel oxygen catalyst model simulates the physical
effects of an oxidation process on the exhaust gas.
The underlying but unmodeled chemical process can be
described by using excess O2 (oxygen) in the exhaust gas
stream to oxidize CO (carbon monoxide) to CO2 (carbon
dioxide) and HC (hydrocarbons) to H2O (water) and CO2.

n
Pressure drop over DOC/DPF
n
Temperature before and after DOC/DPF
n
Lambda before and after DOC/DPF
n
Particulate mass in DPF
n
DPF regeneration by post-injection or additional injection
Selective Catalytic Reduction (SCR) Model

For NOx reduction, a model with selective catalytic reduction
(SCR) is included. The model calculates the physical and
chemical processes of AdBlue injection into the exhaust gas.

n
Zero-dimensional approach
n
Series connection of identical cells
n
Number of cells represents the sectional discretization
n
Outputs of one cell are inputs of the following cell
n
Adblue dosing system with and without air supply
n
Urea decomposition upstream of the SCR catalyst
Software
Diesel Particulate Filter Model

The diesel particulate filter model is designed to remove
diesel particulate matter (DPM) from the exhaust gas.
Hardware
Diesel Aftertreatment System

The diesel aftertreatment system is a combination of
models of an oxidation catalyst, a particulate filter, and a
selective reduction catalyst. The system assumes an ideal
gas with a steady gas constant. The different catalyst and
filter models can be combined in any order. During simulation the pressure drop over the aftertreatment system is
calculated as well as the temperatures and lambda of the
exhaust gas before and after the system.

n
www.dspace.com/asm
Schematic of the diesel exhaust system with DOC, DPF and SCR models.
2015
245
Engineering

n
Diesel oxidation catalyst (DOC)
n
Diesel particulate filter (DPF)
n
Selective catalytic reduction (SCR)
n
Support of all ASM engine diesel models
Application Fields
Real-time diesel aftertreatment system
Electric Components Simulation

Realtime models for vehicle electrics and traction system simulation
n
Electric components including drives and batteries
n
FPGA-based plant models
Parameterization of vehicle electric systems,

drives, and further electric components.
Example Use Case: Parallel Hybrid Drivetrain Simulation

Task
Testing controllers for engine, transmission or drivetrain
management in hybrid drivetrain applications.
Challenge
To perform a detailed simulation of hybrid drivetrain applications including soft ECUs for adequate restbus simulation.
Solution
ASM Electric Components now supports the simulation of
parallel hybrid drivetrain applications in combination with
ASM Engine Gasoline or ASM Vehicle Dynamics. The library
includes all required components, such as drive motor, battery, and clutches. Demo models including soft ECUs for
hybrid management are available.
246
2015
Introduction
ASM Electric Components

Automotive electrical system and electrical drives simulation
n
Ready-to-use components with automotive features
n
Prepared for testing battery management controllers
Application Fields
n
Simulation of a complete automotive electrical system
n
Simulation of electric drive components and power
electronics in a closed loop with ECU

n
NEW: Demo models for simulating a hybrid vehicle or
powertrain with ASM Vehicle Dynamics or ASM Engine

simulation models (support from dSPACE Release 2015-A).
n
Variable sample times for pulse width modulated
(PWM)-synchronous calculation
n

PMSM machines with current-dependent differential
inductances
Software

n
Battery
n
Multi cell battery
n
Starter
n
Alternator
n
Loads
n
Electric motors (DC, BLDC, PMSM,
asynchronous AC induction motor)
n
Controllers
n
Various auxiliary blocks
n
Three level inverter
n
NEW: Discontinuous conduction mode (DCM) inverter
Hardware
features. These models are also optimized for real-time HIL

simulation. The closed-loop components are ideal for HIL
simulation of electric devices such as drives or inverters in
a closed control loop. The models offer variable sample
times for pulse width modulated (PWM)-synchronous model calculation and optimized solvers for real-time simulation.
ASM Electric Components can be combined with other ASM
products such as the engine models and the vehicle dynamics model and is equipped with demo models.
Electric
Motor
Engineering

n
Product Brochure: ASM Electric Components Model
n
www.dspace.com/asm
Transmission
AC/DC
3-Phase
Power
Converter
Schematic of a basic electrical system.
Battery
Schematic of a hybrid powertrain system.
2015
247

ASM Electric Components provides models for the real-time
simulation of a vehicles electrical system. Applications can
range from electric drives and inverters for closed-loop
simulation with an electric drive controller to a complete
automotive electrical system including battery, starter,
alternator, and loads. Typical use cases are the simulation
of realistic battery behavior during starter activation, electric
drives that are integrated into a hybrid electrical vehicle
(HEV) power train, etc. ASM Electric Components consists
of automotive electrical system simulation components and
closed-loop simulation components. The former can be used
directly to create the electric circuits of an automotive system, since they already have all the necessary automotive
ASM Multi Cell Model

To simulate high voltage batteries like Li-ion consisting of
series of multiple battery cells the ASM Electric Component
Model features a cell simulation model. The ASM cell model
consists of a cell voltage model and a charge state model.
With the cell voltage model, individual physical effects such
Reference and Delta Models

The approach used in ASM is to connect single cells of
identical design to create a series string of cells. This consists
of a reference cell model that describes the basic behavior
of the cell type used, and a delta model that computes the
deviation of each individual cells voltage from the reference
voltage. The capacity, initial charge state and deviation from
the reference value of the internal resistance can be specified
for each cell.
Terminal current
of battery
Reference cell
model provides
reference terminal
voltage
Terminal voltage
of reference cell
as internal resistance, diffusion and double-layer capacity

can be parameterized. The charge state model deals with
the cells charge and discharge currents, and also with leakage currents such as those caused by gassing effects in the
charging of NiMH cells.

n
Real-time capable simulation of multiple battery cells
n
Complexity of the model is independent of the number
of cells
n
Parameterization for Li-Ion, NiMH, Pb, etc.
n
Individual physical effects such as internal resistance,
diffusion and double-layer capacity
n
Supports charge, discharge, and leakage currents
n
Online and offline simulation
n
Supports dSPACEs cell voltage emulation hardware
n
Graphical parameterization in ModelDesk
n
Supports simulation of serial and parallel connected
battery modules
EV1077
ECU
battery
management
Vcell
I bal
C1
C2
Reference resistance
and charge state
C4
Voltage differences
of cells
The ASM cell model consists of a reference cell model, and a delta
model that computes the deviation of each individual cells voltage
from the reference voltage.
CAN
bus
EV1077
C5
C6
Vehicle ECUs
C7
C8
ASM Multi Cell Model
Balancing current
C3
Cell module
Delta model
for calculating
deviations in cell
voltage based on
individual parameters
Terminal
voltages of
cells
Simulator
Cell voltage emulation with high precision voltage amplifiers

(EV1077) controlled by the ASM Multi Cell Model.
248
2015
Introduction
XSG Electric Components

Plant models for FPGA-based simulations
Components and Characteristics:

n
Permanent magnet synchronous motor (PMSM)
n
Brushless DC motor (BLDC)
n
NEW: Advanced inverter model supporting DCM
(Discontinuous Conduction Mode)
n
Asynchronous Squirrel cage induction motor
n
Resolver, Sine, TTL, and Hall encoder
n
XSG EC Lib contains XSG utlis offering further
Functionality (see page, 94)
Example of a Simple Electric Drive Application

The FPGA carries
n
The motor model
n
The model for the three-phase inverter
Benefits
n
High precision and stability
n
Very high oversampling rate corresponding to
the PWM switching frequency
n
No PWM synchronization necessary
n
Current ripple (PWM effects) can be simulated
n
Better precision in simulating higher fundamental
frequencies
n
Open models can be modified or partly replaced
by users
n
Run-time license available
n
Parameterization for the FPGA models
Highly Nonlinear Electric Motor Models

n
Inductance and flux depending on stator current
n
Spatial harmonics
n
Continuous integrated parameterization workflow
from FEA tool JMAG-RT to FPGA model

n
Available on request
1)
Please note that due to the introduction of the Vivado software, Xilinx will no longer support the Xilinx System Generator for DSP
2015
249
The processor carries

n
The mechanics model
Engineering
Hardware
Direct FPGA I/O Access

In addition to the plant models, the XSG Electric Component Library is supplemented by enhanced I/O functions
from the contained XSG Utils Library on the DS5203/DS2655
FPGA Boards, e.g., for timing analysis and capturing digital
input sources.
The XSG Electric Components Library and the DS5203/
DS2655 FPGA Boards can be used together for E-motor
simulation both on signal and on power level.
Software
Application Fields
Application Examples
Electric motor control applications that demand very high
precision and correspondingly high sample rates are
simulated best on field-programmable gate arrays (FPGA).
To support identical workflows for controller development
and testing, the XSG Electric Component Models (closedloop simulation components) are implemented as Xilinx
System Generator (XSG)1) models that run on a dSPACE
DS5203 (p. 438, PHS Systems) or DS2655 (p. 311, for
SCALEXIO) FPGA Boards. Closed-loop simulations of electric
devices and their controls are supported at very high sample
rates in real time.
Vehicle Dynamics Simulation

Realtime models for ground vehicle simulation
n
Passenger cars
n
Trucks
n
Trailers
n
Brake hydraulics and pneumatics
Parameterization of the vehicle

dynamics model.
Example Use Case: Electric Power Steering (EPS)

Task
Developing and testing power steering control functions.
Challenge
To frontload function analysis and validation for EPS controls
by means of simulation.
Solution
Simulating steering behavior with ASM Vehicle Dynamics
and a new sophisticated steering model. The steering model simulates up to 3 DoF and supports rack-based as well
as pinion-based EPS. The model includes different types of
interfaces for simulation with mechanical test benches.
250
2015
Introduction
ASM Vehicle Dynamics

Vehicle multibody system plus drivetrain, roads, maneuvers, and driver
Application Software
n
ModelDesk

n
Several strategies (injection, throttle) for reducing and
increasing torque as requested by an ESP/TCS ECU
n
Starter to accelerate the engine to idle speed
Drivetrain Model
The drivetrain model has manual and automatic transmission, and front-, rear-, and all-wheel-drive. The shaft drives
are modeled as elastic components.

n
Clutch with elasticity (torsion spring)
n
Elastic shafts included
n
Front-, rear-, and all-wheel drive including differentials
n
Manual and automatic transmission with torque
converter
n
Model stabilized by semi-implicit Euler integration
method
n
Drivetrain with 13 degrees of freedom (DoFs)
Overview of the drivetrain model configured

with allwheel drive. Modes for rear and
frontwheel drive are also available.
2015
251
Engineering
Engine Model
Included table-based engine that supports ECU interventions. It can be easily replaced by a full-featured gasoline or
diesel engine model.
Software
Application Fields
n
MotionDesk
Hardware

n
Engine (table based)
n
Drivetrain
n
Vehicle dynamics
n
Environment
n
Brake hydraulics and pneumatics
n
NEW: 3DoF steering model

Vehicle Multibody System Model
The system is modeled as a nonlinear vehicle multibody
system with geometrical or table-based suspension kinematics and table-based compliances. It supports the simulation
of vertical, longitudinal, and lateral dynamics.
ASM Kinematics and Compliance (KnC) Testbench
ASM Kinematics and Compliance (ASM KnC) is an add-on
to the ASM Vehicle Dynamics model that provides functions
for designing and simulating wheel suspensions on a virtual test bench. Users can run virtual tests for numerous
vehicle variants and driving maneuvers to optimize vehicle
suspensions and make them available for hardware-in-theloop (HIL) applications.

n
Multibody system (MBS) consisting of car body
and four wheels
n
10 degrees of freedom (DoF)
n
Table-based kinematics and compliances for suspensions
n
Suspension with nonlinear spring and damper
characteristics
n
Aerodynamics forces and torques included
n
Brake model incl. physical brake booster model
n
Additional masses (fixed on vehicle body)
n
NEW: Sophisticated steering model with 3DoF,
friction elements and rack and pinion based EPS support.
n
Tire models: Magic Formula and TMEasy
n
Data import from suspension design tools like ADAMS
available on request
Item
Virtual kinematics and

compliance (KnC) test bench.
Elastic powertrain
13
Body
Steering rod
Wheels
41)
1)
Environment
The environment features models for road, maneuver and
driver. Roads and maneuvers are generated in ModelDesk.
DoF
One independent degree of freedom per wheel for wheel vertical

displacement. The wheel kinematics are included via the MBS
algorithm.
More detailed information

available
n Product Brochure:
n www.dspace.com/asm
n
Driver with lateral and longitudinal control
n
Roads consisting of segments with slope, inclination
and individual profiles

n
Driving maneuvers from ModelDesk or manual driving
A road consists of segments that can be configured individually:

bumps, a longitudinal and lateral inclination, etc.
252
2015
Introduction
ASM Truck
Truck model for tractor and trailer simulation
Software
n
Table-based axles with 3 DoF
n
Twin tires as an option on all axles
n
Axles can be activated and deactivated during simulation
n
Trailers can be hitched and unhitched during simulation
n
Dolly extension for road train simulation
n
Vehicle configurations with arbitrary numbers of axles
Hardware
available on request
n
Truck cabin with additional DoFs
Examples of trailer and axle variants supported by ASM Truck and ASM Trailer.
2015
253
Engineering

n
Multibody dynamics with up to 36 DoF
(depends on truck configuration)
n
Powertrain with 25 DoF (depends on truck configuration)
n
Truck body based on a torsional frame
n
Tractor with up to 4 steerable axles plus trailer with up
to 4 steerable axles
n
Hydraulic or pneumatic brake system (ASM Brake
Hydraulics, ASM Pneumatics)
n
Each wheel can be equipped with a brake
Application Fields
The Truck Tractor Model

ASM Truck is used together with ASM Trailer to simulate a
truck (tractor with dolly) or a tractor-semitrailer combination.
The models contain up to 34 degrees of freedom (DoF) in
the multibody dynamics and up to 25 DoF in the powertrain.
The truck model features a torsional frame. The entire
vehicle model has up to 8 steerable axles, which can have
twin tires as an option. It is easy to modify the configuration
even during run time without manipulating the model. For
example, during the simulation, axles can be activated and
deactivated, and trailers can be hitched and unhitched.
ASM Trailer
Trailer model with hitch and four axles
The Trailer Model for Cars and Trucks
ASM Trailer is an extension to the ASM Vehicle Dynamics
Simulation Package. It is based on a multibody system
consisting of a trailer body, up to 4 axles, and an optional
dolly. The model also includes suspensions, tires, brakes and
aerodynamics. The connection to the towing vehicle is
provided via a hitch that includes mechanical stops. The
trailer and all axles can be activated or deactivated during
simulation without new code generation.

n
Modular multibody system (MBS)
n
Trailer body
n
Up to 4 axles (all axles steerable)
n
Dolly extension for full trailer simulation
n
Tire models TMEasy and Magic Formula
n
Table-based suspension
n
Ball-joint hitch (including mechanical stops)
n
Brakes
n
Aerodynamics
n
Additional loads
n
The trailer can be configured as a semitrailer or it can have an optional dolly extension. It supports the simulation of road trains consisting of
a truck tractor and multiple trailers.
254
2015
Application Fields
Introduction
Engineering
Hardware
Software
The trailer model can be configured for different trailer types,

and it can be used with various towing vehicles.
Axle activation/deactivation
The trailer, axles, and wheels can be modified during simulation, e.g.,
trailer coupled/uncoupled, axles activated/deactivated, and the wheels
can have single tires or twin tires. No code generation is required.
2015
255
Trailer coupling/uncoupling
ASM Pneumatics
Air brake and air suspension models
Application Areas
n
Air brakes
n
Air suspensions
n
Supports ABS/EBS and suspensions (car, bus, truck,
truck dolly, tractor trailer, road train)
n
Complete model including compressor, tanks, valves,
and brake chambers

n
Ready to use ABS/EBS and suspension configurations
n
Support for mechanical/pneumatic backup functions
n
Support for trailer brake systems
n
Graphical user interface for parameterization
n
Offline and online simulation
n
Real-time capable
n
Modular, library-based implementation
n
Easy variable access
n
Add-on library for ASM Vehicle Dynamics, ASM Truck
and ASM Trailer
Pneumatics Model Concept

The pneumatics model provides ready-to-use confi gurations
for air brake and air suspension simulations. Handling and
parameterization are done via a comfortable graphical user
interface.
ASM Brake Hydraulics

Dualcircuit brake hydraulics
Hydraulics Model for Braking Systems
The modeled ESP braking system consists of a dual-circuit
hydraulics system. The model contains all the components
like valves, chambers, accumulators, pumps, and braking
cylinders that are necessary for simulating a standard stateof-the-art ESP braking system.

n
Linear and physical master brake cylinder model
n
Valves with continuously controllable cross-sections
n
Nonlinear, look-up-table based wheel brake cylinder
n
n
Active brake booster
n
Simulation of X- and II-brake system structures
256

n
Product Brochure: ASM Vehicle Dynamics
n
www.dspace.com/asm
2015
Introduction
Traffic Simulation
Realtime models for traffic and environment simulation
Software
Application Fields
Simulation Package
n
Traffic
Hardware
Graphical definition of an intersection.
Example Use Case: Pedestrian Recognition and Autonomous Emergency Braking

Task
Testing ADAS functions which rely on road-based object
information, such as the detection of crossing pedestrians.
Solution
Select VRUs from an object library in ModelDesk or define
them graphically in the Traffic Object Manager (TOM). Define sophisticated movements in ModelDesk. Simulate the
VRU together with the vehicle under test that is equipped
with sensor models and autonomous emergency braking
algorithms. Observe the simulated traffic scenario via highend animation in MotionDesk.
2015
257
Engineering
Challenge
To simulate moving vulnerable road users (VRU), such as
pedestrians or cyclists, in urban traffic scenarios, and to
detect these objects and their specific parameters with
sophisticated sensor models and avoid a collision.
ASM Traffic
Real-time environment simulation with traffic and objects
Features at a glance
n
Simulation of complex traffic scenarios
n
Road network simulation
n
Static and moving objects like traffic signs and
vulnerable road users
n
Multiple traffic sensor types supported
n
Graphical definition of roads, maneuvers,
and environment
(For information on defining traffic scenarios, please see the
Traffic Editor which is part of ModelDesk, p. 265)
Application Areas
ASM Traffic adds traffic and environment simulation to
dSPACEs Automotive Simulation Models (ASM). It supports
you in developing and testing advanced driver assistance
systems (ADAS) that react to other vehicles or objects, like
adaptive cruise control (ACC) and intersection assistants.
The model simulates a road network, the vehicle under test,
a multitude of fellow vehicles and the necessary environment.
The test vehicle can be equipped with multiple sensors for
object detection and recognition (ego-vehicle). ASM Traffic
is typically used for hardware-in-the-loop testing of electronic control units (ECUs) or for early function validation
by offline simulation during the design phase of controller
algorithms.

ASM Traffic consists of a graphical user interface (GUI) and
a set of simulation models that perform in real time. The
GUI provides several interfaces to define the necessary
components like road networks, traffic signs, traffic vehicles,
and sensors. Trajectories for all vehicles, objects and pedes-
258
Key Benefits
ASM Traffic is so flexible that any kind of traffic scenario
can be created to ensure thorough testing of ADAS controllers. It supports the creation of complex road networks, and
you can define sophisticated traffic maneuvers on the roads.
The simulated environment can consist of static and movable
objects, like traffic signs and pedestrians. Various sensor
models and user-definable sensors are available to detect
these objects. To test pre-crash functionalities, you can
define traffic scenarios that in real life could result in an
accident, and observe system behavior under challenging
conditions. Traffic scenarios can be modified and immediately simulated without having to generate code again.
trians are calculated in real time according to the defined

traffic maneuvers. ASM Traffic supports specific scenarios
such as oncoming traffic, stop and go, and pedestrians. The
Traffic Editor is the user interface for very flexible and easy
traffic scenario definition.
2015
Introduction
Road Networks
Software
Application Fields
Features
n
Road networks with roads and intersections for vehicle
dynamics and ADAS use cases
n
Segment- and coordinate-based road definition
n
Lanes with smooth transitions and specific line
definitions
n
Up to 5 lanes per lane segment
n
Support for lane detection sensors
n
GPS coordinate exchange with turn-by-turn navigation
development tools
n
Simulation of tire characteristics and road surface
conditions like split- surfaces, bumps, potholes
Define roads and junctions graphically.
Hardware
Maneuvers
Define where and how the egovehicle drives on the road network.
2015
259
Engineering
Features
n
Movement control of vehicle under test (ego-vehicle)
n
Maneuver segments defined by distance or time
n
Event-based segment changes
n
Lane driving and lane transition/change definitions
n
Trigger events for specific maneuver activities
n
Open- and closed-loop maneuvers
n
Velocity, steering, and pedal actuation can be set by
using measurement data.
n
User output signals programmable via time and
distance
n
External velocity and pedal access for man-in-the-loop
use cases
Traffic
Features
n
Simulation of objects around ego-vehicle
n
Definition of various traffic situations and complex
scenarios
n
Lane driving and lane change definition
n
Support for intersections with oncoming and crossing
traffic
n
Maneuvers based on distance, velocity and acceleration
n
Independent and interdependent movements
n
Time- and road-based trigger events
n
Direct link between model and animation update
Define where and how the surrounding fellow vehicles drive on the
road network.
Objects and Sensors

Features
n
Definition of any number of traffic objects
n
Road- and intersection-based positioning
n
Graphical representation in MotionDesk (p. 140)
n
Moving objects like pedestrians
n
Static objects like traffic signs, traffic lights,
parked vehicles, houses
n
2-D object sensor
n
3-D object sensor
n
Custom sensor
n
Traffic sign sensor
Define sensors on the vehicle and traffic signs, obstacles and
scenery along the road.
Overview of Objects
and Sensors
Sensor Type
Traffic Signs
Object
Sensor Output
80
Speed limit, 80
2-D
More detailed
information available:
n
Product Brochure:
ASM Traffic
n
www.dspace.com/asm
260
Custom
Adult / Child
3-D
2015
Introduction
ModelDesk
The graphical user interface
Main Features
n
Offline and online simulations
n
Graphical user interface
n
Parameter set management
n
Road Generator
n
Maneuver Editor
n
Traffic Editor
n
Tool automation
n
NEW: Preprocessing for engine models
n
Custom model parameterization
Application Fields
ModelDesk Concept
ModelDesk is a graphical user interface for simulation,
intuitive model parameterization and parameter set management. It also provides project handling and allows
parameter sets to be downloaded to offline and online
simulations. It supports tool automation via Python scripts.
ModelDesk can be used seamlessly from parameterization
to offline and online simulation, and finally to parameter
and result management.
Benefits
n
Seamless simulation process from MIL to HIL
Software
n
Intuitive, graphically supported parameterization
n
Parameters changed online and offline
ModelDesks user interface for selecting model subsystems for configuration, parameterization, and simulation on platforms like a PC,
dSPACE VEOS, and dSPACE Simulator.
Graphical Parameterization
The model components and their subsystems are represented by a hierarchical graphical structure. The model
components to be parameterized can be selected from the
top level. Users have the vehicle model before them and
can browse through its systems, guided by graphical representations of the modeled components.
Parameter Management
ModelDesks Project Navigator provides a means of organizing and managing large-scale model parameterization
projects. Parameter files can be created and assigned to
each model component (differential, tires, road, etc.), and
complete vehicle parameter sets can be created and managed. Existing parameter files can be selected from a
parameter pool and applied by drag & drop.
2015
261
Engineering
Hardware
n
Managing parameter sets and entire projects
Simulation Management
ModelDesk includes powerful functions for directly executing
and displaying simulations, and managing their results:
n
Starting and stopping a simulation
n
Plotters for visualization
n
Saving, comparing and managing simulation and measurement data
n
Saving simulation experiments
(driving maneuvers, roads, traffic, etc.)
Plotter
ModelDesk features an integrated plotter which displays
signals from the ASMSignalBus. The signals have the same
structure as in the Simulink model. The bus can include
user-defined signals. Plotter configurations can be defined
and stored, and the same single configuration can be used
seamlessly online (HIL simulations) and offline (Simulink
Configuration of a simulation experiment consisting of a vehicle

model, road, maneuver and vehicle parameters.
simulations). A configuration includes the following data:

simulation results, measurements, and parameter sets consisting of vehicle parameters, roads, maneuvers, and/or
traffic. A configuration collects together all the sources and
conditions that the plotted results are based on.
Features
n
Plots of ASM signal buses
n
Plots of user-defined signals
n
Plotter configurations can be saved
n
The same configuration to be used online and offline
n
Plot printouts
n
Configuration comprises measurements, simulation
and parameters
ModelDesks plotter displaying various vehicle dynamics signals.
Visualization with MotionDesk

ModelDesk and MotionDesk work seamlessly together. In
ModelDesk, users can define scene types such as country
roads, tree-lined roads, and urban areas. The scenes are
then automatically generated in MotionDesk with appropri-
262
ate objects like buildings, trees, borders, reflector posts, and

street lamps. These can also be modified as required in
MotionDesks integrated Scene Editor.
2015
Introduction
Road Networks
Software
Application Fields
Features
n
Support for vehicle dynamics and advanced driver
assistance traffic scenarios
n
Segment and coordinate-based road definition
n
Intersections and junctions
n
Lane, line and traffic sign definition
n
Height, inclination, and surface condition applied via
segment-independent road coordinates
n
Easy definition of bumps, profiles, split- areas, etc.
n
Dedicated 1-D and 2-D views of road features
n
Road import: map data (like OpenStreetMap, Google
Maps, etc.), ADAS RP (Nokia HERE), and OpenDRIVE
format
n
Road networks and predefined sceneries are automatically imported into MotionDesk (city center, country
road, highways)
n
Definition of driving routes
Engineering
Hardware
Road Generator
The Road Generator is the graphical user interface for defining road networks and sophisticated road features. Roads
can be assembled from geometric segments or imported.
Features such as lanes, intersections, height, inclination,
surface condition, etc., can easily be added to a road by
editing attributes that are displayed in 1-D diagrams. The
whole road network is visualized in a 2-D view. The road
design also interacts closely with the 3-D animation software
MotionDesk to define the environment. The Road Generator
gives ideal support to complex traffic scenario creation in
the development and testing of advanced driver assistance
systems (ADAS).
2015
263
The Road Generator supports the definition of intersections and complex road networks. The user interface provides a list of road segments
(upper left), an overview of the whole road network (middle), and a view of lane details (right).
Maneuver
Maneuver Editor
The Maneuver Editor is used to define how and where a
vehicle moves on the road network. Maneuvers consist of
several segments with their own individual properties. There
can be simple maneuvers that just follow the road or very
sophisticated ones based on several stimuli, or user inputs.
A maneuver also defines the driving lane and the lane
changes of the test vehicle. The road or road network the
maneuver relates to is visualized for intuitive maneuver
creation.
Features
n
Definition of driving maneuvers based on road network
routes
n
Maneuver segment definition by distance or time
n
Lane driving and lane change definitions
n
Definition of steering and pedal stimuli or driver-based
maneuvers
n
Standard maneuvers included (lane change, -split,
steady-state cornering, fish hook, etc.)
n
Lateral and longitudinal stimuli can be imported
from measured data (MAT files).
n
User output signals programmable by using time or
distance
The ASM Maneuver Editor: the list of maneuver segments and tabs with maneuver settings in the middle, the imported road with segment
information and a visual preview on the right.
264
2015
Introduction
Traffic
Application Fields
Features
n
Definition of traffic fellow movement based on road
network routes
n
Segment-based definition of fellow vehicle movement
n
All vehicles on one page
n
Overview and detailed view
n
Convenient graphical editing
n
Definition of fellow and traffic object parameters in
Traffic Object Manager
n
Easy-to-use fellow vehicle activity definitions
Example of the traffic definition page.
2015
265
Engineering
Hardware
Software
Traffic Editor
The Traffic Editor is the graphical user interface for defining
the movements of the fellow vehicles on a road network.
The Traffic Object Manager (TOM) is used to give fellow
vehicles additional characteristics. Traffic objects like signs
or construction barriers can also be defined and placed in
road networks.
Traffic scenarios are defined on a single page that can be
completely customized from complete overview to maximum detail.
NEW: Processing
Parameter Processing
ModelDesk provides a fully integrated parameterization
workflow. Users can include initial data, such as measurements, functions, and settings, flexibly and process it into
parameters optimized for simulation models. Users can write
the processing routines for parameters in the well-known
MATLAB programming environment. In addition to this

customizable parameter calculation, sophisticated error
handling procedures have been integrated to support the
users during parameterization.
Import
Measurement data
Process
ModelDesk
Parameter
dSPACE VEOS
(offline simulation)
Download
dSPACE SCALEXIO
(real-time simulation)
MATLAB/Simulink
The processing feature transfers measurements, settings, and functions into parameters optimized for simulation.
Features
n
Read and process measurement data
n
Function administration
n
Settings administration
n
Execute functions with appropriate error handling
n
Adapt parameter as a result of a processing function
Custom Models and Demo Projects

This feature can also be used in combination with custom
components to parameterize own libraries with ModelDesk.
A demo projects for the ASM engine models provide predefined parameterization routines, to deliver a semi-automated calculation of all model parameters.
Use Cases
n
Engine parameterization based on testbench
measurement
n
Battery parameterization based on impedance
spectroscopy
n
Suspension kinematic parameterization based on
kinematic and compliance testbench data
266
2015
Introduction
Tool Automation
Functionality
All ModelDesks functions for experiment management and
model parameterization that are available via its GUI can
now also be accessed via its COM (Component Object
Model of Microsoft Windows) interface (except road and
maneuver creation). You can load existing model parameter-
Application Fields
Features
n
Script-based tool automation
n
Integrated Python interpreter
n
Direct access to project and experiment management
n
Direct alteration of all vehicle model parameters
n
Direct alteration of maneuver segments
n
Direct alteration of road features
Software
Benefits
n
Direct alteration of traffic maneuvers
n
Simulation-based parameter studies
n
Automated marginal condition analyses/detection
n
Long-term behavior studies
n
Sequential maneuver executions
ization projects and activate predefined experiments. All the

vehicle parameters such as vehicle mass, suspension kinematics, engine torque, additional loads, and similarly also
environment or maneuver settings like road friction or
vehicle velocity, can be controlled from within scripts.
Hardware
Remote Control and Batch Processing for ModelDesk

To perform long-term tests or parameter studies, ModelDesk
provides script-based tool automation. This gives you maximum flexibility to define custom simulation scenarios. Tool
automation can be performed by means of scripting languages like Python and MATLAB M scripts.
The scripts can be executed either externally to remotecontrol ModelDesk or internally when ModelDesks batch
mode is used. The batch mode functionality is realized by
a Python interpreter that supports Python 2.5.1.
ModelDesk
Script
Project handling
Engineering
Parameterization
dSPACE VEOS
dSPACE SCALEXIO
(online simulation)
MATLAB/Simulink
The scriptbased tool automation for

ModelDesk provides functionality for
parameter set management and for direct
model parameterization. The parameters
of online and offline simulations can be
changed during a simulation run.
2015
267
Parameter download
Custom Model Parameterization

Graphical Parameterization of
Custom Models
ModelDesk supports the graphical parameterization of
model parts that were replaced by custom models or custom
extensions to ASMs. This allows you to manage all the
parameters of a project from a single source.
Features
n
Automatic generation of new parameter pages based
on custom models
n
Controls provided according to parameter dimension
(scalar, vector, table)
n
Original ASM and customized model parts displayed as
one system
Benefits
n
Centralized parameter management
n
Graphical parameterization without detailed modeling
knowledge
Model Preparation
For use in ASM, custom model libraries have to be prepared
according to ASM guidelines in order to parameterize them
in ModelDesk. The guidelines mainly define how parameters
are declared with masked variables and a fixed declaration
structure. Libraries can have multiple masked subsystems,
and each subsystem has its own parameter page for separate parameterization.
Custom Library Registration

ModelDesks registration function lets you select new libraries to parse them and make their parameters available
graphically. During registration one or more parameter
pages are created automatically, depending on the number
of masked subsystems. Each page lists the controls of declared parameters. Controls can be single entry fields for
scalar types, multiple entry fields for vectors, or complex
tables for table-based parameters.
Navigating Custom Parameters

Whenever a model containing blocks from a registered
custom library is loaded into a ModelDesk experiment the
related parameter pages of these blocks are provided. They
can be selected in the Navigator. Each library is represented
as a branch in the hierarchy with links to the subsystem
pages. The new pages can be used in exactly the same
manner as the standard pages.
Custom parameter page created by ModelDesk. Controls for scalar,

vector or table parameters are automatically labeled with the unit
and caption as defined in the custom library.
268
2015
Application Fields
models can be parameterized with ModelDesks

parameterization options for simulation on a PC
(offline) or on dSPACE real-time hardware (online).
n Seamless 3-D Animation The vehicle dynamics
models provide access to MotionDesk with all license
types. The model must include the MotionDesk
blockset.
n Cost-efficient license types for offline and online (real-
time) simulation
n Simulation models parameterized and reconfigured
in ModelDesk with the Runtime License. This enables
real-time simulation on a dSPACE HIL system without
an additional MATLAB license.
Properties
n Open, modular models, viewable right down to
the Simulink block level
n Customer-specific model parts can easily replace or
extend ASM modules.
n Real-time code generation support
n Simulation on a PC (offline) or on dSPACE real-time
hardware (online)
ASM Runtime License

The Runtime License is designed specifically for simulation
on real-time hardware (online).
Properties
n Real-time code for simulation on dSPACE real-
time hardware
n Code for simulation on dSPACE VEOS
n Code already generated from the models via
the Developer License
n Customer-specific modifications are not supported
2015
269
Engineering
ASM Developer License

The Developer License offers all of the available model
options and supports all development steps and types of
applications.
Software
The Benefits
n A simulation environment that seamlessly covers
the offline and online (real-time) worlds.
n ModelDesk is the parameterization tool throughout
the entire process, which means that the parame
terizations can be reused.
n Mutual Parameterization With all license types, all
Hardware
The ASM License Concept

The ASM models come with different license types: Developer License, Runtime License. This lets users apply the
models in various kinds of applications, without losing any
of the characteristic ASM flexibility.
n Exchangeability You can switch the license types
for your models from Operator License to Developer
License and vice versa if you have both these types.
Introduction
ASM Versions and License Concept
Data Management Software / SYNECT
SYNECT
Data management software for modelbased development and ECU testing
Highlights
n For model-based development and ECU testing
n Integrated variant management
n Direct connection to engineering tools
n Traceability between requirements, models,
parameters, and test cases
n Open API for integration into existing IT infrastructure
and workflows
n Scalable from small local to globally distributed teams
Application Areas
SYNECT is a data management and collaboration software
tool with a special focus on model-based development and
ECU testing. The software is designed to help you manage
data throughout the entire development process. This data
can include models, signals, parameters, tests, test results,
and more. SYNECT also handles data dependencies, versions
and variants, as well as links to the underlying requirements. One key aspect of SYNECT is direct connection to
engineering tools, e.g., MATLAB, Simulink, TargetLink, or
AutomationDesk, and application/product lifecycle management systems (ALM/PLM) so that you can work with your
preferred tools and seamlessly exchange data. SYNECT is
ideal for automotives, aerospace, industrial automation and
medical engineering and wherever embedded systems are
developed through model-based design.
Modular and Scalable

SYNECT focuses on the efficient, integrated management
of all your design and development data throughout the
model-based development process, yet it can also be scaled
to fit specific use cases. SYNECT has modules for individual
areas such as test management, model management, signal
and parameter management, and variant management.
This means that you can introduce SYNECT step-by-step
270
Key Benefits
SYNECT integrates all your development data into one
single environment.
n Directly store and reuse the data objects found in your
model-based development and ECU testing processes.
n Work with your preferred tools in every development
phase and benefit from easy data flow, because
SYNECT integrates with engineering tools and supports
standards commonly used in model-based development.
n Stay on top of the escalating number of variants with
SYNECTs built-in variant management.
n Benefit from fast deployment due to the modular
and scalable product architecture.
n Customize SYNECT to your needs and integrate it
into your IT architecture thanks to SYNECTs open
structure.
n Benefit from SYNECTs open architecture to implement
company-wide processes via connections to ALM/PLM
tools
and in specific teams such as testing groups or function

development teams. You can scale your system to the size
of the team. From local to global, SYNECT grows with
your needs.
The platform supports access control, secure communication, version control, and automation.
2015
Introduction
Module Overview
Module
Description
SYNECT Test Management (p. 272)
n SYNECT module for the intuitive management, planning, monitoring and evaluation of
SYNECT Signal & Parameter Management (p. 277)
n SYNECT module for managing signals, parameters and parameter sets for controller
SYNECT Model Management (p. 280)
n SYNECT module for managing models together with their interfaces, parameters and related files
SYNECT Variant Management (p. 284)
n SYNECT
SYNECT Base
n SYNECT module for working with multiple clients on a common server, for user and rights
Application Fields
all test activities

functions, ECU software and also plant models throughout the entire development process
module for defining and managing variants and their impact on design and
development data
management, and for fine-grained version and configuration management
n SYNECT_TEST_MGMT
SYNECT Signal & Parameter Management
n SYNECT_PAR_MGMT
n SYNECT_MODEL_MGMT
n SYNECT_VARIANT_MGMT
SYNECT Base
n SYNECT_BASE
Hardware
Order Number
arameter M
al & P
ana
ign
S
ge
CT
m
E
e
t
n
M
YN
a
i
a
r
n
a
a
V
ge
T
C
m
e
NE
NECT Base
SY
de
SYNE CT M o
Te
s
em
en
SY
NE
SYNECT has a modular and scalable structure, providing several modules.
2015
271
an
ag
lM
tM
anag
ement
Data
Base
Engineering
nt
SY
nt
Product
Software
Order Information

Highlights
n Manage MIL/SIL/PIL/HIL tests and test data
n Off-the-shelf integration with AutomationDesk
and BTC EmbeddedTester
n Connection to MATLAB and Python
n Monitore, analyze and visualize test results
n Interface to requirements management
n Test case parameterization
n Integrated variant support
Application Areas
SYNECT Test Management supports the intuitive management, planning, monitoring and evaluation of all test activities in ECU development projects. The software provides
special support for model-in-the-loop (MIL), software-inthe-loop (SIL), processor-in-the-loop (PIL) and hardware-
in-the-loop (HIL) testing by directly connecting to test automation tools. Your whole teams tests, test data and test
results are stored centrally and made available for analysis
and status monitoring independently of the test system
and tool that you use.
Key Benefits
SYNECT Test Management handles all the information on
your tests and supports the entire test process.
Master the complexity:
n Centrally manage all test activities across different test
levels and tools in your development project.
n Trace your requirements up to test results by
interfacing to requirements management tools.
n Generate and archive documentation on your test
results.
n Let all users work on the same, consistent set of tests,
test data, and test results with multi-user support.
272
Test efficiently:
n Systematically plan and control test execution.
n Check the requirement coverage and assess the
maturity of your system under test at any time.
n Use existing test authoring and execution tools such
as AutomationDesk, BTC EmbeddedTester, Python
scripting or MATLAB scripting as a basis for test
cases in SYNECT Test Management.
n Manage test execution on different platforms: dSPACE
HIL systems, Simulink, TargetLink, VEOS, etc.
n Fit the system to your team size with scalable clientserver architecture from small groups to large testing
teams.
2015
Introduction
Working with SYNECT Test Management
Test Planning
and Execution
Evaluation
and Reporting
Application Fields
Test
Specification
Import
Test cases
Requirements
Software
Test automation adapters

Test platforms
Manage all test activities with SYNECT Test Management.
Hardware
Supported Tools and Interfaces for SYNECT Test Management
Test Authoring and

Execution Tools
Tool / Interface:
IBM Rational DOORS
PTC Integrity
Microsoft Excel
...
Tool / Interface:
AutomationDesk
BTC EmbeddedTester
Python scripting
MATLAB scripting
Microsoft Excel
Vector CANoe
Vector vTESTstudio
...
2015
273
Requirements Management
Engineering
Importing Test Cases

When you define your tests, you can reuse existing tests
by importing them to SYNECT Test Management. You can
source data from several tools: test lists from Microsoft
Excel, and test implementations from AutomationDesk,
BTC EmbeddedTester, MATLAB, or Python. Tests in
SYNECT come with a standard set of attributes (e.g., test

priority, test platform, test manager, date last executed),
but you can also define your own attributes, of course.
And you can define your own test adapters, so you can use
virtually any of your testing tools or simulation platforms.
Traceability to Requirements and Test Specifications

Thanks to the requirements handling support (p. 289), test
cases can be linked to requirements. You can use this to
conduct traceability analyses, check the completeness of a
test plan, etc.
SYNECT Test Management takes advantage of SYNECTs
automation features by automatically resynchronizing requirements or automatically creating test cases from formally
written test specifications.
After updating requirements, with the help of SYNECT you
can analyze if test cases linked to requirements also need
to be changed.
Resynchronizing requirements.
Versioning and Variant Support

Each test case can be placed under version management.
For example, test cases can be released so that they can no
longer be modified. This lets you reuse existing test cases
in new test plans (see Versioning on p. 288). To manage
the test data for different variants, you can specify variant
dependencies and select which variant configurations will be
supported. You can work with variants by using this module
in combination with SYNECT Variant Management (p. 284).
You can use filters and conveniently group or sort

your tests for an optimal overview.
274
2015
Introduction
Application Fields
various criteria: for example, it can include all your tests for
one variant or for one ECU function. Execution plans can
also be defined using queries that will select test cases which
fulfill a defined criterion. Your test tools use the execution
plan to run the tests and return the results to SYNECT Test
Management, where you can view the overall tests results
and assess the progress of the test.
Software
Test Planning and Execution

SYNECT Test Management easily integrates with test auto
mation tools such as dSPACE AutomationDesk and BTC
EmbeddedTester. It does this via adapters that control the
test automation tool.
To carry out tests, you set up execution plans and add previously defined tests to them. An execution plan is a collection
of tests that have to be executed, and it can be based on
2015
275
Engineering
Hardware
Dialog for defining test execution plans.
Test Result, Test Report and Requirements

Coverage Views
Monitoring testing activities and test progress can be a challenge, especially when many people are involved. SYNECT
Test Management helps you keep track of all tests, whether
planned or already executed. An interactive report functionality and the ability to generate and export reports lets
you evaluate results systematically. For example, you can
display selected test attributes and use them for actions

such as creating an error burndown chart for your project.
A requirements coverage view is available at a mouse click,
so you can see which requirements were already tested and
what the associated verdicts were. Requirements coverage
results can also be exported in a customized report.
Example of a result evaluation, showing test

progress over several calendar weeks.
Requirements coverage view.
276
2015
Introduction
SYNECT Signal & Parameter Management
direct connections to engineering tools, so you can easily

store and retrieve your signals and parameters.
Data stored in SYNECT can be shared by team members and
also reused in subsequent development steps and across
projects.
2015
277
Engineering
Hardware
Application Areas
SYNECT Signal & Parameter Management is used for the
central management of signals, parameters and parameter
sets throughout the entire model-based development process. It can handle the signals and parameters of controller
functions, ECU software and also plant models. It supports
commonly used file formats and standards and provides
Software
Application Fields
Highlights
n Manage signals, parameters, and parameter sets
n For controller software development and plant models
n Interface to Simulink and TargetLink
n Integrated variant support
Working with SYNECT Signal & Parameter

Management
So that you can work with your signals, parameters and
parameter sets efficiently and communicate with the outside world, there are several import/export filters that let
you exchange and use data during the development process. Simulink users benefit from the import and export
of MATLAB M files to flexibly exchange parameter values
and signal and parameter definitions between the modeling environment and SYNECT. TargetLink users benefit
from the option to exchange variables, type definitions and

scalings between the file-based TargetLink Data Dictionary
and SYNECT, the central database with multi-user support.
To manage parameter sets for different variants, you can
specify variant dependencies and select which variant configurations will be supported. You can work with variants
by using this module in combination with SYNECT Variant
Management (p. 284).
Exchange variables, type definitions and scalings easily between

TargetLink Data Dictionary and SYNECT.
278
2015
Introduction
Signal and parameter definitions
.m files
.dd files
Variant 1
Variant 2
Variant 3
1.5
7.9
7.7
8.0
Ki
3.0
K1
1.1
1.1
K2
14.1
K3
5.1
.xls, .xlsx,
.xml, .csv
Parameter
values
A=1;
B=2;
C=7,9;
Ki=3,0;
.cdfx, .dcm, .m,

.par, .xml
ECU image files
AUTOSAR
Signal & Parameter Management
.arxml
.hex, .mot,
.s19
Customer-specific
import/export filters
Software
TargetLink
Data
Dictionary
Variables, scalings,
typedefs
Parameter
Application Fields
Plain variables,
Simulink data objects
Open plug-in concept (e.g., Python adapter scripts)
Variant 1
Variant 2
Software Developer
Function Developer
Version
...
1
2
A=1,5;
A=1,5;
3
B=1; A=1,5;
B=1;
C=8,0;B=1;
C=8,0;
Ki=3,0;
C=8,0;
K1 Ki=3,0;
=1,1;
Ki=3,0;
K1
=1,1;
K3 = 5,1;
K1 =1,1;
K3 = 5,1;
K3 = 5,1;
Variant n
Parameter
Variant 1
Variant 2
Variant 3
1.5
7.9
7.7
8.0
Ki
3.0
K1
1.1
1.1
K2
14.1
K3
5.1
Engineering
Ki=3,0;
Version
1
A=1;
4
B=2;A=1;
C=7,7;
B=2;
Ki=3,0;
C=7,7;
K1 =1,1;
Ki=3,0;
K2 =K1
14,1;
=1,1;
K2 = 14,1;
Calibration Engineer
File-based parameter management generates a large number of files. SYNECT centrally manages parameter sets for different variants.
2015
279
Version
1
A=1;
2
B=2;
A=1;
C=7,9;
3
B=2;
A=1;
Ki=3,0;
C=7,9;
1 A=1;
B=2;
4
Ki=3,0;
C=7,9;
B=2;
Ki=3,0;
C=7,9;
Hardware
SYNECT supports the import and export of several commonly used file formats, and is open to realize customer-specific import/export filters
via an open plug-in concept.

Highlights
n Manage models together with their interfaces,
parameters and related files
n For distributed development and for sharing and
reusing models
n For controller models and simulation models from
various modeling environments
Application Areas
SYNECT Model Management lets you manage your prime
asset in a model-based development process your models.
It combines model file management, model metadata management and model interface management1) all in one tool,
all accessable from one GUI. You can organize your models
in libraries with dedicated user and rights permissions and
according to their variant dependencies. The modeling of
hierarchical dependencies between models and submodels
allows building and configuring model compositions from
different libraries or work projects. Defining and inspecting
the model architecture directly in SYNECT not only increases
the transparency of the models directly in the data management solution, it also supports implementing top-down
development processes for new models.
280
2015
1)
n Supports Simulink models, TargetLink models and FMUs

n Provides open interfaces to support further modeling
environments
n Comprehensive model categorization through
customizable metadata
Key Benefits
n Share and reuse models within an organization
by managing them in one central location
n Make it easy to find the right models by organizing
them in libraries, projects, together with alternative
implementation variants, and in relation to other
models
n Increase model transparency with comprehensive,
customizable metadata
n Keep track of model evolution with fine-grained
versioning of models, interfaces, parameters and
model files
n Implement top-down model development processes
by defining the model architecture and interfaces
before implementation
Requires SYNECT Signal & Parameter Management.
Introduction
Models
SYNECT Model Management manages both the model structure and the actual model implementations by using model
files of the supported modeling environments.
Model structure information can be used as a purely
descriptive feature, increasing transparency and model
understanding directly in the data management solution,
without accessing the actual modeling environment.
You will get the most out of SYNECT Model Management
Par
Out
In
Out
Model
Sub
Model
Out
Out
Model
Sub
Model
Par
Signal & Parameter

Management
Out
In
Par
Par
Sub
Model
Out
In
Par
In
Par
Sub
Model
Model
Sub
Model
Out
Out
In
In
In
Par
Out
Hardware
In
In
In
Software
Sub
Model
Par
Out
Out
Model
Sub
Model
Out
Engineering
Model Implementations
Model implementations contain the actual model files
and all files that come with a model, such as initialization
scripts, parameter files, documentation files, etc. For easy
access to the files, these can be managed directly from the
SYNECT GUI, in the context of the model and its structural
information. SYNECT keeps the model files in an established
file-based configuration management system, such as PTC
Integrity or Apache Subversion. If you already manage
your models in such a system, migration to SYNECT is easy:
Keep the model files in your file-based configuration management systems, link them with your models in SYNECT,
and manage them directly from SYNECT.
2015
281
In
Par
Par
Sub
Model
In
Par
Par
Application Fields
when you start to actively manage model structure and

interfaces directly in SYNECT. By linking signals and parameters from SYNECT Signal & Parameter Management data
pools to your models, you can easily implement central
signal and parameter management for your models. This
enables top-down model development and makes it easier
to keep model interface consistency for smoother model
integration.
Model Variants:
One Model, Multiple Implementations
SYNECT lets you manage multiple implementations
with the same model and its structural properties. As
an organizational feature it helps you group alternative
implementations, called implementation variants. You can
declare the variant dependencies of the individual implementations according to the variant models defined in SYNECT
(see SYNECT Variant Management module, p. 284).
Model
Implementation
Variant A
IImplementation
Variant B
Implementation
Variant C
Version (17)
Version (12)
Version (19)
Version ...
Version ...
Version (16)
Version ...
Version (1)
Version (1)
Version (1)
Model Metadata
The SYNECT metadata model contains standard metadata
and can also be extended with user-specific metadata attributes. Metadata is handled both on the model level as
well as on the model implementation level. Properties that
are valid for all implementations of a model can be managed
at model level, such as the categorization of models as controller models, plant models, etc.. Implementation-specific
information such as the modeling environment, fidelity level

for simulation models, or implementation detail level for
controller models can be handled at the implementation
level. A well thought-out set of metadata will make it easy
to find, sort and categorize the models you are managing
in SYNECT.
Requirements
Requirements that are imported to SYNECT and maintained
in a SYNECT requirements project can be linked to models
bidirectionally. This information can be further processed
and aggregated in order to implement traceability or coverage reports.
282
2015
Introduction
Workflows
Top-Down
In this workflow, new models can be defined by structure
in SYNECT and then exported as structural frame models to
supported modeling environments for the subsequent implementation of behavior. The same procedure can be applied if
structural changes (such as interface changes) will be made
in existing models. Export adapters are currently available
Define new
models
for Simulink models and for TargetLink models. The existing

adapters are open implementations that can be adapted to
customer-specific conditions. The XML export adapter can
be used to implement completely new tool adapters for
additional modeling environments.
Configure
models
Simulink
Simulink
TargetLink
TargetLink
FMI
Hardware
Import
models
Application Fields
& Parameter Management functionality. Import adapters are

currently available for Simulink models, TargetLink models,
and for FMUs (Functional Mock-up Units). The XML import
adapter offers a generic way to import model structure
information into SYNECT. The XML file can be provided
directly by a modeling tool or a custom tool adapter.
Software
Bottom-Up
With this workflow, existing models are imported into
SYNECT Model Management via tool adapters that are specific to the modeling environment. During import, the essential structural information of the model is collected, such as
its inputs, outputs and parameters. After the import these
items can be managed individually with the SYNECT Signal
Export
models
Custom (XML)
Custom (XML)
Modeling/simulation in external modeling tool
Model Configuration
You can define new composite models by combining existing models as submodels of the new composite model.
To configure the composite model, just select the specific
implementation variants and versions to be used for each of
its submodels. By default, SYNECT provides the file system
with the respective model files of the specified submodels

in the correct version and variant for further use. Custom
export adapters can be used to create or configure integration frame models according to your own integration
mechanisms.
2015
283
Engineering
Manage models

Highlights
n Define variant models
n Manage variant configurations
n Define relationships between variants and
development data
Application Areas
SYNECT Variant Management lets you create variant models,
specify constraints between variants, and define variant
configurations that need to be supported in subsequent
development phases. When working with other SYNECT
Working with SYNECT Variant Management

To manage your variants systematically, you explicitly define
a variant model which you can use throughout the entire
development process. This variant model consists of variation
points, variants, and constraints between variants.
modules, e.g., SYNECT Test Management, SYNECT Signal

& Parameter Management or SYNECT Model Management,
you can specify relationships between your data and variants,
and manage different variants of your data.
The variant model is the basis for defining variant configurations, in other words concrete combinations of variants that
need to be supported in your development project.
Example of a SYNECT variant model consisting of

variation points, variants, and constraints between
variants.
284
2015
Application Fields
Introduction
User-defined list of variant configurations to be supported in the current project.
Software
to use an existing execution plan to test a specific variant

configuration, it is easy to identify and exclude tests that
are invalid or that do not apply.
You can specify variant dependencies for your test

cases. For example, to define that a specific test
case applies only to a specific variant.
2015
285
Engineering
Managing Variants in SYNECT Test Management

Variant dependencies in SYNECT Test Management can be
used when defining test execution plans for a specific variant configuration. By default, only test cases that apply to
the selected variant configuration are displayed. If you want
is valid for a certain variant only, that a parameter exists

for a certain variant only, that a parameter has different
values for selected variants, or that a model has different
implementations for different variants.
Hardware
Dependencies Between Data and Variants

When working with other SYNECT modules, such as SYNECT
Test Management or SYNECT Signal & Parameter Management, you can specify dependencies between your data
and variants. For example, you can specify that a test case
Managing Variants in SYNECT Signal &

Parameter Management
To manage parameters and parameter sets for different
variants, in SYNECT you can define variant dependencies for
parameters. You can specify that a parameter exists only for
a certain variant or that a parameter has different values for
different variants. You can then specify and manage different

parameter values for your variant configurations, and also
import and export values for selected variant configurations.
Parameter values for different variant

configurations can be managed centrally.
You can immediately see if a parameter
depends on a variant and has different
values.
Parameter values can be imported or exported for different variant

configurations. You can select which variant to import or export
values for.
Managing Variants in SYNECT Model Management

To manage model implementations for different variants,
you can define variant dependencies for the different implementations of a model in SYNECT. Besides documenting the
variant dependencies of implementations, these dependencies can be accessed via the tool automation API to facilitate
variant-dependent configuration of composite models.
286
2015
Introduction
General SYNECT Functionalities
Software
can restrict access to test project plans according to your

supplier or customer, or provide read-only and export-only
access to specific parameter sets.
Comprehensive user and rights

management.
2015
287
Engineering
User and Rights Management

SYNECT provides user and rights management functionality.
As an administrator, you can define who has what kind of
access to a specific project or specific item types. Data access
can be organized efficiently and securely. For example, you
Data Model Customization

SYNECT makes it easy to extend the data model by adding
custom attributes. For example, you can define additional
attributes for your test cases: supplier or customer lists, test
system IDs, etc. SYNECT also has convenient functions for
importing and exporting data with this customized data
model.
Hardware
Database Support
SYNECT supports SQLite, SQL Server and Oracle. For
a quick start, SYNECT comes with a ready-to-use SQLite
database installer.
Application Fields
Highlights
n Database support
n Data model customization
n User and rights managements
n Version management
n Automation and openness
n Requirements handling
n Working with configuration management systems
Fine-Grained Version Management

SYNECT gives you the ability to manage different versions
of items such as test cases, parameters, or models. There
is also a branching mechanism for creating a new development branch from an already released version of an item.
The trunk, branches and versions are displayed graphically.
A compare functionality enables you to compare different

versions of the same item, or even a complete project or
workspace.
Comments to element versions can be annotated.
Example of a version history.
Version compare window.
288
2015
Introduction
Internal interpreter
*.py
Access
Traceability to Requirements and Specifications

With SYNECT you can link your data (e.g., test cases, parameters, or models) to requirements. SYNECT is flexible
and provides various options for importing requirements.
Excel and the Requirements Interchange Format (RIF) enable you to import requirements for IBM Rational DOORS
or PTC Integrity. An open Python API lets you build customized importers for other requirements formats and tools.
Software
Access
External interpreter
SYNECT helps you analyze the impact of changes in requirements by providing an overview of linked objects that might
be affected. To navigate between requirements and linked
data, all you need is a mouse click. A special requirements
coverage view is available to check if a requirement is covered by a test case and if this test case has been executed
successfully.
Hardware
COM API
Run
Engineering
Programs written
in C#, Python,
MATLAB,
M scripts,...
Application Fields
languages currently supported are Python, MATLAB, Visual

Basic for Applications, C++, C#, and Visual Basic.
To enable convenient use of customer-developed features,
it is also possible to extend the SYNECT GUI. You can create
new ribbons and controls, or extend the context menus
of SYNECT items such as test cases, test plans, or models.
Working with Configuration Management Systems

SYNECT supports file-based configuration management
systems like Apache Subversion or PTC Integrity. You
can browse file repositories from within SYNECT and compare two file versions located in the repository. You can also
create links to a specific file version. These versioned links
can then be stored as an attribute of a SYNECT item, such
as a test case or a model. An example of a use case is to
ensure that the same version of a test case implementation
is always used, in regression testing, for example.
CM Repository
Browser
2015
289
Automation and Openness

SYNECT provides an open COM API that enables you to
automate actions that are usually manual, and also to define
specific actions such as data imports and exports, report
generation or consistency checks. You can also extend the
SYNECT user interface to access these actions. Interaction
with external tools is also possible with this API, via connections created for different integration scenarios. The
Data Management Software / VariantBased Workflow Management
VariantBased Workflow Management

Handling complex workflows including variants
Highlights
n SYNECT-based workflow management solution
n Mastering complex systems with multiple variants
(HIL, modeling) by workflow automation and
simple user interactions
n Reproduceable and reliable workflows
n Easy configuration
n Single-user and multi-user scenarios
Application Areas
Variant-Based Workflow Management (VBWM), which is
based on the data management software SYNECT (p. 270),
makes it easy to integrate your complex workflows (like the
common hardware-in-the-loop (HIL) scenarios for modeling
and control, including variants) into the dSPACE tool chain
and automate them.
290
Key Benefits
With Variant-Based Workflow Management, you can achieve
reproduceable and reliable workflows even in highly complex
use cases, and save a great amount of time by workflow
automation that exactly matches your needs.
n Centrally configure all the information necessary to
support your variant-dependent workflows in SYNECT
n Manage large, highly complex HIL systems with a large
number of variants and multiple software interactions
n Quickly and safely adapt your modeling environment
to changes caused by variant configurations
n Speed up the reliable configuration of your HIL
environment for subsequent HIL tests
n Let multiple real-time applications be configured and
built overnight ready-to-use for HIL testing on the next
day. This can be done easily by using a build server
with scheduled tasks.
2015
Introduction
Data Management Software / Variant-Based Workflow Management
Module Overview
Module
Description
Variant-Based Workflow Management Configurator
n SYNECT component for resource management that allows to specify any kind of information
Starter
Application Fields
relating to variants: links to files and folders or strings, time stamps, etc. The resources are
value/name pairs of information and are the input data for the workflows.
n Use of the SYNECT variant model
n Management of different variant configurations in configuration sets
n Management of resources in a customized tree
n Inheritance of resource values in the variants tree to avoid redundancy
n Macro mechanism for easier resource definition
n Working directory mechanism to support multiple workstations, multiple user and handling
relative paths
n Fine-grained rights management
n Special support of configuration management systems
n Definition of custom workflows
n Consistency check to validate database contents
n Select a variant configuration with a very simple graphical user interface and start a custom
Software
workflow (see also p. 292), e.g., to start and set up dSPACE ControlDesk (p. 106) with the
appropriate experiment for the selected variant configuration.
n Select multiple variant configurations and start a custom workflow for each variant configuration
Multi-Starter
in a kind of batch mode, e.g., to automatically build the real-time code for a huge number of
variant configurations overnight.
Modeling Connector
n Special toolbox in MATLAB with high-level API
of variants inside ConfigurationDesk such as switch of imported/exported

working views
n Connection to the VBWM database (SYNECT) to get project, variant and resource information
n Support of any kind of Simulink variant change mechanism such as libraries, configurable
subsystems and replacing placeholder subsystems
n Support of the Real-Time Interface (RTI) and ConfigurationDesk build workflow
Hardware
n Support
Order Information
Product
Order Number
Variant-based Workflow Management Configurator
n VBWM_CONFIG_SOL
Starter, Multi-Starter, and Command Line Interface (CLI)
n APPL_VBWM_WF_SOL
Modeling Connector
n VBWM_MLCON_SOL
Modeling Connector (local)
n VBWM_MLCON_SOL_LOCAL
Engineering
Starter, Multi-Starter, and Command Line Interface (CLI); (local) n APPL_VBWM_WF_SOL_LOCAL
Relevant Software
Required
Optional
1)
Order Number
n SYNECT Base (p. 271)
n SYNECT_BASE
n SYNECT Variant Management1) (p. 284)
n SYNECT_VARIANT_MGMT
n SYNECT Signal & Parameter Management (p. 277)
n SYNECT_PAR_MGMT
n SYNECT Model Management (p. 280)
n SYNECT_MODEL_MGMT
For editing, it is necessary to have a variant model in SYNECT.
2015
291
Software1)
Data Management Software / VariantBased Workflow Management
Workflow Example
HIL Control and Modeling
Variant-Based Workflow Management ideally suits HIL
testing scenarios and modeling activities. After configuring complex, variant- dependent workflows you can run
them with just a few clicks, including automatic overnight
preparation of large real-time testing applications. As an
example: a powertrain HIL environment with six ECUs and
several variants each can easily lead to more than a million
Workflow example 1
combinations. Now you can easily handle such scenarios.

Starting a complete experiment is simple: just select the
appropriate variant configurations in the Variant-Based
Workflow Management user interface and press a button.
The necessary items such as software tools, experiments,
models, and parameters user-specified via API or via
Modeling Connector are then loaded automatically.
Select variant configuration

Start workflow
Modeling
HIL Control
Data
Real-time application
Configuration files
Workflow
Start dSPACE products
Configure products
Load settings
Variant Configurations
Workflow
Start dSPACE products
Configure products
Load settings
Workflow example 2
Data
Simulink model
Parameterization
Configuration files
File System
Configuration Management
Handling complex workflows with the VariantBased Workflow Management.
The workflow to be executed can be chosen

and activated quickly with the Starter module
(p. 291). The MultiStarter lets you select
multiple variant configurations and start the
custom workflow multiple times for each
variant configuration.
292
2015
Data Management Software / Variant-Based Workflow Management
Introduction
Variant Handling
Variant Model
SYNECT Variant Management (p. 270) provides the variant

model, while the resource information, i.e., information connected to the variants, is supplied by Variant-Based Workflow
Management.
Application Fields
Variants in SYNECT and Variant-Based Workflow

Management
In the HIL and modeling workflows, numerous variants
occur, for example, simulator hardware variants, ECU hardware variants, model parameters and model parts, HIL control parameters, ECU software parameters and many more.
All these variants can affect the workflows and need to be
taken into account when executing a workflow.
Ressources

Information linked to variants
Information linked to variant

configurations
Definition of valid combinations
Text
Link to file
Link to folder
Flag
Etc.
Hardware
Variant Configuration
Software
Information Types
Variant-Based Workflow Management
2015
293
Engineering
Relation between SYNECT Variant Management and Variant-Based Workflow Management (VBWM).
Hardware
SCALEXIO Hardware __________________ 296
Single-Board Hardware ________________ 332
Modular Hardware ___________________ 348
Accessories _________________________ 480
Simulator Hardware __________________ 496
NEW: MicroLabBox Hardware ___________ 516
MicroAutoBox Hardware _______________ 522
RapidPro Hardware ___________________ 542
ECU Interface Hardware _______________ 566
SCALEXIO / Introduction
SCALEXIO
Versatile system for HIL simulation
Highlights
n High channel and system flexibility
n Completely software-configurable
n Connectable to existing systems
n NEW: Multicore and multiprocessor support
n NEW: Support of Functional Mock-up Interface (FMI)
n NEW: Support of virtual ECUs (V-ECUs)
Application Area
dSPACE SCALEXIO1) is a very versatile hardware-in-the-loop
(HIL) simulator that provides highly flexible channels, can be
extended to any required size and is completely softwareconfigurable. Its application range covers all test domains
and vehicles, including the test of electronic control units
(ECU) of electric drives (p. 30).
Thanks to the SCALEXIO multiprocessing feature, the simulator can be coupled with existing SCALEXIO-based or DS100xprocessor-board-based systems, allowing users to expand
their existing test setups to meet growing project needs.
Hardware Concept
The SCALEXIO system is standardized and can be reused in
all SCALEXIO system variations.
n The core of a SCALEXIO system, the SCALEXIO Processing
Unit, is based on commercially available components so
that the processing technology is always up-to-date.
n IOCNET, the scalable serial I/O network, provides the
internal communication between the real-time processor
and the I/O boards.
1)
296
2015
Key Benefits
n Support of different workflows and user roles by separating I/O configuration, modeling and code generation
n Test of different ECU variants and types on a single system
with minimal configuration effort
n Easily resized to fit specific test tasks because component
test systems and network systems are both built with the
same standardized hardware components and connections
n Graphical configuration of channels
n Use of virtual ECUs (V-ECUs) (p. 46) for HIL tests if the
real ECU prototype is not available yet
n Support of FMI (p. 25)
The SCALEXIO I/O units are specifically designed for typical

ECU signals and offer:
n Local signal preprocessing on I/O boards to relieve the
load on the real-time processor
n Integrated signal conditioning, as well as converters and
parts of the electrical failure simulation
n Similar installation and configuration processes, so very
little time is spent on learning
Devices connected to the dSPACE HIL system, for example, electronic control units, can feed in high currents and high
voltages (voltages over 60 V DC or 30 V ACRMS), which can be dangerous for the user. This can happen, for example, in
systems for piezoelectric or hybrid applications. Such currents and voltages can result in property damage, personal injury, or
death. Under all circumstances, you must observe all the safety precautions described in the documentation. Please contact
dSPACE for additional safety-related equipment, such as electrically safe interface cables.
Introduction
System Configuration
FIU & Power Switch Board
Digital I/O Board
retrofitted if required. Hypertac connectors at the front can

be wired according to individual project needs.
Exchangeable load board

of the MultiCompact I/O unit
Application Fields
Due to the standardized SCALEXIO hardware, the system is

easily resizable to fit its test tasks. Additional boards can be
Signal Measurement Board
I/O subrack with HighFlex

boards (left) and
MultiCompact unit (right)
Software
Signal Generation Board

with IOCNET Link Board
Battery simulation power
supply unit
Bus Board
FPGA Board
Digital-I/O Board
Hardware
Hypertac Connector
Multi-I/O Board
I/O Modul
2015
297
Engineering
The SCALEXIO system can be equipped with only HighFlex I/O

boards for maximal flexibility (left) or can even be used as a
variant consisting only of an external processing unit (below).
SCALEXIO I/O Hardware

The SCALEXIO I/O hardware comprises three hardware types,
each specially designed for typical application needs.
MultiCompact, HighFlex and SCALEXIO I/O hardware can
be combined and extended to produce whatever system
configuration you want.
They have the following in common:

n Local signal preprocessing on I/O boards to relieve the
load on the real-time processor
n Connection to the processing unit via an IOCNET interface
n Completely software-configurable
n Similar installation and configuration processes, so very
little time is spent on learning
MultiCompact
n Large number of I/O channels for specific applications
n Each channel has a fixed channel type, so the costs per channel are low.
n Integrated signal conditioning and converters
n Onboard failure insertion unit (FIU)
n Connection of real and substitute loads is possible.
n DS2680 I/O Unit (p. 306)

Compact design for installation in a unit carrier

Basic functions for a fully adequate simulation system, such as power switch

Various channels with dedicated I/O functions
n DS2690 Digital I/O Board (p. 309)

Standardized connector for slot independence and easy assembly

Digital channels with dedicated I/O functions
HighFlex
n Universal input/output/bus channels with freely assignable channel types
n Very versatile and finely scalable with 10 channels per I/O board, 4 channels per bus board
n Each channel is individually galvanically isolated.
n Integrated signal conditioning, as well as converters
n Onboard failure insertion unit (FIU)
n Connection of real and substitute loads is possible.
n Standardized connector concept for all boards
n Boards are slot-independent and easy to assemble.
n DS2601 Signal Measurement Board (p. 318)
n DS2621 Signal Generation Board (p. 320)
n DS2642 FIU & Power Switch Board (p. 322)
n DS2671 Bus Board (p. 324)
SCALEXIO I/O Boards

n Large number of I/O channels with dedicated channel types
n Focus on I/O functions without current-related functionality
n No onboard failure insertion unit (FIU)
n No connection of real or substitute loads
n Connection to I/O via Sub-D connector
n Boards are slot-independent and easy to assemble
n DS6101 Multi-I/O Board (p. 314)
n DS6201 Digital I/O Board (p. 316)
n DS2655 FPGA Base Board (p. 311)
298
2015
Introduction
IOCNET (I/O Carrier Network)
TCP/IP
Coupling Several Processors

IOCNET also couples processors, and no additional hardware is necessary.
Coupling SCALEXIO with Existing Systems
The SCALEXIO system can interact with all dSPACE HIL systems, such as dSPACE Simulator Mid-Size and dSPACE Simulator Full-Size. These are based on the PHS bus technology,
which is used for communication between the processor
and the I/O units. A SCALEXIO system is connected to a PHS
system by processor-to-processor coupling with an IOCNET
Gigalink connection.
Application Fields
IOCNET is a network technology developed by dSPACE for

internal simulator communication based on the Gigabit
Ethernet physical layer. A SCALEXIO system with IOCNET
comprises more than 100 device nodes, which can be
located up to 100 meters apart. The transmission rate is
about 10 times higher than with peripheral high-speed
(PHS) bus-based technology, and input signals can be read
synchronously.
You can also use decentralized I/O, in other words, I/O units
without their own processing units.
Software
Host
Gigalink
I/O Subrack
I/O Subrack
DS100x
Processor
PHS I/O Board
IOCNET
PHS
I/O Subrack
PHS I/O Board

Router
Router
I/O Board
I/O Board
I/O Board
I/O Board
I/O Board
I/O Board
I/O Board
I/O Board
I/O Board
I/O Board
..
.
..
.
FIU/PowerSwitch
Gigalink
FIU/PowerSwitch
Hardware
IOCNET
I/O Subrack
IOCNET
I/O Subrack
Router
IOCNET
..
.
Engineering
IOCNET
FIU/PowerSwitch
2015
299
Processor
Failure Simulation
Hardware Components
The SCALEXIO Failure Insertion Unit (FIU) consists of several
components:
n An onboard failure routing unit (FRU) on the I/O channels
prepares failure simulation by switching the I/O channels
to failplanes. The FRU is available for each channel on
the MultiCompact and HighFlex boards and uses relays
to provide the features of the central failure simulation
unit to each channel.
n Depending on their properties, the channels are connected to the failure simulation system by the high-current (up
to 80 A) or the low-capacitance (up to 1 A) failplane. The
low-capacitance failplane for an optimized signal quality
connects signal generation channels and bus channels
to the central FIU. The high-current failplane connects
signal measurement channels to the central FIU.
n The central FIU is located on either the DS2642 FIU &

Power Switch Board or the DS2680 I/O Unit. The central FIU uses semiconductor switches for switching the
failures. It switches very fast (pulsed switching), which
makes it possible to simulate loose contacts or insert
faults for a very precise duration.
n The failplane segment switch is used to switch selected
segments into the failplanes for failure simulation. This
way, the conducting capacity can be minimized to avoid
signal corruption, even for large simulation systems that
have a high number of inputs/outputs or that are distributed across several cabinets.
Available Failure Types

Failure Type
Failure on Single Signals
Failure on Several Signals1)
Open Circuit
1 channel
All channels1)
Short circuit to ground or UBAT
1 channel
Up to 10 channels1)2)
Short between channels
2 channels
Up to 10 channels1)2)
Failure with pulsed switching
Requires the option Activation by FRU relay and is only possible on I/O channels without current enhancement.
2)
Depending on the ampacity of the failplane.
1)
License Concept
n All SCALEXIO I/O boards and the DS2680 I/O Unit include
a failure simulation (FS) function. You need an additional
FS license to activate the failure simulation. The FS license
will be checked at the host PC. Each license can be used
for one SCALEXIO system.
n The licenses are scaled for failure simulation with different
numbers of channels. The failure simulation is configured in ConfigurationDesk, so you need the appropriate
SCALEXIO failure simulation license for the number of
I/O functions that are mapped to channels with an FRU
that you use in your real-time application. The FS license
is needed only for running the simulation, not for configuring the I/O channels with ConfigurationDesk.
300
Tracing FIU States

The diagnostic functions of ECUs have to detect each failure
within a specified time. To help test an ECUs diagnostic
functions, SCALEXIO provides FIU state tracing. This enables
you to measure or plot FIU states and therefore to monitor
the time from a change in FIU state to any other event, such
as the detection of the failure.
Multiple Failures
SCALEXIO supports the simultaneous insertion of multiple
failures during simulation to allow failure classes such as
broken wire, short circuit to ground or UBAT, or short between
channels. This function can be enabled in ConfigurationDesk
for channels without current enhancement.
2015
Introduction
SCALEXIO
Lowcapacitance
fail rail
Highcurrent
fail rail
DS2908
Failplane
Segment
Switch
DS2671
Bus Board
DS2621
Signal Generation
Board
DS2601
Signal Measurement
Board
DS2642
FIU & Power Switch
Board
I/O unit
Battery
power
supply
unit
Application Fields
DS2908
Failplane
Segment
Switch
Software
I/O unit
Hardware
DS2908
Failplane
Segment
Switch
Connection to
another HIL system
DS2642
FIU & Power Switch
Board
Failplane
ECU connection
DS2601
Signal Measurement
Board
Failplane
DS2621
Signal Generation
Board
Failplane
DS2671
Bus Board
The SCALEXIO FIU concept with an example selection of I/O boards.
Order Number
SCALEXIO Failure Simulation
SCLX_FS_100 (for 100 functions)
SCLX_FS_UNLTD (for an unlimited number of functions)
2015
301
Product
Engineering
Order Information
Power Supply Control for Battery Simulation

With the SCALEXIO system, the battery simulation can be
addressed from directly within the simulation model. No
additional I/O is needed. The battery simulation consists of
three components:
n Battery simulation controller (e.g., DS2907 Battery Simulation Controller, p. 326) to control the power supply unit
by current and voltage values
n Power supply unit to generate current and voltage
n A switch for the power supply to the ECU (DS2642 FIU
& Power Switch Board, p. 322)
Battery simulation
controller
(e.g., DS2907)
Controls
current and
voltage
supply
Power supply unit
In the DS2680 I/O Unit (p. 306), the control for the power
supply and the power switch are already integrated.
You can read out and check the latest current and voltage
values at any time during simulation. The voltage behavior
is specified in the model.
SCALEXIO System
Switches the
power supply
to the ECU
Switch for power

supply (DS2642)
ECU
Configuration Software
ConfigurationDesk (p. 48) is the configuration and implementation software for SCALEXIO and intensifies the system's flexibility. You can perform all configuration tasks in
a single tool, in an easy-to-read 3-column window:
n Describing the connected devices
n Assigning I/O functions and hardware
n Connecting to the model
ConfigurationDesk supports the open Functional Mock-up

Interface (FMI) standard (p. 25). This enables the users to use
different modeling approaches by using functional mockup units (FMUs). In HIL projects, FMUs can be integrated
together with V-ECUs (p. 46) and Simulink models.
dSPACE Engineering Services

You can make use of dSPACE Engineering Services in any
project phase. Whether you need engineering support for
an entire project or just for system installation or first use,
you can rely on our years of experience and comprehensive
302
know-how. These will help you get the maximum benefit

from the system's flexibility for your projects. For example,
all the I/O units contain FPGAs whose microcode machines
we can program for project-specific I/O functions.
2015
Introduction
Special Applications
For testing ECUs for electric motors, which require short

simulation cycles, fast calculations and quick I/O access,
SCALEXIO offers the DS2655 FPGA Base Board (p. 311)
with a freely programmable FPGA and a high level of I/O.
Used in combination with the XSG Electric Components
Library, the DS2655 provides the fast reaction times required
for simulating electrical machines in closed-loop operation
with a controller. The FPGA computes parts of the simulation model for the electrical machine, e.g., from the XSG
Electric Components Library. For more information, please
refer to www.dspace.com/go/xsg-utils.
Application Fields
Tests for Electric Motors
SCALEXIO emulates electric motors together with the Electronic Load

Module and DS2655 FPGA Base Board.
Software
You can also connect electronic load modules to the

SCALEXIO system for different voltage ranges up to 800 V.
For more information about the electronic load modules,
please refer to page 511.
Engineering
The generation of VECUs is based on AUTOSARcompliant ECU

software development.
2015
303
If an ECU's hardware prototype is not yet available for

HIL testing, a virtual ECU (V-ECU) can be used with the
SCALEXIO system instead. A V-ECU usually has the same
software components as the final ECU and is generated
using the SystemDesk V-ECU Generation Module (p. 46).
A V-ECU can be used either alone with the SCALEXIO or
together with other V-ECUs or real ECUs. The combination of
V-ECUs and ECUs in a network enables high-quality restbus
simulation early in the development process.
For using a V-ECU during HIL simulation, a SCALEXIO RealTime license is needed (p. 305).
To configure V-ECUs, you can integrate them into a realtime application in ConfigurationDesk (p. 48) just like any
other behavior model.
Hardware
HIL Simulation with Virtual ECUs
SCALEXIO / Processing Unit

The newest processor technology
Highlights
n x86 processor technology Intel XEON E3
n High bandwith for I/O communication
via IOCNET
n SCALEXIO connectable to DS100x-based HIL
systems (via Gigalink)
n Multiprocessor support
The SCALEXIO Processing Unit is based on an industrial

PC with an Intel XEON E3 quad-core processor, a real-time
operating system (RTOS), and a PCIe plug-on card developed
by dSPACE for communication with the I/O and with other
real-time processors. Because the processor and motherboard components are standard components, they can be
Host
interface
304
Real-time
processor
Processing
Unit
PCI Express
updated regularly to benefit from performance improvements in processor technology.

To ensure communication between the real-time application running on the processer and the I/O, dSPACE offers
the SCALEXIO Real-Time Library that is based on the QNX
real-time operating system.
IOCNET
Link Board
IOCNET/
Gigalink
The IOCNET Link Board connects the

realtime processor to the SCALEXIO
I/O. The Ethernet host interface is
connected to the service core of the
realtime processor.
Multicore Support for Large Models

Large, complex simulation models can be distributed across
three processor cores instead of one to ensure that they can
be computed in real time. The fourth core is reserved for
internal system services. A configuration software is used
to distribute model parts to the cores and to configure the
communication behavior, the simulation hardware and the
model connections (see ConfigurationDesk, p. 48).
IOCNET
SCALEXIO's communication network IOCNET (I/O Carrier
Network) uses a proprietary dSPACE protocol to guarantee
the simulator's real-time capability. It is the interface to
the I/O boards and SCALEXIO processing units, providing a
flexible network topology and high bandwidth to connect
a large number of I/O boards, even when they are far apart
(p. 299).
Large Test Systems via Multiprocessor Support

With the new multiprocessor support for SCALEXIO, two or
more SCALEXIO systems can be coupled to increase computational power. To provide large bandwidths, SCALEXIO
systems can be coupled to processing units via IOCNET.

To ensure convenient modeling, you still have just one overall
project in ConfigurationDesk.
2015
Introduction
SCALEXIO / Processing Unit
Host PC Interface
Communication with the host PC runs via Gigabit Ethernet,
so that the SCALEXIO system can be used in any company
network. When more than two SCALEXIO Processing Units
are used, they are coupled via the SCALEXIO MP Switch to
ensure communication with the host PC. The IP address for
the connection can be assigned via a DHCP server or stored
on the SCALEXIO system itself.
Application Fields
IOCNET Link Board

The DS2502 IOCNET Link Board is used to connect I/O units
or couple the SCALEXIO with other dSPACE HIL simulator
systems. It is available in two versions: one with 4 and one
with 8 IOCNET connectors.
The DS2502 also has angular processing unit (APU) functionality for highly precise angle-based simulation, for example, to measure injection and ignition signals. Up to six
independent APUs can be used.
Parameter
Specification
Processor
n Intel XEON E3-1275v3 with 3.5 GHz
Memory
n L1 cache: 32 + 32 kB (data + instructions)
Software
Technical Details
n L2 cache: 256 kB
n L3 cache: 8 MB
n 4 GB RAM memory (DDR3)
n 6 APUs on the DS2502 IOCNET Link Board
Angular processing unit (APU)

Angular resolution
n 0.011
Speed range
n 28,610 rpm
Speed resolution
n 0.109 rpm
n 4
or 8 IOCNET connectors on the DS2502 IOCNET Link Board (optionally usable

as Gigalink connectors)
Interfaces for I/O boards
Physical data
Physical size
Hardware
n Gigabit Ethernet
Host interface
n 19-inch subrack
n 3 HU
n 483 x 133 x 400 mm (19.0 x 5.2 x 15.7 in)
Cooling
n Active cooling
n Operating temperature 0 C ... 40 C (32 F ... 104 F)
Voltage supply
n 100 ... 240 V AC, 50/60 Hz
Order Number
SCALEXIO Real-Time Library
n SCLX_RTLib
SCALEXIO Real-Time Library for Multicore Systems
n SCLX_RTLib_MC
SCALEXIO Real-Time Library for Multiprocessor Systems
n SCLX_RTLib_MP
SCALEXIO Real-Time Library for virtual ECUs
n SCLX_RTLib_VECU
Hardware
Order Number
SCALEXIO Real-Time PC (Rack-Mount Version)
n SCLX_RTPC_RACK E31275
n Please inquire if you use a SCALEXIO Real-Time PC with another processor
DS2502 IOCNET Link Board
n DS2502_4P (with 4 IOCNET connectors)

n DS2502_8P (with 8 IOCNET connectors)
SCALEXIO MP Switch
n SCLX_SWITCH SG300_10
Relevant Software
Product
Required

2015
305
Software
Engineering
Order Information
SCALEXIO / DS2680 I/O Unit
DS2680 I/O Unit

MultiCompact unit for powertrain and vehicle dynamics scenarios
Highlights
n 140 channels for extensive I/O functions
n Galvanically isolated as a unit
n Compact half 19" unit
n Attractive price
306
The DS2680 I/O Unit is a MultiCompact unit for the

SCALEXIO system that provides all the I/O channels required
for the hardware-in-the-loop simulation of transmission or
vehicle dynamics ECUs. Most of the I/O channels have a fixed
function, i.e., they are dedicated analog or digital channels.

With its predefined channels, the DS2680 has an attractive
price, and is ideal for specific application scenarios.
I/O Functionality
The DS2680 has numerous I/O channels, each with a mostly
predefined function. You can choose between analog and
digital inputs and outputs, resistance simulation channels,
and special I/O channels. Signal measurement and generation can be time-triggered or angle-triggered.
Testing Electrical Failures

The DS2680 includes a Failure Insertion Unit (FIU) for testing
ECU behavior in the event of a failure. It can be used as a
central FIU for the SCALEXIO system. Each channel has a
failure routing unit (FRU) for switching the connection to
the FIU via the fail rails. For further information, please refer
to Failure Simulation on p.300.
Real Loads
Substitute loads can be plugged onto the DS2680 internally
if required. An exchangeable load board is available for
you to mount different plug-on loads. Real loads or large
substitute loads can be connected externally via the load
connector provided for them.
Component Variants
The DS2680 is available with and without an integrated
bus board. The integrated bus board provides two channels
for each of the bus protocols LIN, CAN and FlexRay. If you
need more or different bus channels, for example, four CAN
channels, you can use a HighFlex bus board in addition or
as an alternative.
2015
Introduction
Technical Details
Parameters
Specification
Signal measurement
n Max. 6 A per channel

n Substitute loads pluggable, up to 2W per measurement channel
n Connector for real loads
n Channel bundling to increase current carrying capacity
(Analog In 1)
Application Fields
n Multifuse for electrical safety

n 20 analog inputs
n Only voltage measurement

n Measurement range 0 ... 60 V
n Resolution 16 bit
n 30 digital inputs
n Voltage measurement
(Digital In 1)
n Trigger value 0 ... 24 V

n Voltage range 0 ... 60 V
n 18 variable inputs
(Flexible In 2)
n Voltage measurement digital

n Voltage range 0 ... 60 V
n Trigger value 0 ... 24 V
n Current measurement analog and digital
n Measurement range 18 A
n 15 analog outputs (DC)
(Analog Out 1)
Software
n Resolution 16 bit (analog)
Signal generation
n Only voltage generation

n Output voltage 0 ... 10 V
n Output current -5 ... +5 mA
n Resolution 14 bit
(Analog Out 4)

n Resolution 14 bit
n Current sink: Current range -30 ... +30 mA
(Analog Out 3)

n Output voltage -20 ... +20 V
Hardware
n Resolution 14 bit
n Effective inner resistance 250
n 12 resistance simulation channels
(Resistance Out 1)
n Resistance range 16 ... 1 M

n Voltage range -3 ... +18 V to GND
n Current range -80 ... +80 mA
n Power max. 250 mW
n 28 digital outputs
(Digital Out 1)
n Configurable as low-side/high-side switch or push/pull

n Low-side = GND
n High-Side VBAT or Dig-Out-Ref
n High-side voltage range: 5 ... 60 V
n 2 analog input and output groups,
e.g., for lambda

(Analog In 2, Analog Out 2, Load 1)
Engineering
Special I/O channels
n 1 ADC
n 1 DAC
n 1 load (component channel)
n Voltage range -10 ... +10 V
n 1 channel to control the power unit
n Control of Lambda Genesys power supply
(Power Control 1)
n 6 power switches without current
measurement (Power Switch 2)
n Up to 60 V
n Continuous current 4 x 6 A per channel (but a maximum total of 50 A for all channels)
2015
307
Voltage supply
Parameters
Specification
Buses
n 2 CAN (CAN 1)
1)
n Configurable as high-speed or low-speed CAN

n Conventional CAN VBAT
n 2 LIN (LIN 1)
n Configurable as K-line
n Conventional LIN VBAT
n 2 FlexRay (FlexRay 1)
n Only 4 bus lines, i.e., 1 fault-tolerant FlexRay bus (channels A + B) or 2 FlexRay buses
(channel A)
n Conventional FlexRay VBAT
Failure Insertion Unit
General
n Voltage 60 V
n Failure switch for up to 48 A
n Continuous current for high-current fail rail 48 A
n Continuous current fail rail with low capacitance 1 A
n Broken wire
Failure types
n Short circuit to GND or UBAT

n Crossed wire between two channels
n All failures with optional bouncing
Internal communication interface
n IOCNET
Physical data
Physical size
n 475 x 132 x 215 mm (18.7 x 5.2 x 8.5 in)
Voltage supply
n 24 V
1)
Only for DS2680 with bus support
Order Information
Product
Order Number
DS2680 I/O Unit (without bus support)
n DS2680_ONLY
DS2680 I/O Unit (with bus support)

Additional Hardware
n DS2680_2672
DS2680-IL Load Board (exchangeable load board)
n DS2680_IL
OBD to Sub-D Adapter Cable
n SCLX_OBD_CAB1
Relevant Software
Product
Required
Optional for DS2680 I/O Unit with bus support
RTI CAN MultiMessage Blockset (p. 70)

RTI LIN MultiMessage Blockset (p. 73)
308
2015
SCALEXIO / DS2690 Digital I/O Board
Introduction
DS2690 Digital I/O Board

MultiCompact board for vehicle body scenarios
Application Fields
Highlights
I/O Functionality
The DS2690 offers digital channels that are either predefined
for signal measurement or signal generation, or can be individually configured for either. Channels for signal measurement and generation are usable as Digital In, PWM In or
Digital Out, PWM Out.
The signal types and channel bundling are configured with
ConfigurationDesk (p. 48).
IOCNET connector
Hardware
Key Benefits
The DS2690 offers a large number of dedicated digital I/O
channels for signal generation and measurement. Their
supported I/O functionalities cover exactly the ones needed
for body electronic ECUs. Real loads can be connected to
each channel individually.
An on-board failure routing unit (FRU) enables failure simulation on all channels. For further information on the failure simulation function, please refer to Failure Simulation
on p. 300.
I/O connector
Fuse
Engineering
Application Area
The DS2690 Digital I/O Board is the tailored SCALEXIO solution for hardware-in-the-loop (HIL) simulation of body electronics ECUs. Vehicle body applications such as electric window lift and windscreen wipers require many high-current
digital I/O channels, as well as the ability to simulate failures.
Software
n Large number of digital I/O channels

n Signal measurement or generation
n Connection of real loads
n Seamless integration into SCALEXIO FIU concept
n Attractive price
Fuse
FRU
Internal load
Controller
I/O
Real Loads for Real Currents

Testing ECUs under realistic circumstances sometimes
requires real currents, so real loads can be connected
externally. Substitute loads are available internally as well.
Status LED
Digital
In
Digital
Out
PWM
In
PWM
Out
2015
309
...
Technical Details
Parameters
Specification
General
n Multifuse for electrical safety

n Channels bundling to increase the continuous current
Signal measurement
(Digital In 2)
n 10 channels
n Supported I/O functions

Multi Bit In

PWM/PFM In
n Max. 6 A per channel
n Substitute loads pluggable, up to 2 W per measurement channel
n Real loads can be wired externally
n FIU via high-current failplane
Signal generation
(Digital Out 2)
n 10 channels

Multi Bit Out

PWM/PFM Out
n Low-side = GND
n High-side = external reference for each channel
n Voltage range high-side: 5 ... 60 V
n FIU via low-capacitance failplane
Signal measurement or generation

(Digital In/Out 1)
n 10 channels

Multi Bit In

PWM/PFM In

Multi Bit Out

PWM/PFM Out
n FIU via low-capacitance failplane
Digital In

n Max. 100 mA per channel
n Substitute loads pluggable, up to 2 W per measurement channel
n Real loads can be wired externally
Digital Out

n Low-side = GND
n High-side = external reference for each channel
n On-board failure routing unit (FRU)
Failure simulation
n Signal forwarding to central FIU

n Based on relays
n Available for each channel
n IOCNET
Physical data
n 402 x 100 x 58 mm (15.8 x 3.9 x 2.3 in)
Physical size
n Requires 3 slots
Voltage supply
n 24 V
Order Information
Product
Order Number
n DS2690
Relevant Software
Product
310
Required
2015
SCALEXIO / DS2655 FPGA Base Board
Introduction

HighFlex board with userprogrammable FPGA
Application Fields
Highlights
Key Benefits
The DS2655 includes a powerful, freely programmable fieldprogrammable gate array (FPGA), the Xilinx Kintex-7 160T.
To include I/O channels, you connect up to five I/O modules
to the board.
Together with dSPACE electronic load modules and/or the
XSG Electric Components Library, the DS2655 provides the
fast reaction times required for simulating electrical machines
in closed-loop operation with a controller (p. 511).
Hardware
Application Area
The DS2655 FPGA Base Board has been designed for applications that require very fast, high-resolution signal processing, for example:
n Hybrid vehicle applications
n Electric drive applications
n Wind energy converters
n Processor-based motor simulation
n FPGA-based motor simulation
Software
n User-progammable FPGA
n Flexible board for special I/O solutions
n Up to 5 piggyback modules for I/O can be added
DS2655M1 I/O Module
2015
Engineering
The DS2655M1 is a piggyback module for the DS2655 FPGA

Base Board. It contains the digital and analog I/O channels
needed for electric drives applications.
311
Programming the FPGA

Programs for the DS2655 FPGA Base Board's FPGA are programmed with the RTI FPGA Programming Blockset and with
XSG-based solutions. The programs are downloaded to the
FPGA via dSPACE ConfigurationDesk (p. 48).
You can test the program in offline simulation before implementing it on the real-time hardware. This enables you to
react flexibly to new requirements, such as new interfaces
or having to accelerate the execution of submodels.
Technical Details DS2655

Parameter
Specification
General
FPGA
n Xilinx Kintex-7 160T

Logic cells: 162,240 (DSP slices: 600)

Distributed RAM:480 kBits

Block RAM:11,700 kBits
Number of connectors for I/O Modules
n 5
Device timing
n 125 MHz
n IOCNET
Physical characteristics
Physical size
n 100 x 18 x 210 mm ( 3.9 x 0.7 x 8.3 in)
Power supply
n 24 V
Technical Details DS2655 M1

Parameter
Specification
Digital I/O
n 10 channels, usable as input or output
Input
n Maximum input voltage: 15 V

n Threshold for each channel adjustable from 1 V to 7.5 V
Output
n Push-pull drivers
n One output voltage can be selected for all channels: 3.3 V or 5 V
Analog I/O
Input
n 5 channels
n Resolution 14 bit
n Sampling rate 4 MSPS SAR
n Input voltage range selectable for each channel: 5 V or 30 V
Output
n 5 channels
n Resolution 14 bit
n Update rate 7.8 MSPS
n Output voltage range: 10 V
Physical
characteristics
312
Physical size
n 208 x 100 x 18 mm (8.2 x 3.9 x 0.7 in)
Power supply
n 24 V
2015
Introduction
Order Information
Required
Optional
Product
Order Number
DS2655 7K160
DS2655M1 I/O Module
DS2655_M1
Adapter for two Sub-D 50 connectors to one Hypertac connector
HYPERTRONICS_CON90_FP1_QT
Application Fields
Relevant Software
Product
RTI FPGA Programming Blockset (p. 86)
XSG Electric Components Library (p. 249)
XSG Utils Library (p. 94)
Hardware
Software
XSG AC Motor Control Library (p. 96)
Engineering
Optional
2015
313
Required
SCALEXIO / DS6101 MultiI/O Board
NEW: DS6101 MultiI/O Board

I/O hardware with signal conditioning for automotive systems
Highlights
n 69 channels for comprehensive I/O functions
n Signal conditioning for signal levels of 12-V, 24-V, and
48-V automotive systems
n Ideally suited for engine, powertrains, and vehicle
dynamic applications
Application Area
The DS6101 comprises a large variety of I/O functions needed for hardware-in-the-loop simulation and can be used
for generating and measuring typical automotive signals.
This makes the DS6101 ideally suited for applications with
extensive I/O requirements.
For failure simulation, you can connect additional hardware
to your system, such as the DS2642 FIU & Power Switch
Board. The same holds true for bus communication. There
you can revert to the DS2671 Bus Board.
Key Benefits
The DS6101 Multi I/O board offers 69 I/O channels for voltage-related functions, including analog, digital, resistance,
and special input/output groups, for example for lambda
probe simulation.
The integrated signal conditioning is tailored to automotive project requirements, such as voltages of 12 V, 24 V,
and 48 V.
I/O Functionality
The I/O channels of the DS6101 offer software-configurable
I/O functions. You can choose between analog and digital
inputs and outputs, resistance simulation channels, and
special I/O channels. All channels are defined and configured
graphically in the dSPACE ConfigurationDesk software.
314
2015
Introduction
SCALEXIO / DS6101 Multi-I/O Board
Technical Details
Parameter
Specification
General
n All I/O channels are software-configurable

n 3 x 50-pin Sub-D connectors
n 10 analog inputs
(Analog In 3)
n 12 digital inputs
n Voltage measurement range 0 ... 60 V
Application Fields
Signal Measurement
n Resolution 16 bit
n Voltage measurement range 0 ... 60 V
(Digital In 3)
n 10 variablel inputs
(Flexible In 3)
n Voltage measurement digital
Voltage range -10 ... 10 V

Fast threshold adaptation (useful for ignition/injection signal measurement)
n Voltage measurement analog
n Voltage range -10 ... 10 V
n Resolution 16 bit
n
n
Signal generation
(Analog Out 5)

Software

n Resolution 14 bit
(Analog Out 8)

n Resolution 14 bit
n Current sink: Current range -30 ... +30 mA
n 3 analog outputs (AC)
(Analog Out 3)

n Output voltage -20 ... +20 V
n Resolution 14 bit
n 6 resistance simulation channels
(Resistance Out 2)
n Effective inner resistance range 16 ... 1 M

n Voltage range -3 ... +18 V to GND
Hardware

n Power max. 250 mW
(Digital Out 3)

n Low-side = GND
n High-side Dig-Out-Ref 1 or 2
Special I/O channels
n 1 analog input and output group,
e.g., for lambda

(Analog In 4, Analog Out 6)
n 1 ADC, 12 bit
n 1 DAC, 14 bit
n Voltage range -10 ... +10 V
n IOCNET
Physical data
n 100 x 58 x 238 mm (3.9 x 2.3 x 9.4 in)
Physical size
Engineering
n Requires 3 slots
Voltage supply
n 24 V
Product
Order Number
DS6101
n DS6101
Adapter for two Sub-D 50 connectors to one Hypertac connector n HYPERTRONICS_CON90_FP1_QT
Relevant Software
Product
Required
2015
315
Order Information
NEW: DS6201 Digital I/O Board

SCALEXIO I/O board with 96 bidirectional digital I/O channels
Highlights
n 96 channels for high I/O requirements
n Signal conditioning up to 60 V
n Measures and generates automotive signals and
TLL signals
n All channels configurable as input or output
n Software-configurable channels
Application Area
The DS6201 Digital I/O Board comprises a large number of
digital I/O channels that can all be configured as input or
output channels. The available I/O functions cover digital,
PWM, and PFM functions for hardware-in-the-loop simulation in automotive projects, such as the test of body electronics ECUs.
Additionally the DS6201 includes an onboard signal conditioning unit. This makes the DS6201 a cost-efficient way
to start a HIL simulation project.
Key Benefits
The DS6201 Digital I/O Board offers 96 I/O channels for signal measurement and signal generation. The onboard signal
conditioning is tailored to automotive project requirements,
such as voltages of 12 V, 24 V, 36 V, and 48 V, as well as to
customary TLL levels.
I/O Functionality
The 96 digital channels of the DS6201 can be configured
for signal measurement or signal generation. They can be
used as
n Multi Bit In or Out
n PWM In or Out
n PFM In or Out
The channels are software-configurable and are defined and
configured graphically in the dSPACE ConfigurationDesk
software.
316
2015
Introduction
Technical Details
Parameter
Specification
General

n Multi Bit In
Application Fields
n PWM/PFM In
n Multi Bit Out
n PWM/PFM Out
n 3 x 50-pin Sub-D connectors
n Digital inputs
n Digital outputs

n Low-side = GND
n High-side
= 2 independent external high-side references per group (Sub-D connector /

32 channels)
n Voltage range high-side: 3.3 ... 60 V
n Current max. 80 mA
n IOCNET
Physical data
n 100 x 58 x 238 mm (3.9 x 2.3 x 9.4 in)
Physical size
Software
Digital signal measurement

or generation
(Digital In/Out 2: Digital In/
Out 1)
n Requires 3 slots
Voltage supply
n 24 V
Order Information
Order Number
DS6201
n DS6201
Adapter for two Sub-D 50 connectors to one Hypertac connector
n HYPERTRONICS_CON90_FP1_QT
Hardware
Product
Relevant Software
Product
Engineering
2015
317
Required
SCALEXIO / DS2601 Signal Measurement Board
DS2601 Signal Measurement Board

HighFlex board for measuring ECU output signals
Highlights
n Current and voltage measurement
n Channel bundling to increase current carrying capacity
n Configurable fuses
n Onboard failure routing unit
n Onboard loads or external loads via 2nd connector
n Galvanically isolated channels
Application Area
The DS2601 Signal Measurement Board measures ECU output signals and passes the measurement values to the realtime processor. Signal measurement can be time-triggered
or event-triggered, and the execution of signal measurement
can be voltage- or current-triggered.
For information on the failure simulation function, see

Failure Simulation on p.300.
I/O Functionality
The DS2601 has 10 flexibly configurable input channels,
onto the board itself or connect real loads via a cable harness to the externally accessible load connector.
which can connect analog (analog-digital converter) and
also digital (comparator) measurement units
to measure the current and voltage. For
example, the measurement units can be comLoad connector
IOCNET interface
I/O connector
bined to trigger analog current measurement
if a specified voltage is exceeded. The channels
DC
are defined and configured in the ConfiguraDC
tionDesk software.
Fuse
The 10 channels on the DS2601 can be conFRU
Controller
nected in parallel. This channel bundling
AnalogFuse
Voltage
increases the current-carrying capacity up to
digital
measurement
converter
Measurement
80A (RMS). ConfigurationDesk displays the
circuit
Current
Comparator
measurement
Internal load
bundled channels as one single I/O function.
10
...
The DS2601 supports the use of loads for the
Status LED
LED
1
ECU. You can either plug substitute loads
318
2015
Introduction
SCALEXIO / DS2601 Signal Measurement Board
Technical Details
Parameter
Specification
General
n 10 galvanically isolated channels for signal measurement

n Load connections for plugging loads of up to 2W on the board
Application Fields
n External load connection (for real loads or substitute loads > 2 W)

n Up to 10 channels connected in parallel to increase the continuous current to max. 80 A
n Status LED for overall board status
n 10 channel-specific LEDs to indicate channel voltage
n Voltage 60 V per channel
Electrical capacity
n Continuous current 10 A per channel

n Maximum continuous current of 80 A when all 10 channels bundled
Signal measurement
(Flexible In 1)
n Adjustable digital filtering for analog measurements

n Current/voltage measurement: Sampling rate up to 250 kHz
Voltage measurement
n Voltage measurement 60 V per channel

n Voltage, analog and digital (settable trigger value)
n ADC resolution 16 bit
n Current measurement 30 A per channel
Software
Current measurement
n Current measurement, analog and digital (settable trigger value)

n ADC resolution 16 bit
Trigger
n Time-, angle- and event-driven signal measurement

n Voltage-driven current measurement
n Control from within the model
n Onboard failure routing unit (FRU)
Failure simulation (p.8)

n Relay-based
n Software-configurable and software-resettable
Electronic fuses
n IOCNET
Physical data
n 410 x 100 x 41 mm (16.1 x 4.2 x 1.6 in)
Physical size
Hardware
n Fuse trip settable 0.5 ... 10 Aeff
n Requires 2 slots
Voltage supply
n 24 V
Product
Order Number
DS2601 Signal Measurement Board
n DS2601
Engineering
Order Information
Relevant Software
Product
2015
319
Required
SCALEXIO / DS2621 Signal Generation Board
DS2621 Signal Generation Board

HighFlex I/O board for simulating ECU input signals
Highlights
n Signal generation for simulating voltage, current,
resistance and switches
n Channel bundling to increase output voltage
n Galvanically isolated channels
Application Area
The DS2621 Signal Generation Board stimulates ECU inputs.
It mimics sensors or switches such as door contact switches,
Hall sensors, and sensors for wheel speed and oil temperature. Each of the DS2621's 10 channels can be softwareconfigured as a voltage source, a current sink, a digital
output simulation or a resistance simulation.
I/O Functionality
The DS2621 has 10 flexibly configurable output channels
to make analog and digital signal generators available. To
increase the current or voltage range, up to 10 channels can
be bundled in parallel or in series. For example, two voltage
sources can be switched in sequence, or two current sinks in
parallel, to increase the output voltage or current. The digital
output can be used as a switch and can generate time- and
frequency-dependent signals (such as PWM). For example,
the resistance simulation can be used to pass the specified
temperature changes to an ECU via the environment model.
Channel bundling is supported by the software. ConfigurationDesk displays the bundled channels as one single I/O
function.
320
For information on the failure simulation function, please

refer to Failure Simulation on p.300.
IOCNET connection
I/O connector
DC
Current sink
DC
Voltage
source
Fuse
Controller
Digital output
FRU
Fuse
Resistance
simulation
Signal generator
circuits
1
... 10
Status LED
2015
Introduction
SCALEXIO / DS2621 Signal Generation Board
Technical Details
Parameter
Specification
General
n 10 galvanically isolated channels

n Up to 10 channels can be connected in sequence or in parallel to increase the current range
Application Fields
to max. 320 mA and the voltage range to max. 60 V

Signal generation
(Flexible Out 1)
Voltage source
n Output voltage 20 V
n Output current 40 mA
n DAC resolution 16 bit
n Signal frequency 0 ... 140 kHz (sine)
Current sink
n Voltage range 60 V
n Current range 40 mA
n DAC resolution 15 bit
n Signal frequency 0 140 kHz (sine)
Resistance simulation
n Resistance range 17.5 ... 1 M

Software
Digital output
n Signal frequency 0 ... 1 MHz
Failure simulation (p.8)
n Onboard failure routing unit (FRU)

n Relay-based
Electronic fuses
n 100 mA RMS ECU (effective value)

n On ECU side tripping at I = 100 mA
n IOCNET
Physical data
n 410 x 100 x 15 mm (16.1 x 3.9 x 0.6 in)
Physical size
Hardware
n On sensor side with configurable trip range I = 5 ... 40 mA
n Requires 1 slot
Voltage supply
n 24 V
Product
Order Number
DS2621 Signal Generation Board
n DS2621
Engineering
Order Information
Relevant Software
Product
2015
321
Required
SCALEXIO / DS2642 FIU & Power Switch Board
DS2642 FIU & Power Switch Board

HighFlex board for powerswitching with Failure Insertion Unit
Highlights
n Central FIU
n Switched battery voltage
n Failure feedforward
n High-precision current measurement on each channel
Application Area
The DS2642 FIU & Power Switch Board combines two components:
n Central Failure Insertion Unit (FIU) for simulating failures
for the I/O channels of the SCALEXIO HighFlex boards
and MultiCompact units
Central FIU
The central FIU on the DS2642 is connected to the failure
routing units of the I/O boards via the fail rails. It switches
the failures for the channels on the boards.
The following options are available:
n Broken wires on each individual channel, with or without bouncing as selected
n Crossed wire between two channels, with or without
bouncing
n Short circuit to a fixed potential such as the supply
voltage, with or without bouncing
The failures are prepared on the I/O boards by relays, and
failure insertion is performed by semiconductor switches on
the central FIU. The result is a fast switching frequency that
enables loose contacts to be simulated.
322
n Power switches for simulating up to 10 switched

potentials, for example, on terminal K15
Power Switch
The power switch provides 10 switchable channels, which
supply current to the external devices such as ECUs and
loads. The current can be measured simultaneously. The
central FIU can also use the power switch channels to simulate short circuits to the supply to the ECU. The channels
can be bundled to increase the current, and are selected in
ConfigurationDesk. Several DS2642s can be used in one
SCALEXIO system.
Current Measurement
The power consumption of the connected components
can be measured precisely on each power switch channel.
2015
Introduction
SCALEXIO / DS2642 FIU & Power Switch Board
Technical Details
Parameter
Specification
Power switches (Power Switch 1)
General
n 10 channels for the ECU's current supply

n Voltage 60 V
Application Fields
n Continuous current 10 A per channel

n Channel parallelization to increase the measurement range to max. 80 A (RMS)
n 10 channel-specific LEDs for channel status (power switch open/closed)
Current Measurement
n Current measurement on each channel

n Precision mode
n Resolution 6.25 A
n Sampling time 135 ms
n Measurement range 0 ... 1.6 A
n Dynamic mode
n Resolution 150 A
n Sampling time 262 s
n Measurement range 0 A ... 39 A
n 10 A RMS ECU (effective value)
Software
Electronic fuses
n Software-configurable and software-resettable
Failure Insertion Unit
General
n Voltage 60 V
n Failure switch for up to 80 A
n Continuous current for LC fail rail 80 A
n Continuous current fail rail with low capacitance 1 A
n Status LED for the FIU component
Failure types
n Broken wire
n Short circuit to GND or UBat
n Crossed wire between two channels
n IOCNET

Physical data
Hardware
n All failures with optional bouncing
Physical size
n 410 x 100 x 41 mm (16.1 x 3.9 x 1.6 in)

n Requires 2 slots
Voltage supply
n 24 V
Product
Order Number
DS2642 FIU & Power Switch Board
n DS2642
Engineering
Order Information
Relevant Software
Product
2015
323
Required
SCALEXIO / DS2671 Bus Board
DS2671 Bus Board

HighFlex board for interfacing to different bus systems
Highlights
n Supports CAN, LIN, and FlexRay bus systems
n 4 flexibly configurable channels
Application Area
The DS2671 Bus Board is the interface between dSPACE
Simulator and various bus systems. It has 4 multifunctional
channels, each of which can support a bus system that is
assigned to it by software.
The following buses and protocols are supported:
n FlexRay
n CAN (high-speed & fault-tolerant)
n LIN/K-line
n RS232, RS422, RS485
n TLLbased protocols
I/O Functionality
Each channel on the DS2671 has a bus FPGA, all the standardly supported transceivers for bus systems and protocols,
and a piggyback slot for customer-specific transceivers. The
bus system controllers, which include certified IP cores such
as the Bosch E-Ray controller for FlexRay, are implemented
on the bus FPGA.
To use a bus system or protocol that is not yet standardly
supported, you can install the necessary transceiver in the
channel's piggyback slot.
324
With its freely configurable channels, the DS2671 can serve

different bus systems for one ECU. The selected bus system
can easily be changed from project to project because the
channels can be completely configured by software.
Other bus systems and protocols can be added on request.
A different bus system can be used on each of the 4 channels on the DS2671.
2015
Introduction
SCALEXIO / DS2671 Bus Board
Technical Details
Parameter
Specification
General
n 4 independent bus channels

n Onboard failure routing unit (FRU) (p. 300)
Application Fields
n Overvoltage and undervoltage protection for transceivers

n Parallel termination resistors with overcurrent protection
n Channel-specific LEDs for individual bus channels (inactive, ready for data transfer, data
transfer running, error message)

n One piggyback module slot per channel for a customer-specific transceiver
Supported protocols/bus systems
n FlexRay 2.1 (based on Bosch E-Ray)

n High-speed CAN (ISO 11898-2)
n Fault-tolerant CAN (ISO 11898-3)
n LIN 2.0/K-line (ISO 9141)
n RS232, RS422 and RS485
n IOCNET
Physical data
n 410 x 100 x 15 mm (16.1 x 3.9 x 0.6 in)
Physical size
Software
n TTL driver
n Requires 1 slot
n 24 V
Voltage supply
Product
Order Number
DS2671 Bus Board
n DS2671
Hardware
Order Information
Relevant Software
Product
IOCNET
connection
I/O connector
DC
Required
Optional

DC
Engineering
Fuse
FRU
Termination
Controller
or
Piggyback
Bus FPGA
.
1 ..
Status LED
LED
2015
325
Bus
transceivers
SCALEXIO / DS2907 Battery Simulation Controller
DS2907 Battery Simulation Controller

Power supply control for battery simulation
Highlights
n Supports different power supply units for battery
simulation
n Wiring simplified by adapter
Application Area
The DS2907 Battery Simulation Controller is used to control
the current and voltage values of battery simulation in a
SCALEXIO system. Control is performed by software.
Supported Power Supply Units

Two adapter modules are available for easier connection
and wiring of different power supply units.
Two battery simulation modules can be plugged onto the

DS2907 to support up to two power supply units from
different manufacturers like TDK-Lambda and Delta. Other
power supply units can also be used.
No slot is needed for mounting it in SCALEXIO. An optical

IOCNET connection acts as an internal interface.
Battery Simulation Adapter Module
Supported Power Supply Units
DS2907M1 Adapter Module
TDKLambda Genesys 20V76A
Delta SM35/45 (with RS232 option P183)1)
Delta SM15/100 (with RS232 option P183)1)
DS2907M2 Adapter Module

1)
Example of custom-specific solution. Further power supplies can be supported on request.
Order Information
Product
Order Number
DS2907 Battery Simulation Controller (Base Board)
DS2907
DS2907M1 Adapter Module for TDKLambda power supply units n DS2907_M1

DS2907M2 Adapter Module for Delta power supply units
DS2907_M2
Relevant Software
Product
Required
326
2015
SCALEXIO / Additional Solutions
Introduction
Additional Solutions
SCALEXIO Interface Solution for ARINC 429
Application Fields
The SCALEXIO Interface Solution for ARINC 429 enables the

connection of a dSPACE real-time system to an ARINC 429
network for hardware-in-the-loop applications. ARINC 429 is
typically used in projects for commercial aerospace industries.
The solution is based on PMC modules from AIT, full-featured
and aerospace-industry-proven hardware. The PMC modules
are on a carrier board that plugged into the SCALEXIO processing unit (p. 304), providing the optimal bandwidth to
the real-time model. dSPACE specifically developed QNX
device drivers to ensure real-time simulation capability.
Software
Configuration with the well-known and etablished AIT Flight

Simulyzers is seamlessly integrated into the configuration
process via dSPACE ConfigurationDesk (p. 48).
Technical Details
Parameter
Specification
General
n AIT ARINC 429 module on PCI carrier Board
Hardware
n 4, 8, 16, or 32 software-programmable Tx/Rx channels per PMC module

n AIT Flight Simulyzer used for fieldbus configuration
n Code generation by ConfigurationDesk
n Programmable high-speed and low-speed operation
Features
n Transmission and reception of multiple labels per channel

n Multiple transmission rates for individual labels
n Configuration of the labels based on the data formats and scaling factors
n Transmission of same labels with different SDI values possible
n Scheduled transfers and block transfers supported
n Data buffers for individual labels for scheduled and block transfers
Order Information
Product
Order Number
SCALEXIO Interface Solution for ARINC 429
Please inquire
2015
327
Engineering
n Continuous and counter-based transfers
SCALEXIO Interface Solution for MIL-STD-1553

The SCALEXIO Interface Solution for MIL-STD-1553 enables the connection of a dSPACE real-time system to an
MIL-STD-1553 network for hardware-in-the-loop applications. MIL-STD-1553 is typically used in projects for noncommercial aerospace industries.
are on a carrier board that is plugged into the SCALEXIO
processing unit (p. 304), providing the optimal bandwidth
to the real-time model. dSPACE specifically developed QNX
Technical Details
Parameter
Specification
General
n AIT MIL-Std-1553 XMC module on PCI carrier Board

n One, two or four dual redundant MIL-STD-1553A/B databus streams
n Operate as bus controller, 31 remote terminals, and bus monitor operation
Features
n Multi-level trigger for capture and filtering

n IRIG-B time code encoder/decoder
n FPGA-based hardware architecture
n Transformer or direct coupling for connection to the MIL-STD-1553A/B bus stub
Order Information
328
Product
Order Number
SCALEXIO Interface Solution for MIL-STD-1553
Please inquire
2015
Introduction
NEW: SCALEXIO Interface Solution for AFDX
Application Fields
The SCALEXIO Interface Solution for AFDX (AFDX is a

registered trademark of Airbus) enables the connection of a
dSPACE real-time system to an AFDX network for hardwarein-the-loop applications. AFDX is typically used in projects
for commercial aerospace industries.
are on a carrier board that is plugged into the SCALEXIO
processing unit (p. 304), providing the optimal bandwidth
to the real-time model. dSPACE specifically developed QNX
Software

Technical Details
Parameter
Specification
General
n AIT AFDX PMC module on PCI carrier Board
Hardware
n Dual Channel Copper AFDX PXI Interface

n Simulates up to 32 ARINC 664 End Systems, including virtual link (VL) traffic shaping and
Features
input VL redundancy management

n Support for up to 128 output virtual links
n Support for up to 512 input virtual links
n Time stamping of all received messages with 8 ns resolution
n Support for transfers of the following types:
n UDP Sampling
Engineering
n UDP Queuing
n SAP (Service Access Ports) UDP
n SAP IP
n SAP MAC
Product
Order Number
SCALEXIO Interface Solution for AFDX
Please inquire
2015
329
Order Information
SCALEXIO Interface Solution for PROFIBUS and EtherCAT

The dSPACE SCALEXIO Field Bus Solution lets you connect
a SCALEXIO hardware-in-the-loop system to various field
bus types, such as PROFIBUS and EtherCAT. The solution is
based on a PCI card, which is plugged into the SCALEXIO
processing unit (p. 304) to provide the optimal bandwidth
to the real-time model. Specially developed device drivers
ensure real-time simulation capability. Different licenses are
required according to the type of field bus. Configuration is
performed in dSPACE ConfigurationDesk (p. 48).
Technical Details
Parameter
Specification
General
Hilscher softwarereconfigurable boards

CIFX PCI PROFIBUS board
n CIFX PCI RealTime Ethernet (RTE) board
n SyCon.Net used for fieldbus configuration
n
PROFIBUS Features
Bus master and slave supported

Cyclic data exchange by selectable bus cycle time
n PROFIBUSspecific settings performed in SyCon.net
n
n
EtherCAT Features
n
n
n
n
n
n
Bus master and slave supported

Cyclic data exchange by selectable bus cycle time
Bussynchronous interrupts
Distributed clocks
EtherCAT master bus cycle 500 s or larger
EtherCAT slave bus cycle depending on the EtherCAT bus master
Order Information
330
Product
Order Number
SCALEXIO Interface Solution for PROFIBUS and EtherCAT
Please inquire
2015
Introduction
PSI5 Master/Slave Solution
Application Fields
n Based on the Programmable Generic Interface (PGI1)

n Generic interface box for decentralized connection of
sensors and actuators to dSPACE systems via diverse
serial interfaces and protocols
n Emulation of sensor signals (e.g., of yaw rate or crash
sensors) with hardware-in-the-loop (HIL) simulation
n Connection to a SCALEXIO system via Ethernet
n PSI5 Master/Slave Solution supporting up to 4 masters
and 10 slaves
2015
331
Engineering
Hardware
Software
For more information, see page 477.
SingleBoard Hardware / Introduction
SingleBoard Hardware
For building a complete realtime control system with just one controller board
Highlights
n Compact and versatile controller boards
n For a variety of applications in rapid control
prototyping
n Real-time processor for fast calculation of models
n Variety of I/O components
Application Areas
Controller development and rapid control prototyping are
ideal application areas for the DS1103 PPC Controller Board
and the DS1104 R&D Controller Board.
The DS1103 (ISA bus) can be installed in an AutoBox or
a dSPACE Expansion Box. The DS1104 board can be installed in virtually any PC with a free PCI or PCIe slot.
332
Key Benefits
Both boards, the DS1103 as well as the DS1104, combine
compactness with high performance and a high number of
features. Used with Real-Time Interface (RTI), the controller
boards are fully programmable from the Simulink block
diagram environment.
2015
Introduction
SingleBoard Hardware / Introduction
DS1103 PPC Controller Board

Versatile controller board with an unparalleled number of
I/O modules, including CAN, and ample calculation power
for control prototyping.
dSPACE offers two compact and versatile controller boards

for different requirements and fields of application:
the DS1103 PPC Controller Board and the DS1104 R&D
Controller Board.
DS1104 R&D Controller Board

Cost-effective controller board with a comprehensive set of
I/O modules frequently used in control systems.
n
Connector Panels (p. 346)
Demo Equipment (p. 347)
Hardware
Demo Equipment
For educational and training purposes, dSPACE also offers
demo equipment for single-board hardware. The demo
equipment comprises hardware for the simulation of typical
mechanical positioning systems and cables for connection
to the controller boards.
tailored to a specific controller board, so that you have all the

signals for easy connection to the real world at your disposal.
Engineering
Connector Panels
All I/O signals of controller boards can usually be accessed
via adapter cables. A more convenient solution is I/O access
via connector panels, which make the signals available
in either a 19 rack or a 19 desktop box. The panels are
Software
Programming Single-Board Hardware

Implementing your model on dSPACE single-board hardware
is easy with Simulink and dSPACEs Real-Time Interface.
You can initialize and configure the on-board I/O modules
graphically within the Simulink environment. Real-time code
generation, compiling and downloading is reduced to a
single mouse click. Programming your single-board hardware without Real-Time Interface is also possible with the
included C software environment, together with a compiler and loader software.
n
Real-Time Interface (RTI) (p. 54)
2015
333
Application Fields
Controller Boards
Controller boards contain a real-time processor for fast
calculation of your model, and a variety of I/O interfaces
that allow you to carry out your control developments.
SingleBoard Hardware / DS1103 PPC Controller Board

Powerful controller board for rapid control prototyping
Highlights
n Single-board system with real-time processor
and comprehensive I/O
n CAN interface and serial interfaces ideally suited
to automotive applications
n High I/O speed and accuracy
n PLL-driven UART for accurate baud rate selection
Application Areas
The DS1103 controller board is designed to meet the requirements of modern rapid control prototyping and is highly
suitable for applications such as:
n Automotive controllers
n Induction motor control
n Robotics
n Positioning systems and stepper motors
n Active vibration control
Key Benefits
The DS1103 is an all-rounder in rapid control prototyping. You can mount the board in a dSPACE Expansion Box
or dSPACE AutoBox to test your control functions in a
laboratory or directly in the vehicle. Its processing power
and fast I/O are vital for applications that involve numerous actuators and sensors. Used with Real-Time Interface
(RTI, p. 54), the controller board is fully programmable from
the Simulink block diagram environment. You can configure
all I/O graphically by using RTI. This is a quick and easy way
to implement your control functions on the board.
An integrated Infineon CAN microcontroller makes the

board an attractive tool for automotive and automation
applications.
Comprehensive Interfaces
The unparalleled number of I/O interfaces makes the DS1103
a versatile controller board for numerous applications. It
provides a great selection of interfaces, including 50 bitI/O channels, 36 A/D channels, and 8 D/A channels. For
additional I/O tasks, a DSP controller unit built around Texas
Instruments TM320F240 DSP is used as a subsystem.
334
Recording and Output of I/O Values

The control of electrical drives requires accurate recording
and output of I/O values. It is possible to synchronize the
A/D channels and D/A channels, and the position of the
incremental encoder interface, with an internal PWM signal
or an external trigger signal. Also, the serial interface (UART)
is driven by a phase-locked loop to achieve absolutely
accurate baud rate selection.
2015
Introduction
Single-Board Hardware / DS1103 PPC Controller Board
Technical Details
Parameter
Specification
Processor
PowerPC Type
n PPC 750GX
CPU clock
n 1 GHz
Cache
n 32 KB level 1 (L1) instruction cache

n 32 KB level 1 (L1) data cache
Memory
Timer
n 133 MHz
Temperature sensor
n Reads actual temperature at the PPC
Local memory
n 32 MB application SDRAM as program memory, cached
Global memory
n 96 MB communication SDRAM for data storage and data exchange with host
2 general-purpose timers
n One 32-bit down counter
Application Fields
n 1 MB level 2 (L2)
Bus frequency
n Reload by software
n 15-ns resolution
n One 32-bit up counter with compare register
n 30-ns resolution
1 sampling rate timer (decrementer)
n 32-bit down counter
Software
n 30-ns resolution
1 time base counter
n 64-bit up counter
n 30-ns resolution
n 3 timer interrupts
Interrupt controller
n 7 incremental encoder index line interrupts

n 1 UART (universal asynchronous receiver and transmitter) interrupt
n 1 CAN interrupt
n 1 slave DSP interrupt
n 2 slave DSP PWM interrupts
n 1 host interrupt
n 16 multiplexed channels equipped with 4 sample & hold A/D converters
(4 channels belong to one A/D converter. 4 consecutive samplings are necessary to sample
all channels belonging to one A/D converter.)
n 4 parallel channels each equipped with one sample & hold A/D converter
n Note: 8 A/D converter channels (4 multiplexed and 4 parallel) can be sampled simultaneously.
Resolution
n 16-bit
Input voltage range
n 10 V
Overvoltage protection
n 15 V
Conversion time
n Multiplexed channels: 1 s1)
D/A converter
Offset error
n 5 mV
Gain error
n 0.25%
Offset drift
n 40 V/K
Gain drift
n 50 ppm/K
Signal-to-noise ratio
n >83 dB
Channels
n 8 channels
Resolution
n 16-bit
Output range
n 10 V
Settling time
n 5 s (14-bit)
Offset error
n 1 mV
Gain error
n 0.5%
Offset drift
n 30 V/K
Gain drift
n 25 ppm/K
Speed and timing specifications describe the capabilities of the hardware components and circuits of our products.
Depending on the software complexity, the attainable overall performance figures can deviate significantly from the hardware
specifications.
Engineering
n Parallel channels: 800 ns1)
1)
2015
335
Channels
Hardware
n 4 external interrupts (user interrupts)
A/D converter
Parameter
Specification
D/A converter
Digital I/O
n >83 dB
I max
n 5 mA
C I max
Channels
n 10 nF
n 32-bit parallel I/O
n Organized in four 8-bit groups
n Each 8-bit group can be set to input or output (programmable by software)
Digital incremental
encoder interface
Voltage range
n TTL input/output levels
I out, max
n 10 mA
Channels
n 6 independent channels
n Single-ended (TTL) or differential (RS422) input (software programmable for each channel)
Position counters
n 24-bit resolution
n Max. 1.65 MHz input frequency, i.e.,fourfold pulse count up to 6.6 MHz
n Counter reset or reload via software
Encoder supply voltage
n 5 V/1.5 A
n Shared with analog incremental encoder interface
Analog incremental
encoder interface
n 1 channel
Channels
n Sinusoidal signals: 1 Vpp differential or 11App differential (software programmable)
Position counters
n < 5 resolution
n 32-bit loadable position counter
n Max. 0.6 MHz input frequency, i.e., fourfold pulse count up to 2.4 MHz
A/D converter performance
n 6-bit resolution
n 10 MSPS
Encoder supply voltage
n 5 V/1.5 A
n Shared with digital incremental encoder interface
CAN interface
Configuration
n 1 channel based on SAB 80C164 microcontroller

n ISO DIS 11898-2 CAN high-speed standard
Serial interface
Baud rate
n Max. 1 Mbit/s
Configuration
n TL6C550C single UART with FIFO

n RS232/RS422 compatibility
n Up to 115.2 kBd (RS232)
Baud rate
n Up to 1 MBd (RS422)
Slave DSP
Type
n Texas Instruments TMS320F240 DSP
Clock rate
n 20 MHz
Memory
n 64 Kx16 external code memory

n 28 Kx16 external data memory
n 4 Kx16 dual-port memory for communication
n 32 KB flash memory
I/O channels1)
n 16 A/D converter inputs

n 10 PWM outputs
n 4 capture inputs
n 2 serial ports
Input voltage range
n TTL input/output level

n A/D converter inputs: 0 5 V
Output current
Host interface
n Max. 13 mA
n Plug & Play support
n Requires a full-size 16-bit ISA slot
Physical
characteristics
Physical size
n 340 x 125 x 45 mm (13.4 x 4.9 x 1.77 in)
Ambient temperature
n 0 50 C (32 122 F)
Cooling
n Passive cooling
Power supply
n +5 V 5%, 4 A
n +12 V 5%, 0.75A
n -12 V 5%, 0.25A
336
2015
1)
The exact number of I/O channels depends on your configuration and is described in the user documentation.
Product
Order Number
n DS1103
Introduction
Order Information

Order Number
Included
Required
Optional
n DS1103 Real-Time Library
n Experiment and Platform Manager for hardware management
n Real-Time Interface (RTI) (p. 54)
n RTI
n Microtec C Compiler for PowerPC (p. 98)
n CCPPPC
n Real-Time Interface CAN Blockset (p. 68)
n RTICAN_BS
n Real-Time Interface CAN MultiMessage Blockset (p. 70)
n RTICANMM_BS
n ControlDesk Next Generation (p. 106 )
See p. 106
n PLATFORM_API
n MotionDesk (p. 140)
n MotionDesk
Order Number
Optional
n Connector Panel (p. 346)
n CP1103
n Connector/LED Combi Panel (p. 346)
n CLP1103
n Set of adapter cables for DS1103
n ADP_CAB1103
Software
Hardware
Application Fields
Software
PC
ISA Bus
Host
Interface
PowerPC
750GX
Hardware
Block Diagram
Slave
DSP I/O
96 MB
Communication
SDRAM
PWM
1 x 3-Phase
4 x 1-Phase
TMS320F240
DSP
Local Bus
2 General
Purpose
Timers
Interrupt
Controller
Dual Port
RAM
DAC
8 channels
16-bit
Incr. Encoder
7 channels
Digital I/O
32 channels
Serial
peripheral
interface
Serial
communication
interface
16- / 32-bit I/O Bus
ADC
20 channels
16-bit
Analog Input
16 ch. 10-bit
Serial
Interface
RS232/RS422
Dual Port
RAM
Digital I/O
18 bits
CAN Interface
on 80C164
Master PPC I/O
DS1103
2015
337
32 MB
Application
SDRAM
Engineering
4 Capture
Inputs
SingleBoard Hardware / DS1103 PPC Controller Board
Graphical Configuration of the Controller Board

Using RTI
With Real-Time Interface (RTI, p. 54), you can easily run your
Simulink models on the controller board. You can configure
all I/O graphically by using RTI. Thereby, the implementation
time is reduced to a minimum. With the RTI CAN Blockset
(p. 68), CAN configurations can be completely carried out
in a Simulink block diagram, with very little effort.
RTI CAN MultiMessage Blockset (p. 70) for graphical configuration

of CAN interfaces.
RealTime Interface (p. 54) provides Simulink blocks for convenient

configuration of items such as A/D, D/A, digital I/O lines, incremental
encoder interface and PWM generation.
338
2015
Introduction
Robotics
Easy Handling
In the example below, the controller board replaces the
position controller. The easy programmability of the DS1103
enables you to implement and test different control algorithms very quickly, which reduces design iteration times
to a minimum. The prototyping hardware allows easy
parameter changing and modification, without any hardware
setup changes.
Application Fields
Rapid Control Prototyping in Robotics

The DS1103 provides six digital incremental encoder inter
faces. This is sufficient to pick up all the movements of
a six-joint robot. Thus, this cost-effective single-board
hardware makes it possible to perform rapid control
prototyping in robotics.
Hardware
Software
Calculating Values
The real-time system picks up the robots six incremental
encoder signals to determine the current robot position.
Then this data is compared with the reference values.
Afterwards, the DS1103 calculates the control algorithm
and sends the controller output for example, data on
positions and velocities back to the robot.
Further Processing Potential

All reference values are calculated in real-time, even for
inverse kinematics with highly nonlinear functions. External sensors such as axis-force momentum sensors can be
included. Performing trajectory planning and advanced
algorithms for collision avoidance is also very convenient
with the DS1103 PPC Controller Board.
2015
339
Engineering
Calculating a control algorithm for robotics on a DS1103 PPC Controller Board.
SingleBoard Hardware / DS1104 R&D Controller Board

Costeffective system for controller development
Highlights
n Single-board system with real-time hardware
and comprehensive I/O
n Cost-effective
n PCI hardware for use in PCs
n Variant with PCIe (PCI Express) host interface
Application Areas
The real-time hardware based on PowerPC technology and
its set of I/O interfaces make the controller board an ideal
solution for developing controllers in various fields, such as
drives, robotics, and aerospace. The board is used in many
university laboratories.
Key Benefits
The DS1104 R&D Controller Board upgrades your PC to a
powerful development system for rapid control prototyping
(R&D stands for research & development). Real-Time
Interface (RTI, p. 54) provides Simulink blocks for graphical
I/O configuration. The board can be installed in virtually any
PC with a free PCI or PCIe slot.
Using Real-Time Interface

With Real-Time Interface (RTI), you can easily run your function models on the DS1104 R&D Controller Board. You can
configure all I/O graphically, insert the blocks into a Simulink
block diagram, and generate the model code via Simulink
Coder (formerly Real-Time Workshop). The real-time model
is compiled, downloaded, and started automatically. This
reduces the implementation time to a minimum.
340
2015
Introduction
Single-Board Hardware / DS1104 R&D Controller Board
Technical Details
Parameter
Specification
Processor
n MPC8240 processor with PPC 603e core and on-chip peripherals

n 64-bit floating-point processor
n CPU clock: 250 MHz
Timer
Global memory
n 32 MB SDRAM
Flash memory
n 8 MB
Application Fields
n 2 x 16KB cache, on-chip
Memory
n Reload by hardware
n 80-ns resolution
1 sampling rate timer (decrementer)

n 40-ns resolution
1 time base counter
n 64-bit up counter
n 40-ns resolution
n 5 timer interrupts
n 2 incremental encoder index line interrupts
Software
n 1 UART interrupt
n 1 slave DSP interrupt
n 1 slave DSP PWM interrupt
n 5 A/D converter (end of conversion) interrupts
n 1 host interrupt
n 4 external interrupts (user interrupts)
A/D converter
Channels
n 4 multiplexed channels equipped with one sample & hold A/D converter (1x16-bit)
n 4 parallel channels each equipped with one sample & hold A/D converter (4x12-bit)
n Note: 5 A/D converter channels (1x16-bit and 4x12-bit) can be sampled simultaneously
Resolution
n Multiplexed channels: 16 bit

n 10 V
Conversion time
n Multiplexed channels: 2 s1)
Hardware
n Parallel channels: 12 bit
Input voltage range
n Parallel channels: 800 ns1)
Offset error
n 5 mV
Gain error
n Multiplexed channels: 0.25%

n Parallel channels: 0.5%
Offset drift
n 40 V/K
Gain drift
n 25 ppm/K
n Multiplexed channels: >80 dB

n 8 channels
Resolution
n 16-bit
Output range
n 10 V
Settling time
n Max. 10 s (full-scale, accuracy LSB)
Offset error
n 1 mV
Gain error
n 0.1%
Offset drift
n 130 V/K
Gain drift
n 25 ppm/K
n >80 dB
Imax
Channels
n 5 mA
n 20-bit parallel I/O
n Single bit selectable for input or output
1)
Voltage range
n TTL input/output levels
Iout, max
n 5 mA
Speed and timing specifications describe the capabilities of the hardware components and circuits of our products. Depending on
the software complexity, the attainable overall performance figures can deviate significantly from the hardware specifications.
2015
341
Digital I/O
Channels
Engineering
n Parallel channels: >65 dB
D/A converter
Parameter
Specification
Digital incremental
encoder interface
Channels
n 2 independent channels
n Selectable single-ended (TTL) or differential (RS422) input (software programmable
for each channel)

Position counters
n 24-bit resolution
n Max. 1.65 MHz input frequency, i.e., fourfold pulse count up to 6.6 MHz
n Counter reset or reload via software
Serial interface
Sensor supply voltage
n 5 V/0.5 A
Configuration
n Single UART (universal asynchronous receiver and transmitter) with FIFO

n RS232/RS422/RS485 compatibility
Baud rate
n Up to 115.2 kBd (RS232)

n Up to 1 MBd (RS422/RS485)
Slave DSP
n Texas Instruments TMS320F240 DSP
Type
n 16-bit fixed-point processor
Clock rate
n 20 MHz
Memory
n 64Kx16 external code memory

n 28Kx16 external data memory
n 4Kx16 dual-port memory for communication
n 32 KB flash memory
I/O channels
1)
n 10 PWM outputs
n 4 capture inputs
n 1 serial peripheral interface
Input voltage range
n TTL input/output level

n A/D converter inputs: 0 5 V
Output current
n Max. 13 mA
Host interface (requires one PCI or one PCIe x 1 slot)
PCI
PCIe
Physical
characteristics
Physical size
n 185 x 107 mm (7.28 x 4.2 in)
n 220 x 111 mm (8.66 x 4.3 in)
Ambient temperature
n 0 55 C (32 131 F)
n 0 55 C (32 131 F)
Cooling
n Active cooling by fan
n Active cooling by fan
Power consumption
n 18.5 W
Please inquire
Power supply
n +5 V 5%, 2.5 A
Please inquire
n +12 V 5%, 0.3 A

n -12 V 5%, 0.2 A
1)
342
The exact number of I/O channels depends on your configuration and is described in the user documentation.
2015
Introduction
Order Information
Product
Order Number
DS1104 R&D Controller Board (with PCI host interface)
n DS1104
DS1104 R&D Controller Board (with PCI Express host interface)
n DS1104PCIE
Software
Order Number
n DS1104 Real-Time Library
n Experiment and Platform Manager for hardware management
Optional

n Microtec C Compiler (p. 98)
n CCPPPC
See p. 106
n PLATFORM_API
Hardware
Order Number
n CP1104
n Combined Connector/LED Panel (p. 346)
n CLP1104
n Adapter cable for DS1104
n ADP_CAB1104
Hardware
n Connector Panel (p. 346)
Engineering
Optional
n RTI
Software
Required
2015
343
Included
Application Fields
Block Diagram
PCI Bus / PCIe x 1 Bus
PC
Slave
DSP I/O
PWM
1 x 3-Phase
4 x 1-Phase
PCI Interface /
PCIe Interface
Interrupt Control
Unit
32 MB
SDRAM
Timers
TMS320F240
DSP
4 Capture
Inputs
Dual Port
RAM
Serial
peripheral
interface
Memory Controller
8 MB Flash
Memory
PowerPC 603e
Digital I/O
14 bits
24-bit I/O Bus
ADC
4 ch. 16-bit
4 ch. 12-bit
DAC
8 channels
16-bit
Master PPC I/O
344
Incr. Encoder
2 channels
Digital I/O
20 bits
Serial Interface
RS232/RS485/
RS422
DS1104
2015
Introduction
Induction Motor Control

Use Case
Determining Values
One of the boards incremental encoder interfaces picks up
the encoder signal of the motor, while two A/D converters
are required to analyze the motor currents. The controller
board calculates the control algorithm on the basis of the
measured values and determines the corresponding pulse
width modulation (PWM). The three-phase PWM signals are
generated on the boards DSP subsystem and determine the
converters output voltage and frequency.
Application Fields
Drive Control
In this use case, an induction motor controller is developed
with the DS1104. The DS1104 is well suited for drive control:
while in this use case the slave DSP system calculates the
PWM signals, the PowerPCs calculation power supports
convenient simulation. With an experiment software such
as ControlDesk Next Generation (p. 106), measuring and
parameterization can be performed during run-time.
Software
DS1104 R&D
Controller Board
Encoder Signal
6 PWM
Signals
Hardware
Ua
Ub
Uc
Engineering
Frequency
Converter
2015
345
AC
ia
SingleBoard Hardware / Connector and LED Panels
Connector and LED Panels

Easy access to I/O signals with BNC and SubD connectors
Highlights
n Access analog signals via BNC connectors
n Access digital signals via Sub-D connectors
Sub-D connectors are grouped according to I/O
n
channels or functional units
n LED panels indicate the status of the boards digital

signals
Connector Panel
Connector/LED Combi Panel

Width
Board
BNC Connectors
Sub-D Connectors
Width
DS1103 (p. 334)
n
20 ADC inputs
n
Digital I/O
14 MU
n
8 DAC outputs
n
Slave DSP I/O
1)
21 MU1)
n
Incremental encoder interfaces
n
CAN interface
n
Serial interfaces
DS1104 (p. 340)
n
8 ADC inputs
n
Digital I/O
n
8 DAC outputs
n
Slave DSP I/O
9 MU1)
14 MU1)
n
Incremental encoder interfaces
n
Serial interfaces
1)
MU = measurement unit (1.2 / 30.5 mm)
Order Information
346
Product
Order Number
Connector Panel for DS1103 PPC Controller Board
n
CP1103
Connector Panel for DS1104 R&D Controller Board
n
CP1104
Connector/LED Combi Panel for DS1103 PPC Controller Board
n
CLP1103
Connector/LED Combi Panel for DS1104 R&D Controller Board
n
CLP1104
2015
SingleBoard Hardware / Demo Equipment
Introduction
Demo Equipment
Hardware and software for demonstrating singleboard hardware
Application Fields
Highlights
VCFP Demo Equipment

n VCFP hardware
n MATLAB/Simulink demo controller for simulation
n Instrumentation panel
n Automation scripts
Hardware
Simulating a Positioning System

If you want to start controlling right after installing the
system, or if you are looking for an inexpensive, impossibleto-break way to close the loop in your students labs, the
VCFP demo is an attractive solution. The models dynamics
include an integrator, two first-order lag transfer functions,
and two resonances at 1.5 and 2 kHz.
Software
n For DS1103 PPC Controller Board and

n Simulation of a hard disks access arm
n Ideally suited to university labs

n Simulation of a 7th-order mechanical actuator
(voice-coil-driven flexible positioner, VCFP)
Product
Order Number
VCFP demo equipment
n
VCFP
Engineering
Order Information
Hardware
Required
Order Number
Cable to DS1103 PPC Controller Board or
n
VCFP_CAB1103
Cable to DS1104 R&D Controller Board
n
VCFP_CAB1104
DS1103 PPC Controller Board (p. 334) or
n
DS1103
n
DS1104
2015
347
Relevant Hardware
Modular Hardware / Introduction
Modular Hardware
Optimum scalability and flexibility for hardware that fits your project
Highlights
n Scalable hardware for applications like rapid control
prototyping and hardware-in-the-loop simulation
n High processing power
n High performance with multiprocessor systems
n Fast access to I/O hardware
n Variety of I/O boards available
n NEW: DS1007 PPC Processor Board
348
Key Benefits
Our modular hardware gives you optimum scalability and
flexibility. You can choose from our wide range of I/O boards
and processor boards to put together exactly the hardware
you need for your project. You can set up both singleprocessor and multiprocessor systems with a processor
board as a base, and then adapt the system to your tasks
by connecting I/O boards. The system can be expanded or
adapted to new projects at any time. The type and number
of I/O interfaces, the computing performance, and I/O
capabilities can easily be expanded by adding further boards
to the system.
Processor Boards
Processor boards (p. 349) are the basis of dSPACEs modular hardware. They give your system real-time calculation
power, and also provide the interfaces to the I/O boards
and to the host PC. The processor boards also do all the
communication with experiment tools running on the host
computer.
I/O Boards
The wide range of I/O boards (p. 350) features numerous
options, from simple signal input/output to complex signal
generation and interface support. Nearly all I/O boards can
be configured and programmed graphically using Simulink
and Real-Time Interface (RTI). For special I/O specifications,
which are not covered by our off-the-shelf boards, dSPACE
provides additional I/O solutions (p. 474).
Accessories
Accessories (p. 351) for our modular hardware will help you
complete your system. In addition to expansion boxes for
installing dSPACE systems, for use in either the laboratory
or a vehicle, there are also panels allowing easy access to
the signals from I/O boards.
2015
Introduction
Processor Boards
Application Fields

The DS1006 Processor Board (p. 356) is dSPACEs flagship
for high-end real-time applications. The DS1006 is an alternative heart for modular hardware, designed for calculating
complex, precisely detailed simulation models that require
enormous computing power. The processing power and I/O
capacity can be boosted even further by linking up to 20
DS1006 Processor Boards in a multiprocessor system (p. 349).

The DS1007 PPC Processor Board (p. 362) is designed for
applications which require a combination of high computing
power and fast closed-loop rates. It features a QorlQ P5020
dual-core processor running at 2 GHz.
The DS1007 offers an integrated, high-data-throughput Ethernet host interface for setting up modular systems without
additional host interface cards. The DS1007 is highly expandable. Its Ethernet I/O interface can be used for direct real-time
model access via the TCP/ IP or UDP/IP protocol and for bypassing.
The DS1007 also comes with a USB interface for long-term
data acquisition via a USB mass storage device.
Support for a multiprocessor system with several DS1007
boards is planned for the future.
Software
DS1005 PPC Board

The DS1005 PPC Board (p. 352) provides the computing
power for your real-time system and also functions as an
interface to the I/O boards and the host PC. It is equipped
with the 750GX PowerPC processor from IBM. The processing power and I/O capacity can be boosted even further by
linking up to 20 DS1005 PPC Boards in a multiprocessor
system (p. 349).
Choosing between DS1005, DS1006 and DS1007

This table gives you an impression of the three processor boards capabilities.
DS1006 Processor Board2)
n
For applications with very high I/O
n
For applications with moderate I/O
requirements (minimum latencies, high

reactivity)
n
For models with low complexity
DS1007 Processor Board3)
n
For applications with high I/O
requirements (moderate latencies, moderate
requirements (low latencies, high
reactivity)
reactivity)
n
For models with very high complexity
n
For models with high complexity
Hardware
Key Features
DS1005 PPC Board1)
1 GHz processor
2.8 GHz Quad-Core AMD Opteron processor
3)
QorlQ P5020 dual-core processor running at 2 GHz
1)
Up to 16 I/O boards
Up to 16 I/O boards
PHS bus
Gigalink
Module
Processor boards
Gigalink
Module
Further processor boards
(up to 20 in total)
Setting up multiprocessor systems.
2015
349
Multiplying Calculation Power

There might be some cases where a single processor system
is not sufficient, for example, when you calculate extremely
large real-time models, or if you require more than 16 I/O
boards. For the DS1005 and DS1006 you can reach any
performance and I/O capacity you need simply by expanding
your hardware with further processor boards. The processor
boards are connected via Gigalink Modules, which allow
high-speed serial data transmission via fiber-optic cable and
1.25 Gbit/s technology, and over distances exceeding 100
meters.
n Multiprocessor setup for the DS1005 (p. 352)
n Multiprocessor setup for the DS1006 (p. 356)
Engineering
2)
I/O Boards
Key Benefits
Modular hardware usually contains at least one I/O board for
connection to the real world.
To meet all the demands of rapid control prototyping and
hardware-in-the-loop simulation, dSPACEs wide range of
intelligent I/O boards features numerous options, from
simple signal input/output to complex signal generation and
Connector Panels for I/O Boards

With I/O boards, all I/O signals can usually be accessed at
the boards connectors. A more convenient solution is I/O
access via connector panels, which make the signals available in either a 19 rack or a desktop box. The panels are
I/O Bus (PHS bus)

Communication between processor board and I/O boards is
performed via the peripheral high-speed I/O bus (PHS bus).
The PHS bus provides several features that are essential for
real-time control systems: The I/O access times are guaranteed
because it is a single-master bus, and is always available for
I/O-to-processor communication. As the PHS bus is especially designed for real-time applications, there is no software
overhead caused by extensive transfer protocols.
interface support. If you cannot find the I/O board you need,
we also offer additional I/O solutions to fit your requirements.
n I/O boards overview (p. 350)
n Additional I/O solutions (p. 474)
n Engineering services (p. 580)
tailored to specific I/O boards, so that all the signals for

connection to the real world are at your disposal.
n Panels for I/O boards (p. 480)
n High-speed 32-bit bus between processor board and
I/O boards
n 20 MB/s peak transfer rate (higher for new I/O boards)
n Up to 16 I/O boards can be connected to one
processor board
n Up to 64 interrupts from up to 8 I/O boards can be
used, for example, from CAN messages, ECU inter

faces, serial interfaces.
Overview of I/O Boards

I/O Board
Details
Page
DS2002 Multi-Channel A/D Board
32 channels, resolution 4, 8, 12 or 16 bit, MUX, 2 ADCs
p. 366
32 channels, resolution 4, 8, 10, 12, 13, 14, 15 or 16 bit, MUX, 2 ADCs
p. 366
DS2004 High-Speed A/D Board
16 channels, resolution 16 bit, 16 independent ADCs, 800 ns conversion time
p. 372
DS2101 D/A Board
5 parallel D/A converters, resolution 12 bit, sample time 3.0 s
p. 375
DS2102 High-Resolution D/A Board
p. 375
DS2103 Multi-Channel D/A Board
p. 375
DS2202 HIL I/O Board
Signal conditioning for 12 V, 24 V, and 48 V automotive systems
p. 382
Central I/O board for hardware-in-the-loop simulation,16 x A/D, 20 x D/A
p. 386
DS2302 Direct Digital Synthesis Board
Real-time and high-accuracy signal generation, 6 x VC33 DSP and 16-bit DACs, 36 digital I/O
p. 392
DS2401 Resistive Sensor Simulation Board
Simulating resistive sensors, 4 resistance output channels (10 to 500 k)
p. 398
DS3001 Incremental Encoder Interface Board Precise position control, 5 incremental encoder interface channels (digital)
350
2015
p. 400
DS3002 Incremental Encoder Interface Board Precise position control, 6 incremental encoder interface channels (digital and analog)
p. 400
DS4002 Timing and Digital I/O Board
Generating and capturing digital signals, 8 timing channels, 200 ns resolution, 32 digital I/O
p. 404
96 digital I/O channels for various applications
p. 409
DS4004 HIL Digital I/O Board
96 bidirectional digital I/O channels with signal conditioning
p. 410
DS4121 ECU Interface Board
Connection of ECUs to a dSPACE system, 2 bypass interfaces
p. 412
DS4201 Prototyping Board
Integration of customized circuits
p. 416
DS4201-S Serial Interface Board
Communication between a dSPACE system and external devices, 4 RS232/RS422/RS485 channels
p. 417
DS4302 CAN Interface Board
Connection to CAN bus, 4 CAN channels
p. 418
DS4330 LIN Interface Board
Connection to LIN bus, 16 channels
p. 421
DS4505 Interface Board
Interface to FlexRay or (NEW) CAN FD communication bus
p. 424
DS5001 Digital Waveform Capture Board
Capturing of digital signals, 16 channels, resolution 25 ns
p. 428
DS5101 Digital Waveform Output Board
Generation of pulse patterns, 16 channels, resolution 25 ns
p. 432
SCRAMNet+ Interface
Connection to SCRAMNet+ networks
p. 442
PROFIBUS Interface
Connection to PROFIBUS systems
p. 444
Interface to MIL-STD 1553
Connection to MIL-STD-1553 networks
p. 446
ARINC 429 Interface
Connection to ARINC 429 bus
p. 448
ARINC 717 Interface
Connection to ARINC 717 bus
p. 450
FPGA Base Board
FPGA application-specific-programmable on a per project basis
p. 452
DS5203 FPGA Board
Completely user-programmable via RTI FPGA Programming Blockset
p. 438
High-precision capturing of 3-phase PWM signals
p. 454
Position Sensor Simulation Solution
p. 456
p. 460
EMH Solution
p. 464
Slave interface to an EtherCAT communication bus
p. 470
100 Mbit/s Ethernet Interface (UDP/IP, TCP/IP) Connection to an Ethernet network
p. 472
p. 474
Solutions for I/O and buses not covered by dSPACE standard boards. Examples: electrical failure
insertion, interfaces to Ethernet, VME, and resolvers
Application Fields
Page
Software
Details
Hardware
I/O Board
Introduction
DS830 MultiLink Panel

The DS830 MultiLink Panel gives you the option of controlling up to 16 dSPACE systems (expansion boxes, AutoBoxes, and MicroAutoBoxes1)) from one host PC.
n DS830 MultiLink Panel (p. 494)
AutoBoxes
AutoBox and Tandem-AutoBox are special expansion
boxes for in-vehicle applications.
n AutoBox/Tandem-AutoBox (p. 488)
DS802 PHS Link Board

The DS802 PHS Link Board enables developers to use I/O boards
in expansion boxes that do not have their own processor
boards, but utilize those in other expansion boxes instead.
n DS802 PHS Link Board (p. 492)
Does not apply to the MicroAutoBox II. The MicroAutoBox II offers an Ethernet host interface.
1)
2015
351
Expansion Boxes
Accessories for our modular hardware will help you complete your system. Our I/O boards can be inserted in expansion boxes with several ISA slots for up to 20 boards. The
boxes communicate with the host PC via ISA, PCI, PCI
Express, PCMCIA, ExpressCard or Ethernet connections.
n Expansion boxes (p. 484)
Engineering
Accessories
Modular Hardware / DS1005 PPC Board
DS1005 PPC Board

Computing power and scalability
Highlights
n PowerPC 750GX, 1 GHz
n Fully programmable from Simulink
n High-speed connection to all dSPACE I/O boards
via PHS bus
n Multiprocessor system of several DS1005 PPC Boards
via fiber-optic connection (Gigalinks)
352
Key Benefits
The DS1005 features a PowerPC 750GX processor running
at 1 GHz, so it has ample power for the vast majority of
cases. If you need even more calculation power, the DS1005
PPC Board meets all multiprocessing requirements.
The DS1005 is directly connectable to all dSPACE I/O boards
via PHS and PHS++ bus. The PHS++ bus standard is compatible with the standard PHS bus, but allows faster communication with I/O boards supporting PHS++ bus access, such
as the DS2211.
Modular Hardware Concept

The DS1005 PPC Board is one of dSPACEs processor boards
that form the core of dSPACEs modular hardware. Processor boards provide the computing power for your real-time
system and also function as interfaces to the I/O boards and
the host PC. The DS1005 is the board of choice for applications with high sampling rates and a lot of I/O capacity.
Great processor power plus fast access to I/O hardware with
minimum latencies make dSPACE processor boards considerably faster than solutions based on commonly available PCs.
Multiprocessor Setup
The processor board can be connected to other DS1005
boards via an additional optical interface (DS910 Gigalink
Module) to create DS1005 multiprocessor systems of all
sizes, so that your modular hardware can be tailored
exactly to your requirements. Synchronization between
the boards is ensured, since interrupts can be dispatched
to other DS1005 boards via hardware, with minimal
latencies.
Compatibility with Earlier Versions

The DS1005 (1 GHz) is compatible with all of its earlier
versions. Programs or models compiled for the older versions
run on the DS1005 (1 GHz) without modifications. Multiprocessor systems can mix old and new DS1005 boards
without impairing performance.
2015
Introduction
Technical Details
Parameter
Specification
Processor
n
IBM PowerPC 750GX, 1 GHz
n
Up to 4 instructions in parallel
n
32 KB L1 data cache
n
32 KB L1 instruction cache
n
1 MB L2 cache
Memory
Application Fields
n
Cache running at processor clock
n
128 MB SDRAM global main memory for host data exchange and application
n
16
MB flash memory for boot firmware and for user-specific applications, with flight
recorder functionality for data recording
n
Full host access to global memory
n
Timer
n
Synchronous time base unit (for multiprocessor systems)
n
Interrupt controller with up to 18 interrupt sources
Interfaces
Serial interface
n
RS232 interface with standard UART allowing transfer rates of up to 115.2 Kbaud
Connection to I/O boards
n
PHS++ bus Interface
n
32-bit I/O bus for modular I/O configuration (p. 350)
n
Peak transfer rate 20 MB/s, up to 30 MB/s for new I/O boards
Software
n
Up to 64 PHS bus interrupts
n
One full-size 16-bit ISA slot required
Host interface
n
Interface via eight 16-bit I/O ports (ISA bus)
n
Bidirectional interrupt line (PPC/host PC)
n
Plug & Play support
n
Building multiprocessor systems with further DS1005 PPC Boards
Multiprocessor systems
n
Up to 20 DS1005 PPC Boards
n
High-speed link via one DS910 Gigalink Module on each DS1005
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.59 in)
Ambient temperature
n
0 55 C (32 ... 131 F)
Cooling
n
Passive cooling
Power supply
n
+5 V 5%, 4 A (without DS910 Gigalink Module)
Hardware
n
Cable length of up to 100 m
n
+5 V 5%, 5.2 A (with DS910 Gigalink Module)
Order Number
n
DS1005

Software
Included
Order Number
n
C Real-Time Library
n
Experiment and Platform Manager
Required
Optional
n
RTI
n
Microtec C compiler for PowerPC (p. 98)
n
CCPPPC
n
Real-Time Interface for multiprocessor systems extension (p. 60)
n
RTI_MP
Hardware
Optional
n
Real-Time Interface (p. 54)
Order Number
n
PHS bus cable (with x connectors and terminator)
n
PHS-CABx
n
DS910 Gigalink Module
n
DS910
n
n
See p. 468
2015
353
Product
DS1005 PPC Board
Engineering
Order Information
Block Diagram
DS910 Gigalink
Module
Further
DS1005s
PowerPC
750 GX
64 MB
Global RAM
Global Bus
64 MB
Global RAM
I/O Boards
16 MB Boot
Flash
Local Bus
1 MB Level 2
Cache
PHS Bus
PHS-Bus
Interface
Supervisor
Interrupt
Controller
External
Timers
Peripheral Bus
Global Bus
Serial
Interface
Host
Interface
DS1005
ISA Bus
PC
Graphical Programming
Programming from MATLAB/Simulink/Stateflow
You can easily program the DS1005 PPC Board from Simulink via Real-Time Interface. A set of Simulink blocks gives
access to the entire range of dSPACE I/O Boards. Even
setting up multiprocessor systems is simple thanks to dedicated RTI-MP blocks.
354
Dialogs for altering simulation parameters such as solver

options and simulation time, and for generating C code,
are directly accessible from the Simulink environment.
2015
Introduction
Multiprocessor Setup via DS910 Gigalink Module
Application Fields
Gigalink Modules
All variants of the DS1005 PPC Boards are connected via
optional Gigalink modules, which allow high-speed serial
data transmission via fiber-optic cable and 1.25Gbit/s technology. You can connect up to 20 processor boards in a
system, and over distances up to 100meters, in this way.
The fiber-optic connectors of the Gigalink modules are
pluggable, making it easy to replace them yourself.
Software
Expanding Processor Power

With modular hardware based on the DS1005 PPC Board,
you can reach any performance you need simply by expanding your hardware with further DS1005 boards. Tasks can
be shared between the processor boards to attain optimum
response times and performance. And what is more, you
automatically increase the I/O capacity of your system.
Parameter
Specification
General
n
Hardware extension to DS1005 PPC Board for building multiprocessor systems
Hardware
Technical Details DS910 Gigalink Module
n
Requires several DS1005 PPC Boards (1 GHz, 933MHz, 800MHz, or 480MHz variant), each with
a DS910 Gigalink Module

n
Gross transfer rate: 1.25 Gbit/s
n
Distance up to 100m
optical, high-speed communication ports (Gigalinks), each providing 16 bidirectional interrupt lines
and 16 bidirectional data channels (2 kilowords width on each channel)
n
The fiber-optic connectors are pluggable, making it easy to replace them yourself. Substitute connectors
are available only from dSPACE (order number: SFP_TRANS_MOD).
n
I/O access speed of send operations adapted to Gigalinks capabilities: Data is sent directly without
a FIFO buffer
n
32-bit or 64-bit read/write operations allowed: 32-bit access for single 32-bit (or shorter) data words,
fast 64-bit access for block transfer functions wherever possible
n
Real-time interrupt dispatching
n
Passive cooling
2015
Engineering
n
4
355
Hardware details
Modular Hardware / DS1006 Processor Board

Computing power for processingintensive realtime models
Highlights
n x86 processor technology
n Quad-Core AMD Opteron processor
n High-speed connection to all dSPACE I/O boards
via PHS bus

n Multiprocessor system of several DS1006 Processor
Boards via fiber-optic connection (Gigalinks)
Key Benefits
The DS1006 processor board is our flagship for very complex, large, and processing-intensive models for example,
for powertrain and virtual vehicle simulations. The board is
built around the AMD Opteron, x86-compatible 64-bit
server multi-core processor. It provides 512 kB L2 cache per
core and 6 MB shared L3 cache. The DS1006 also has 1 GB
Modular Hardware Concept

The DS1006 Processor Board is one of dSPACEs processor
boards that form the heart of dSPACEs modular hardware
(the other being the DS1005 PPC Board). It provides the
computing power for your real-time system and also functions as an interface to the I/O boards and the host PC. The
DS1006 is directly connectable to all dSPACE I/O boards via
PHS bus.
Multi-Core Processor for More Computing Power

You can set up a multi-processor system by using the individual cores of the multi-core processor, and assign the I/O
boards easily by graphical programming via RTI-MP (p. 60).
356
local memory for executing real-time models, 128 MB

global memory per core for exchanging data with the host
PC, and 2 MB on-board boot flash memory, plus an optional application flash memory on a CompactFlash card for
automatic, host-independent booting of real-time applications.
Multiprocessor Setup
If you need even more performance, you can build a multiprocessor system by connecting several DS1006 boards via
an additional optical interface (DS911 Gigalink Module,
p. 361). Synchronization between the boards is guaranteed,
since interrupts can be sent to other processor boards via
hardware, with minimal latencies.
With the possibility for parallel computing and a high performance data exchange between the cores, the DS1006
multi-core board speeds up all your applications (p. 359).
2015
Introduction
Technical Details
Parameter
Specification
Processor
n
Quad-Core AMD Opteron processor, 2.8 GHz
n
4 x 64 kB L1 data cache, 4 x 64 kB L1 instruction cache, 4 x 512 kB L2 cache, 6 MB L3 cache
n
1 GB DDR2-800 SDRAM local memory for the application and dynamic application data
Memory
n
4 x 128 MB DDR2-267 SDRAM global memory for host data exchange
n
2 MB on-board boot flash memory for boot firmware
Application Fields
n
Application flash memory on CompactFlash card (accessable via ControlDesk). The capacity
depends on the card.

n
For each core: 3 general-purpose timers
Timer
n
Synchronous time base unit (STBU) for multiprocessor systems
n
For each core: one interrupt controller with 18 different interrupt sources
n
The
interrupt sources of the connected I/O boards can be handled from each core via internal
Gigalinks.
Interfaces
Serial interface
n
n
PHS++ bus interface
n
32-bit I/O bus for modular I/O configuration (p. 350)
n
Software
n
n
One full-size 16-bit ISA slot required
Host interface
n
Interface via eight 16-bit I/O ports (ISA bus)
n
Building multiprocessor systems with further DS1006 Processor Boards
Multiprocessor system
n
Up to 20 DS1006 Processor Boards
n
Up to 4 high-speed links via one DS911 Gigalink Module on each DS1006
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in)
Ambient temperature
n
0 ... 40 C (32 ... 104 F)
Cooling
n
Active cooling (fan)
Power supply
n
ISA bus:
Hardware
n
Possible cable length of up to 100 m
n
+5 V 5%, 2.0 A (without DS911)
n
+5 V 5%, 3.0 A (with DS911 as of module revision 2.0)
n
+12 V 5%, 1.5 A
n
CPU power connector: +5 V 5%, 20 A
Order Information
Order Number
n
DS1006
2015
357
Engineering
Product

Software
Order Number
Included
n
C Real-Time Library
n
Required
Optional
n
n
RTI
n
GNU C compiler for AMD Opteron
n
DS1006_COMP
n
Real-Time Interface for multiprocessor systems extension (p. 60)
n
RTI_MP
n
DS1006 Ethernet Blockset (p. 88)
Hardware
Order Number
Required
n
For safety reasons DS1006 Processor Boards must be used only in
Optional
n
PHS bus cable (with x connectors and terminator)
n
PHS-CABx
n
DS911 Gigalink Module
n
DS911
n
n
See p. 492
n
DS921 (Connector bracket for Ethernet connection)
n
See p. 475
For detailed information about Expansion

PX10 and PX20 Expansion Boxes with hardware revisions certified Boxes, please contact dSPACE.
for DS1006 Processor Boards. (May require an Expansion Box update.)
Block Diagram
DS911 Gigalink
module
1 ... 4
Further
DS1006s
Firmware
flash
PHS bus
I/O boards
1024 MB
local RAM
Compact
Flash
AMD
OpteronTM
(Quad-Core)
Chipset
..
128 MB
global RAM
Bus arbiter
External
Timers
PHS-bus
interface
..
Host
Interface
Peripheral bus (32 bit)
..
Interrupt
Controller
Watchdog
..
..
Internal
Gigalink
connection
Timer A (32 bit)

Timer B (32 bit)
Timer C (64 bit)
DS1006
ISA bus
358
PC
2015
Introduction
Hardware
Software
Application Fields
Programming from
MATLAB/Simulink/Stateflow
You can easily program the DS1006 Processor Board from
Simulink via Real-Time Interface (RTI, p. 54). Simulink blocks
provide access to the entire range of dSPACE I/O boards.
The setting up of multiprocessor systems as well as the
configuration of the data transfer between the processor
cores is simple thanks to dedicated RTI blocks (RTI-MP,
p. 60).
Dialogs for altering simulation parameters (such as solver
options or the simulation time) and for generating C code,
are directly accessible from the Simulink environment.
Speed Information
Mean Turnaround Time
n
0.11 ms
n
ASM Vehicle Dynamics Simulation Package (including Brake Hydraulics Model) (p. 251)
n
0.14 ms
Performance of the DS1006 Processor Board Using

More Than One Core with Connections via Gigalinks
For this benchmark, ASM Virtual Vehicle with two main
model components (Gasoline Engine Basic, Vehicle Dynamics) with I/O and CAN restbus simulation is calculated on
different cores with connections to each other via internal
Gigalinks; two DS2211 HIL I/O Boards are connected to the
PHS bus of one DS1006 Processor Board:
ASM Main Model Component
n
Gasoline Engine Basic
n
0.16 ms
n
Vehicle Dynamics
n
0.20 ms
For comparison: the same model with external Gigalinks

and the predecessor DS1006 Processor Board (single-core
2015
359
ASM Package (including I/O and CAN Restbus Simulation)

n
ASM Gasoline Engine Basic Simulation Package (p. 241)
Engineering
Performance of the DS1006 Processor Board Using One Core
processor with 2.6 GHz). Two DS1006 Processor boards are

used with one DS2211 HIL I/O Board connected to each:
n
Gasoline Engine Basic
n
0.17 ms
n
Vehicle Dynamics
n
0.22 ms
Performance of the DS1006 Processor Board Using

More Than One Core (Without Connected I/O Boards)
The following benchmark without any connected I/O
demonstrates the different performance of external and
internal Gigalink connections: ASM Virtual Vehicle with
three main model components (Drivetrain, Gasoline Engine,
Vehicle Dynamics) is calculated on different cores connected
to each other via internal Gigalinks.
For comparison: the same model with external Gigalinks

and the predecessor DS1006 Processor Board. ASM Virtual
Vehicle with main model components (Drivetrain, Gasoline
Engine, VehicleDynamics) is calculated on different DS1006s
(predecessor DS1006 with 2.6 GHz single core processor)
connected to each other via external Gigalinks.

(without I/O)

(without I/O)
n
Drivetrain
n
17.2 s
n
Drivetrain
n
43.7 s
n
Gasoline Engine
n
36.1 s
n
Gasoline Engine
n
66.5 s
n
Vehicle Dynamics
n
91.3 s
n
Vehicle Dynamics
n
140.9 s
These benchmarks are only examples that give an idea of

the performance achievable by the DS1006 Processor Board.
The turnaround time of an application depends on a large
number of factors, such as:
n The application size compared to the cache size of the
processor
n The amount of I/O at each PHS-bus, because of additional time needed for communication via PHS bus
n The number of signals that have to be sent via
Gigalink connections (external or internal)
360
Comparison of both Measurements

Because the I/O communication is split into two PHS buses
in the second benchmark, it might be expected to be faster
than the first one. But the better performance of the
internal Gigalink connections used in the first benchmark
outweigh the disadvantage of having only one PHS bus.
It might be better to use more than one DS1006 Processor
Board in other cases (e.g., with very high I/O communication
at each main model component).
n The way the model is divided into parts that can be
calculated in parallel
For applications with tough requirements on I/O latencies,
please note that the DS1006 Processor Board with the
Quad-Core processor has to access all connected I/O boards
via one PHS bus.
2015
Introduction
Multiprocessor Setup via DS911 Gigalink Module
Application Fields
Gigalink Modules
The DS1006 Processor Boards are connected via optional
Gigalink modules, which allow high-speed serial data transmission via fiber-optic cable and 1.25Gbit/s technology.
You can connect up to 20 processor boards in a system, and
over distances up to 100meters, in this way.
The fiber-optic connectors of the Gigalink modules are
pluggable, making it easy to replace them yourself.
Hardware
Software
Expanding Processor Power

With modular hardware based on the DS1006 Processor
Board, you can achieve any performance you need simply
by expanding your hardware with further DS1006 boards.
Tasks can be shared between the processor boards to attain
optimum response times and performance.
What is more, this automatically increases the I/O capacity
of your system.
Technical Details DS911 Gigalink Module

Parameter
Specification
General
n
Hardware extension to DS1006 Processor Board for building multiprocessor systems
n
Requires several DS1006 Processor Boards, each with a DS911 Gigalink Module
n
Gross transfer rate: 1.25 Gbit/s
n
Distance up to 100m
n
4 optical, high-speed communication ports (Gigalinks), each providing 16 bidirectional interrupt lines and
Engineering
Hardware details
16 bidirectional data channels (2 kilowords width on each channel)

n
The fiber-optic connectors are pluggable, making it easy to replace them yourself. Substitute connectors
are available only from dSPACE (order number: SFP_TRANS_MOD).

n
I/O access speed of send operations adapted to Gigalinks capabilities: Data is sent directly without
a FIFO buffer
n
32-bit or 64-bit read/write operations allowed: 32-bit access for single 32-bit (or shorter) data words,
fast 64-bit access for block transfer functions wherever possible

n
Passive cooling
2015
361
n
Real-time interrupt dispatching
Modular Hardware / DS1007 PPC Processor Board

Computing power and small I/O latencies
Highlights
n Freescale QorlQ P5020, dual-core, 2 GHz
n Integrated Ethernet host interface for high data
throughput
n Ethernet I/O interface for real-time connection of
sensors and devices via TCP/IP and UDP/IP protocols
n USB interface for data logging via USB mass storage
device
362
Application Areas
The DS1007 PPC Processor Board is one of dSPACEs processor boards that form the core of dSPACEs modular hardware. The DS1007 is an excellent fit when your application
models require a combination of high computing power
and fast closed-loop rates (e.g., for electric motor control,
advanced driver assistance systems or active noise and vibration cancellation).
Key Benefits
As the successor of the DS1005, the DS1007 features a
QorlQ P5020 dual-core processor running at 2 GHz. The
DS1007 offers an integrated, high-data-throughput Ethernet host interface for setting up modular systems without
additional host interface cards.
The DS1007 is highly expandable. Its Ethernet I/O interface
can be used for direct real-time model access via the TCP/
IP or UDP/IP protocol and for bypassing. USB mass storage
devices can be connected for long-term data logging via
the integrated USB interface.
Dual-Core Processor for More Computing Power

You can set up a multicore system by using the individual
cores of the dual-core processor and easily assign the I/O
boards by graphical programming via RTI-MP. The DS1007
dual-core board speeds up all your applications with parallel computing and high-performance data exchange between the cores.
Support for a multiprocessor setup with several DS1007
boards is planned for the future.
Upgrading from DS1005 to DS1007

Because the DS1007 only requires one slot, it is not necessary to change existing DS1005-based setups when upgrading from DS1005 to DS1007. All I/O boards can be used as
before.
2015
Introduction
Technical Details
Parameter
Specification
Processor
Real-time processor
n
Freescale QorlQ P5020, dual-core, 2 GHz
n
32 KB L1 data cache per core, 32 KB L1 instruction cache per core, 512 KB L2 cache per core,
2 MB L3 cache total
Host communication
coprocessor
n
Freescale QorlQ P1011 800 MHz for communication with host PC
Application Fields
n
1 GB DRAM
Memory
n
128 MB flash memory
n
Each core has 3 general-purpose timers
Timer
n
Synchronous time base unit (for multiprocessor systems)
n
Each core has one interrupt controller with full and independent access to all real-time events
n
Additional interprocessor interrupts and messages via internal Gigalinks
Interfaces
Serial interface
n
Ethernet interfaces
n
Integrated low-latency Gigabit Ethernet I/O interface
USB interface
n
USB 2.0 interface for data logging via USB mass storage device (requires a separate license)
n
PHS++ bus Interface
n
32-bit I/O bus for modular I/O configuration
Software
n
n
n
Integrated Gigabit Ethernet host interface
Host interface
Physical size
n
340 x 125 x 19 mm (13.4 x 4.9 x 0.75 in)
Ambient temperature
n
0 ... 55 C (32 ... 131 F)
Cooling
n
Active cooling via fan
Power supply
n
+5 V 5%, 9 A
2015
363
Engineering
Hardware
n
+12 V 5%, 0.8 A
Order Information
Product
Order Number
DS1007 PPC Processor Board
n
DS1007

Software
Included
Order Number
n
C Real-Time Library
n
Required
Optional
n
RTI
n
GNU C Compiler for PowerPC
n
DS1007_COMP
n
For multi-core applications: Real-Time Interface for multiprocessor systems extension (p. 60)
n
RTI_MP
n
n
RTI_ETH_BS
n
RTI USB Flight Recorder Blockset
n
RTI_USB_FR_BS
Hardware
Optional
364
n
Order Number
n
PHS bus cable (with x connectors and terminators)
n
PHS-CABx
n
n
See p. 492
n
DS1007 RS232 bracket (requires an additional slot)
n
DS1007_RS232
2015
Introduction
Block Diagram
PHS-bus
interface
Real-time
processor
(P5020)
RAM
256MB
Flash
64MB
Interrupt
controller
Host
communication
coprocessor
(P1011)
Ethernet
switch
Real-time
clock (RTC)
Local bus
Flash
128MB
Timer A (32 bit)

Timer B (32 bit)
Timer D (32 bit)
Internal
Gigalink
connection
USB 2.0
Software
RAM
2 x 512MB
I/O boards
Application Fields
PHS bus
I/O boards
UART
DS1007
Ethernet
PC
RS232
2015
365
Engineering
Hardware
ECU
Modular Hardware / DS2002/DS2003 A/D Boards
DS2002/DS2003 A/D Boards

Highresolution A/D boards
Highlights
A/D boards with various resolutions, channel numbers
and speeds
n Up to 32 channels
n Resolution up to 16 bit
n Sample times 3.9 - 5.6 s (16 bit)
n
Application Areas
A/D conversion is an element of most applications in rapid
control prototyping and hardware-in-the-loop (HIL) simulation. In rapid control prototyping, sensors for pressure,
temperature, or other signals provide analog voltages or
currents. In HIL simulations, the electronic control unit provides analog voltages or currents that control the simulated
actuators.
Key Benefits
The A/D boards provide various channel numbers, resolutions, and speeds for you to choose from. The table below
gives you an initial overview. The boards can be configured
from Simulink using Real-Time Interface (p. 54). You can
select the voltage range and the resolution separately for
each channel or A/D converter.
Comparing the Boards

Sample Time1)
(All Channels)
4, 8, 12, 16 bit,
shortcycling
3.9 s (16 bit)
66.9 s (16 bit)
4, 8, 10, 12, 13, 14, 15,

16 bit, shortcycling
5.6 s (16 bit)
56.6 s (16 bit)
Channels
Resolution
DS2002
MultiChannel A/D Board
32 in
DS2003
MultiChannel A/D Board
32 in
1)
366
Sample Time1)
(2 Channels)
Board
Speed and timing specifications describe the capabilities of the hardware components and circuits of dSPACE products. Depending on the
software complexity the attainable overall performance can deviate significantly from the hardware specification.
2015
Introduction

Technical Details
Parameter
Specification
General
n
32 A/D input channels (single-ended)
n
2 independent A/D converters with separate sample & hold (S/H), 16 multiplexed inputs each
n
Hold mode
Application Fields
n
4-, 8-,12- or 16-bit resolution (programmable)
Conversion time1)
n
1.5, 2.0, 2.5, 3.0 s (resolution-dependent)
S/H acquisition time
n
0.9 s to 0.01% of FSR (full-scale range)
Multiplexer settling time
n
1.2 s to 0.01% of FSR
Offset error
n
2.0 mV
Gain error
n
0.2% of FSR
Offset drift
n
4 ppm of FSR/K
Gain drift
n
25 ppm of FSR/K
Linearity error
n
0.003% of FSR
Differential linearity error
n
0.002% of FSR
Missing codes
n
No missing codes at 14-bit resolution
SNR (signal-to-noise ratio)
n
78 dB
Channel crosstalk
n
-75 dB (at 10 kHz signal frequency)
Input impedance
n
1 M
Input overvoltage protection
n
Up to 15 V
Warm-up time
n
2 min.
n
2 interrupts on end of A/D conversion (one for each A/D converter)
Sampling
n
By software from processor board
Software
n
5 V or 10 V input voltage range (programmable)
A/D channels1), 2)
n
Simultaneous
Host interface
Physical
characteristics
Hardware
n
50-pin male Sub-D input connector
Physical connections
n
One 8- or 16-bit ISA slot (power supply only)
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in)
Ambient temperature
n
0 70 C (32 158 F)
Power supply
n
+5 V 5%, 2.5 A
n
+12 V 5%, 200 mA
n
-12 V 5%, 130 mA
1)
Engineering
2)
Typical values at 25 C, 16-bit resolution and 10 V input voltage range (FSR = full-scale range).
Order Information
Product
Order Number
n
DS2002
Software
Required
Order Number
n
Hardware
Optional
n
RTI
Order Number
n
Connector Panel for DS2002 (p. 480)
n
CP2002
2015
367

Technical Details
Parameter
Specification
General
n
32 A/D input channels (single-ended)
n
2 independent A/D converters
n
Simultaneous sample-and-hold (S/H)
n
Hold mode
n
4-, 8-,10-, 12-, 13-, 14-, 15- or 16-bit resolution (programmable separately for each channel pair)
n
5 V or 10 V input voltage range (programmable)
n
1 external trigger input line
A/D Channels1), 2)
Conversion time1)
n
1.4 ... 3.0 s (resolution-dependent)
S/H acquisition time
n
1 s to 0.01% of FSR (full-scale range)
Hold step time
n
1.6 s to 0.01% of FSR
Multiplexer settling time
n
400 ns
Offset error
n 2.5 mV
Gain error
n
0.2% of FSR
Offset drift
n
10 ppm of FSR/K
Gain drift
n
35 ppm of FSR/K
Linearity error
n
0.006% of FSR
n
0.002% of FSR
Missing codes
n
SNR (signal-to-noise ratio)
n
78 dB
Adjacent channel crosstalk
n
-80 dB
Static crosstalk
n
-80 dB (at 10 kHz signal frequency)
Dynamic crosstalk
n
-110 dB
Input impedance
n
1 M
n
Protection up to 15 V
Warm-up time
n
10 min.
n
Scan process complete
n
A/D converter data buffer: not empty, half full, full
n
By software from processor board
Sampling
n
By external signal
n
Simultaneous
n
Host interface
Physical
characteristics
n
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in)
Ambient temperature
n
0 70 C (32 158 F)
Power supply
n
+12 V 5%, 350 mA
n
-12 V 5%, 280 mA
n
+5 V 5%, 1.5 A
2)
1)
368
2015
Introduction
Order Information
Product
Order Number
n DS2003
Software
Application Fields

Order Number
Required
n Real-Time Interface (p. 54)
n RTI
Hardware
Order Number
n Connector Panel for DS2003 (p. 480)
PHS Bus
n
CP2003
Processor
Board
I/O Boards
Software
Optional
Block Diagram for DS2002

Multi-Channel A/D Board
PHS-Bus
Interface
Hardware
Barrel
Shifter
A/D 2
A/D 1
Setup
Register
Power
Supply
Interrupt
Controller
Channels
17 ... 32
Short
Cycle
16-bit ADC
Range
Select
S/H
16 to 1
MUX
Channels
1 ... 16
Start of
Conversion
Generator
Engineering
Power
Supply
DS2002
ISA Bus
PC
2015
369
Channel
Select
Register

Multi-Channel A/D Board
Processor
Board
PHS Bus
PHS-Bus
Interface
I/O Boards
Control
Ext. trigger
Start
Scanning
Register
A/D 2
A/D 1
Scan
Table
Buffer
Power
Supply
Short
Cycle
16-bit ADC
Range
Select
32 to 1
MUX
Channels
1 ... 32
S/H
Setup
Register
Power
Supply
Interrupt
Controller
DS2003
ISA Bus
370
PC
2015
Introduction
2015
371
Engineering
Hardware
Software
Application Fields

The Real-Time Interface (RTI) board libraries for
the A/D boards provide blocks that implement
the functionality and I/O capabilities of the
boards in Simulink models. The RTI blocks can
be added to a Simulink model via drag & drop.
The blocks can be configured using the setup
mask of the related block.
Modular Hardware / DS2004 HighSpeed A/D Board
DS2004 HighSpeed A/D Board

Fast and precise A/D board
Highlights
n 16 high-speed A/D channels with high accuracy
n 4 external trigger inputs and extensive trigger
functions
n Single and burst conversion mode
Key Benefits
Each of the DS2004s 16 channels has an independent
A/D converter with a resolution of 16 bits and differential
inputs. The conversion time is 800 ns per channel. The measurement modes plus 4 external trigger inputs and extensive
trigger functions enable the conversion of both single measurement values and whole sample bursts. The board buffers
up to 16,384 values per channel and then transfers them to
the processor board as a burst. This reduces the communication overhead and improves the overall system performance.
Application Areas
The DS2004s triggered sample mode can be used to record
data within a defined window based on trigger events. For
example, angle-synchronous measurements of a combustion
engine can be started by an external software trigger.
Possible applications include cylinder pressure-based control
and the measurement of knock signals in an angle window.
Two Burst Modes

The DS2004s burst mode offers two ways of converting
measurement values:
n Continuous sample mode: When one burst of
conversions ends, the next burst starts automatically.
The conversion of individual measurement values
within a burst is triggered by software, an internal
timer, or an external trigger.
n Triggered sample mode: A burst of conversions can
be started by software or a trigger event.

The Real-Time Interface (RTI) libraries for the A/D board
provide RTI blocks that allow you to implement the functionality and I/O capabilities of the board in Simulink models.
The RTI blocks can be added to a Simulink model via
drag & drop.
372
2015
Introduction
Modular Hardware / DS2004 High-Speed A/D Board
Technical Details
Parameter
Specification
General
n
16 A/D input channels (differential)
n
16 independent A/D converters
n
16-bit resolution
n
0.8s ... 1s trigger interval (adjustable)
n
5 V or 10 V input voltage range (programmable for each channel)
Application Fields
n
12 V input voltage working range
n
4 external trigger input lines
A/D Channels1), 2)
Conversion time
n
800 ns
Initial offset error
n
1 mV
Initial gain error
n
0.1% of FSR
Input offset drift
n
2 ppm of FSR/K
Gain drift
n
20 ppm of FSR/K
Linearity error
n
0.003% of FSR
n
0.003% of FSR
Missing codes
n
SNR (signal-to-noise-ratio)
n
+85 dB (at 10 kHz, 10 V range)
Software
n
+83 dB (at 10 kHz, 5 V range)
THD (total harmonic distortion)
n
-85 dB (at 10 kHz, 10 V range)
n
-83 dB (at 10 kHz, 5 V range)
Channel crosstalk
n
-95 dB
CMRR (common mode rejection ratio) n

+85 dB (at 10 kHz signal frequency)
Input impedance
n
1 M
n
50 V continuous, 60 V for up to 10 s
n
Burst start
n
Data ready
n
Data lost
Input voltage
n
CMOS level
n
50 V continuous, 60 V for 10 s
Host interface
Physical
Characteristics
Hardware
n
Conversion trigger overflow
External trigger
input
n
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in)
Ambient temperature
n
0 55 C (32 131 F)
Power supply
n
+5 V 5%, max. 1.5 A
n
+12 V 10%, 1.5 A
2)
Order Information
Product
Order Number
n
DS2004

Software
Required
Order Number
n
Hardware
Optional
n
RTI
Order Number
n
n
CP2004
2015
373
Engineering
1)
Modular Hardware / DS2004 High-Speed A/D Board
Block Diagram
Processor
board
PHS bus
I/O boards
...
PHS-bus
interface
16
1
Swinging buffer
Free buffer
Free buffer
Write buffer
Buffer
control unit
IRQ controller
A/D converter
unit
Differential
input
Signal
conditioning
External trigger 1
.
.
.
External trigger 4
Trigger
unit
ADC
timer
Power supply
DS2004
ISA bus
374
PC
2015
Modular Hardware / DS2101/DS2102/DS2103 D/A Boards
Introduction
DS2101/DS2102/DS2103 D/A Boards

Fast D/A boards
Application Fields
Highlights
D/A boards with various resolutions, channel
numbers, and speeds
n Up to 32 channels
n Resolution up to 16 bit
n Minimum settling time of 1.6 s
n
Key Benefits
The D/A boards provide various channel numbers, resolutions, and speeds for you to choose from. The table below
gives you an initial overview. All three boards can be configured from Simulink with Real-Time Interface. You can
select the voltage range for each channel individually.
Hardware
Application Areas
D/A conversion is required by many rapid control prototyping applications to provide the control signal for actuators.
In the other direction, in hardware-in-the-loop applications,
sensors that provide analog signals have to be simulated.
Software
Comparing All Three Boards

Channels
Resolution
Sample Time 1)
DS2101 D/A Board
5 out
12 bit
3.0 s
DS2102 HighResolution D/A Board
6 out
16 bit
1.6 s
DS2103 MultiChannel D/A Board
32 out
14 bit
10.0 s
2015
Engineering
1)
375
Board
DS2101 D/A Board

Technical Details
Parameter
Specification
General
n
5 parallel D/A converters
n
12-bit resolution
n
5 V, 10 V or 0 ... +10 V output voltage range (programmable)
n
Reset to 0V on I/O error (programmable)
D/A channels1), 2)
Settling time
n
3 s typ. (4 s max.) to 0.01% of FSR (full-scale range)
n
1 s typ. at major carry
Output current
n
5 mA max.
Output impedance
n
0.3
Offset error
n
< 3 mV
Gain error
n
< 0.1 %
Offset drift
n
10 ppm of FSR/K
Gain drift
n
30 ppm of FSR/K
Linearity error
n
1/2 LSB
n
3/4 LSB
Monotonicity
n
Fully monotonic
Triggering
n
By software from the processor board
n
Immediate output or simultaneous output
n
25-pin female Sub-D output connector
Host interface
n
Physical
characteristics
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in)
Ambient temperature
n
0 ... 70 C (32 ... 158 F)
Power supply
n
+5 V 5%, 2.25 A
2)
Typical values at 25 C and 10 V output voltage range (FSR = full-scale range).
1)
Order Information
Product
Order Number
DS2101 D/A Board
n
DS2101

Software
Required
Order Number
n
Hardware
Optional
376
n
RTI
Order Number
n
n
CP2101
2015
Introduction

Technical Details
Parameter
Specification
General
n
n
16-bit resolution
Output current
n
Reset to 0 V on I/O error (programmable)
Board revisions DS2102-01 DS2102-043):
n
Deglitcher disabled: 1.3 s to 0.025% of FSR (full-scale range)
n
Deglitcher enabled: 2 s to 0.025% of FSR
Board revision DS2102-053):
n
1.6 s to 0.025% of FSR
n
5 mA max.
Offset error
n
1 mV
Gain error
n
0.05%
Offset drift
n
14 ppm of FSR/K
Gain drift
n
25 ppm of FSR/K
Linearity error
n
2 LSB
n
4 LSB
Monotonicity
n
14 bits
n
-90 dB (at 10 KHz)
Settling time
Triggering
Software
D/A channels1), 2)
Application Fields
n
5 V, 10 V or 0 ... +10 V output voltage range (programmable)
n
n
Immediate output or simultaneous output
n
n
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in)
Ambient temperature
n
0 ... 70 C (32 ... 158 F)
Power supply
n
+5 V 5%, 3.3 A (DS2102-01 ... DS2102-04)
Hardware
Host interface
Physical
characteristics
n
+5 V 5%, 1.6 A (DS2102-05)
n
12 V 5%, 50 mA
Typical values at 25 C and 10 V output voltage range.

2)
3)
Up to board revision DS2102-04, deglitchers are available that you can enable/disable via software (RTI or RTLib). As of board revision DS210205, the DS2102 uses D/A converters with reduced output spikes.
1)
Product
Order Number
n
DS2102
Engineering
Order Information
Required
Order Number
n
Hardware
Optional
n
RTI
Order Number
n
n
CP2102
2015
377
Software

Technical Details
Parameter
Specification
General
n
n
14-bit resolution
n
5 V or 10 V ouput voltage range (programmable)
n
Reset to 0V on I/O error (programmable)
D/A channels1), 2)
Settling time
n
10 s to 0.012% of FSR (full-scale range)
Output current
n
5 mA max.
Offset error
n
1 mV
Gain error
n
0.2% of FSR
Offset drift
n
10 ppm of FSR/K
Gain drift
n
10 ppm of FSR/K
n
1 LSB
Monotonicity
n
14 bits
n
-92 dB (at 10 kHz)
Triggering
n
n
Immediate output or simultaneous update in groups of four channels
Host interface
Physical
Physical size
characteristics
Ambient temperature
Power supply
n
n
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in)
n
0 ... 70 C (32 ... 158 F)
n
+5 V 5%, 3.0 A
n
12 V 5%, 50 mA
1)
2)
Typical values at 25 C and 10 V output voltage range.

Order Information
Product
Order Number
n
DS2103

Software
Required
Order Number
n
Hardware
Optional
378
n
RTI
Order Number
n
n
CP2103
2015
PHS Bus
PHS-Bus
Interface
I/O Boards
D/A 5
D/A 4
D/A 3
D/A 2
D/A 1
Setup
Register

D/A Board
Application Fields
Processor
Board
Introduction
Ch. 5
Ch. 4
Ch. 3
Ch. 2
Auto-Zero
Circuit
12-bit DAC
Range
Select
Ch. 1
Power
Supply
PC
ISA Bus
Processor
Board

High-Resolution D/A Board
I/O Boards
Calibration
Hardware
PHS Bus
PHS-Bus
Interface
Software
DS2101
D/A 6
D/A 5
D/A 4
D/A 3
D/A 2
D/A 1
Setup
Register
Ch. 6
Ch. 5
Ch. 4
Ch. 3
EEPROM DAC
16-bit DAC
Ch. 2
Range
Select
Ch. 1
Engineering
Auto-Zero
Circuit
Power
Supply
DS2102
PC
2015
379
ISA Bus

Multi-Channel D/A Board
Processor
Board
PHS Bus
PHS-Bus
Interface
I/O Boards
D/A 8
D/A 7
D/A 6
D/A 5
D/A 4
D/A 3
D/A 2
Scan
Table
D/A 1
Range
Register
Strobe
Register
14-bit
DAC
14-bit
DAC
14-bit
DAC
14-bit
DAC
17...20
13...16
1...4
DS2103
380
21...24
5...8
Power
Supply
ISA Bus
29...32
25...28
9...12
Mode
Register
Auto-Zero
Circuit
Channels
PC
2015
Introduction
Application Fields
blocks can be added to a Simulink model via drag & drop.

The blocks can be configured using their setup masks.
2015
381
Engineering
Hardware
Software

The Real-Time Interface (RTI) board libraries for the D/A
boards provide blocks that implement the functionality and
I/O capabilities of the boards in Simulink models. The RTI
Modular Hardware / DS2202 HIL I/O Board

I/O hardware with signal conditioning for 12 V, 24 V, and 48 V automotive systems
Highlights
n Ideally suited to body electronics, transmission,
and component tests
n Lower-cost alternative to DS2211 HIL I/O Board,
without signal processor and angular processing unit
n High number of analog and digital channels
n Supports 2-voltage systems
Key Benefits
The DS2202 HIL I/O Board has been designed for hardwarein-the-loop simulation in automotive applications, and is
tailored to the simulation and measurement of automotive
signals. The board contains signal conditioning for typical
signal levels of 12 V, 24 V, and 48 V automotive systems
and supports 2-voltage systems. Typical use cases are body
electronics, transmission, and component tests performed
by automotive suppliers, or as an additional HIL I/O board
in large powertrain and vehicle dynamics HIL applications.
382
Building an HIL Simulator

Together with a processor board (DS1005, DS1006 or
DS1007), the DS2202 HIL I/O Board constitutes the hardware
core of dSPACE Simulator. While the DS2202 measures and
generates the signals required, the processor board performs
the calculation of the real-time model. Communication
between the processor board and the I/O board runs via the
peripheral high-speed bus (PHS++ bus). The DS2202 can
be used in dSPACE Simulator Mid-Size (p. 496) and Full-Size
(p. 500).
2015
Introduction
Technical Details
Specification
A/D channels
D/A channels
Channels
n
16 differential A/D channels (multiplexed)
Resolution
n
14 bit
Conversion time1)
n
1.1 s per channel
Input voltage range
n
0 60 V, differential inputs
Offset error
n
10 mV
Gain error
n
0.5 %
Input impedance
n
>1 M
Channels
n
20 D/A channels with individual ground sense line
Output voltage range
n
0 10 V (with internal reference, or ratiometric with 5 10 V external
Application Fields
Parameter
reference)
lines allow differential outputs with DACx2) output swing -10 V ... +12 V
from system ground
Digital inputs
Resolution
n
12 bit
Settling time
n
20 s (full scale to 1 LSB)
Output current
n
5 mA
Offset error
n
5 mV
Gain error
n
0.5 % (with internal reference)
Channels
n
Max. 24 PWM measurement inputs (shared with digital inputs),
Software
n
Sense
up to 50 ns resolution, 0.01 Hz 100 kHz

n
Max. 38 digital inputs (24 inputs shared with PWM inputs)
n
PWM measurement input channels can also be used for frequency
Digital outputs
Input voltage
n
0 +60 V
Threshold voltage level
n
1 V 23.8 V
Input impedance
n
390 k
Channels
n
16 digital outputs
Hardware
measurement
n
9 PWM outputs, resolution 16 bit, 0.01 Hz 100 kHz, push/pull outputs
n
PWM outputs can also be used for square wave signal generation
External supply voltage
n
+5 V +60 V
n
Supplied from two independent rails (VBAT1 and VBAT2)
n
2-voltage support for digital outputs, selectable pin-wise
Output current range
n
Max. 50 mA
Vout high, min.
n
(VBATx 1.2 V) at +50 mA
Vout low, max.

Interfaces
Serial interface
n
0.4 V at -50 mA
Configuration
n
TL16C550C single UART (universal asynchronous receiver and transmitter)
Engineering
n
RS232, RS422 compatibility
Baud rate
n
Up to 115.2 kBd (RS232)
n
Up to 1 MBd (RS422)
CAN bus interface
Configuration
n
2 CAN channels based on ST10F269 microcontroller
n
ISO DIN 11898-2 CAN High-Speed standard
n
Max. 1 MBd
n
I/O
Host interface
n
connection via 2 x 100 pin high-density connectors and a 50-pin female

Sub-D connector
software complexity, the attainable overall performance can deviate significantly from the hardware specification.
2)
Output swing referenced to ground, when DACx is connected to another potential than GND.
1)
2015
383
Baud rate
Technical Details
Parameter
Specification
Physical
characteristics
Physical size
n
340 x 125 x 61 mm (13.4 x 4.9 x 2.4 in)
n
Requires three brackets
n
0 55 C (32 131 F)
Ambient temperature
Power supply
From host PC/expansion box
n
+5 V 5%; 1 A (without load on power supply outputs on output connector)
n
+12 V 5%; 0.15 A (typ.), 0.3 A max. (with load on all analog outputs)
n
-12 V 5%; 0.15 A (typ.), 0.3 A max. (with load on all analog outputs)
VBAT
n
Two VBAT rails (5 V 60 V DC)
n
Each rail (VBATx): 0.05 A + load current on digital outputs
n
VBATx has to be supplied from an external source
Order Information
Product
Order Number
n
DS2202
Relevant Software
Software
384
Order Number
Required
n
n
RTI
Optional
n
RTI CAN Blockset (p. 68)
n
RTICAN_BS
n
n
RTICANMM_BS
2015
Introduction
Block Diagram
PHS bus
Processor board
I/O boards
Sensor and
actuator interfaces
Application Fields
ADC
interface
PHS-bus
interface
DAC
interface
Bit I/O unit
PWM unit
Software
CAN
subsystem
Serial
interface
Power
supply
Communication
interface
DS2202
PC
2015
385
Engineering
Hardware
ISA bus

Central I/O board for hardwareintheloop simulation
Highlights
Highlights
n Simulates and measures all engine signals
(for up to 8 cylinders)
n Signal conditioning for signal levels of 12 V,
24 V, and 48 V automotive systems
n Supports 2-voltage systems
n Ideally suited for engine, powertrain,
and vehicle dynamics applications
386
Key Benefits
The DS2211 HIL I/O Board is the central I/O board for hardware-in-the-loop simulation, especially in the field of automotive electronics. The DS2211 HIL I/O Board is tailored to
the simulation and measurement of automotive signals,
particularly for engine and vehicle dynamics applications,
and combines a variety of typical HIL I/O signals on one
board. The board contains signal conditioning for typical
signal levels of 12 V, 24 V, and 48 V automotive systems
and supports 2-voltage systems.
Building a HIL Simulator

Together with a processor board (the DS1005, DS1006 or
DS1007), the DS2211 HIL I/O Board constitutes the hardware
core of dSPACE Simulator. The processor board performs
the calculation of the real-time model, for example, of an
engine, while the DS2211 measures and stimulates all the
required I/O signals. The simulator can be expanded from
8-cylinder up to 96 cylinders by using two or more DS2211
HIL I/O Boards.
Angular Processing Unit

The DS2211 HIL I/O Board features a unique angular
processing unit which supports high-speed generation and
measurement of crank angle-related signals to simulate
engines up to 29,000 rpm.
Angle-Synchronous Cascading
For tougher I/O requirements, several boards, for example,
several DS2211s, can be cascaded. The boards operate
angle-synchronously if their time base connectors are connected. One DS2211 board acts as the time base (angle
master), and the other boards read out its time base, which
allows signals to be generated and measured angle-synchronously on several boards. The same applies to the
DS4002 Timing and Digital I/O Board (p. 404), the DS5001
Digital Waveform Capture Board (p. 428), and the DS5203
FPGA Board (p. 438), which can all be connected to the
time base, too.
See p. 390 for an application example.
2015
Introduction
Technical Details
Parameter
Specification
General
n
Angular
Slave processor
DSP (digital signal

processor)
Application Fields
processing unit (APU) to handle all crankshaft-angle-related signals (ignition,

injection, crankshaft, camshaft, etc.)
n
Simulation of crankshaft sensors that detect the direction of rotation
n
1 crankshaft signal output (programmable analog and digital waveforms)
n
Max. 4 camshaft signal outputs (2 with programmable analog and digital output plus
2 with digital output only, shared with 2 digital outputs)
n
Complex comparator functionality support for ignition and injection signals
n
Support for the SAE standard J2716 (SENT)
n
Time-base connector
n
Texas Instruments TMS320VC33 floating-point DSP
n
150 MFLOPS
n
13.3 ns cycle time
n
6 angle position interrupts (can be set at any engine position in 0.01 degree increments)
n
1 CAN controller interrupt
n
1 serial interface (universal asynchronous receiver and transmitter) interrupt
D/A channels
n
0.011 crank angle
Speed range
n
29,000 rpm
Speed resolution
n
0.112 rpm
Channels
n
16 differential A/D channels (multiplexed)
Resolution
n
14 bits
Conversion time1)
n
1.1 s per channel
Input voltage range
n
0 60 V, differential inputs
Offset error
n
10 mV
Gain error
n
0.5 %
Input impedance
n
> 1 M
Channels
n
20 D/A channels with individual ground sense line
n
0 10 V (with internal reference, or ratiometric with 5 10 V external reference)
Software
A/D channels
Angular resolution
Hardware
Angular processing unit (APU)
n
Sense lines allow differential outputs with DACx2) output swing -10 V ... +12 V from
system ground
Resolution
n
12 bits
Settling time
n
Analog outputs
n
1 crankshaft signal (angular processing unit)
n
2 camshaft signals (angular processing unit)
n
4-channel wheel speed or 4-channel knock signal generation (based on DSP); up to
8 knock signals per cycle
Slave DSP DAC
Transformer outputs
Output current
n
5 mA
Offset error
n
5 mV
Gain error
n
0.5 % (with internal reference)
Settling time
n
n
10 V
Output current
n
5 mA
n
20 V (transformer output mode)
Engineering
n
4 additional analog waveform outputs (from DSP, no sense line, 10V)
n
5 mA
software complexity, the attainable overall performance can deviate significantly from the hardware specification.
2)
Output swing referenced to ground, when DACx is connected to a potential other than GND.
1)
2015
387
n
10 V (DC output mode)
Output current
Technical Details
Parameter
Specification
Resistive output channels
Digital inputs
Channels
n
10 channels
Topology
n
16-bit switched resistor ladder
Resistance range
n
15.8 1 M
Resistance error
n
2% or 3, whichever is greater, with RESx pin within 5 V of system ground
Voltage range
n
Each terminal must stay within 10 V of system ground
n
Max. 80 mA
Power per channel
n
Max. 250 mW
Channels
n
Max. 24 PWM measurement inputs (16 inputs shared with digital inputs, 2 inputs
shared with injection inputs), up to 50 ns resolution, 0.01 Hz 100 kHz

n
Max. 16 digital inputs (all inputs shared with PWM measurement inputs)
n
Max. 8 ignition inputs (2 inputs shared with auxiliary capture inputs), up to
64 sparks per event window, or up to 64 events buffered for continuous readout

n
Max. 8 injection inputs (2 inputs shared with PWM measurement inputs), up to
64 pulses per event-window, or up to 64 events buffered for continuous readout

n
Max. 2 auxiliary capture inputs (all inputs shared with ignition inputs)
n
PWM measurement input channels can also be used for frequency measurement
n
Max. 4 SENT receive channels (revision SENT2010)
Digital outputs
Input voltage
n
0 +60 V
n
1 V 22.65 V or 23.8 V (dependent on I/O circuit)
Input impedance
n
390 k
Channels
n
Max. 16 digital outputs (2 pins shared with digital camshaft signal outputs)
n
9 PWM outputs, resolution 16 bit, 0.01 Hz 100 kHz, push/pull outputs
n
PWM outputs can also be used for square wave signal generation
n
Max. 5 SENT transmit channels (revision SENT2010)
External supply voltage
n
+5 V +60 V
n
Supplied from two independent rails (VBAT1 and VBAT2)
n
2-voltage support for digital outputs, selectable pin-wise
Interfaces
n
Max. 50 mA
Vout high, min.
n
(VBATx 1.2 V) at +50 mA
Vout low, max.
n
0.4 V at -50 mA
Serial interface
n
TL16C550C single UART (universal asynchronous receiver and transmitter)
n
RS232, RS422 compatibility
n
Up to 115.2 Kbaud (RS232)
n
Up to 1 Mbaud (RS422)
CAN bus interface
n
2 CAN channels based on ST10F269 microcontroller
n
ISO DIN 11898-2 CAN High-Speed standard
n
Max. 1 Mbaud
n
I/O connection via 2 x 100 pin high-density connectors and a 50-pin female Sub-D
Host interface
n
connector
n
Requires three brackets (for I/O connectors)
Physical size
n
340 x 125 x 61mm (13.4 x 4.9 x 2.4in)
n
The board requires three brackets.
Ambient temperature
n
0 55 C (32 131 F)
Power supply
n
+5 V 5%; 1.5A
n
+12 V 5%; 0.25 A typical (max. 0.5A with load on all analog and transformer outputs)
n
-12 V 5%; 0.2 A typical (max. 0.5A with load on all analog and transformer outputs)
n
Two VBAT rails (5 V 60 V DC)
n
Each rail (VBATx): 0.05 A + load current on digital outputs
n
VBATx has to be supplied from an external source.
388
2015
Introduction
Order Information
Product
Order Number
n
DS2211
Relevant Software
Order Number
n
n
RTI
Optional
n
n
RTICAN_BS
n
n
RTICANMM_BS
n
Texas Instruments C3X/4X Code Composer (p. 98)
n
TMDS3240130
Application Fields
Software
Required
PHS bus
I/O boards
Sensor and
actuator interfaces
ADC
interface
Crankshaft
signal
generator
DAC
interface
Camshaft
signal
generators
Resistance
simulation
Ignition
capture
Bit I/O unit
Injection
capture
PWM unit
DSP
subsystem
CAN
subsystem
Hardware
PHS-bus
Interface
Engineering
Angular
processing unit
Engine
position
accumulator
Processor board
Serial
interface
Power
supply
Communication
interface
DS2211
ISA bus
PC
2015
389
Engine Position Bus
Further
DS2211s,
DS4002s,
DS5001s
Software
Block Diagram
Programming from MATLAB/Simulink/Stateflow
Programming and connecting to I/O is simple with our Real-Time
Interface (p. 54), which enables you to program all your I/O
graphically in Simulink, even the angular processing unit.
For connection to the CAN bus, for example, the optional

RTI CAN Blockset extends Real-Time Interface for easy,
graphical CAN configuration from Simulink. The blockset
comprises CAN controller configuration and dialog-based
parameterization of messages in receive and transmit modes
(p. 68).
Application Example: Simulating a 12-Cylinder EVT Engine

The Challenge: Immense I/O
HIL simulation of a 12-cylinder, 48-valve engine with an
electromagnetic valve train (EVT) is a real challenge, especially as regards I/O. The engine ECU generates 12 injection
signals plus 12 ignition signals. In addition, 4 valve signals
are needed for each of the 12 cylinders to control the
electromagnetic valve actuators. This means that if the
engine is simulated, 72 signals generated by the ECU have
to be captured angle-synchronously.
.
.
.
DS5001
(Slave)
Engine Position Bus
DS5001
(Slave)
DS5001
(Slave)
DS2211
(Slave)
Injection signals
12
Cascading Several I/O Boards

The DS2211 HIL I/O Board is designed to be the heart of
such applications. The hardware can be cascaded via the
Engine Position Bus, with further boards operating anglesynchronously. In this case, the dSPACE Simulator hardware
consists of a further DS2211 and three DS5001 Digital
Waveform Capture Boards. The DS2211s are ready to capture injection and ignition signals of 6 (up to 8) cylinders
each, while each DS5001 provides 16 capture channels for
the valve signals. One board is the time base (angle master)
for the other boards, so that all signals can be generated
and captured angle-synchronously.
Another example in which you might need angle-synchronous
signal capturing is a rail pressure actuator for direct injection
gasoline engines.
Injection signals
12
Valve train signals

48
ECU
Crankshaft signal
DS2211
(Master)
.
.
.
390
2015
Introduction
Application Example: HIL Simulation of a 6-Cylinder Engine
Processor Board
Camshaft Phase
Knock Parameters
Engine
Position
Bus
Crankshaft Signal
Generator
Crankshaft Signal
Camshaft Signal
Generator
Camshaft Signal
VC33 DSP
Knock Signals
Ignition
Capture
Ignition Signals
Injection Angles
Injection
Capture
Injection Signals
Hardware
Spark Advance
ECU
Engineering
Engine I/O Performed by the DS2211

The DS2211 HIL I/O Board uses the engine position and
other model parameters to generate all the required signals
(for example, crankshaft, camshaft, and knock signals). To
simulate the complexity of an engine, the signals have to
be highly realistic so that they can be processed by the ECU.
In parallel, the DS2211 reads out the ECUs reactions to the
simulation (for example, ignition and injection signals), and
preprocesses them for the real-time model running on
the processor board.
Simulated crankshaft and camshaft signals.
The engine model is calculated by the processor board, while the

DS2211 performs the challenging I/O tasks.
2015
391
Engine Position
Accumulator
Software

Speed
PHS
Bus
Engine Position Based Signal Generation

The processor board performs the calculation of an engine
model and sends all the calculated engine data to the
DS2211 (for example, engine speed, camshaft phase, and
engine knock parameters). The DS2211 processes this data
with an engine position accumulator that constantly calculates the engine position according to the current engine
speed. With a 16-bit angle resolution and an engine speed
resolution of 0.112rpm, this engine position is the basis for
all further signal generation.
Application Fields
A HIL System with Just Two Boards

Together with a processor board (the DS1005, DS1006 or
DS1007), the DS2211 provides a compact, yet powerful
dSPACE Simulator for hardware-in-the-loop simulation, for
example, for function or system testing.
Modular Hardware / DS2302 Direct Digital Synthesis Board

Powerful board for realtime and highaccuracy signal generation
Highlights
n Essential for hardware-in-the-loop simulation
n Flexible sensor signal simulation with up to 6 channels
n Fast analog output on up to six 16-bit DACs
n APU (angular processing unit) slave interface for each
channel
Key Benefits
The DS2302 enables you to simulate complex sensor signal
waveforms for testing electronic control units (ECUs). The
board was redesigned and equipped with a faster processor,
and is compatible with its earlier version. It meets tough
requirements regarding complexity, flexibility and resolution.
The DS2302 is equipped with six DSPs and designed for
fast, flexible waveform generation. It computes each signal
sample just-in-time and outputs it immediately. The signal
parameters can easily be changed on-the-fly by a master
processor board. The DS2302 C functions allow you to
exchange data between your main application and an application running on one of the six DSPs. Communication
runs via the dual-ported memories of the DS2302.
392
Application Areas
To test an ECU to its limits, even interferences such as noise
or spikes often need to be simulated. For example, in automotive hardware-in-the-loop applications, signals such as
crankshaft or camshaft pulses have to be generated as
angle-based for the greatest accuracy. Signal variables, such
as engine speed, must be modified in real time. The Fast
Analog Capturing Module (p. 394) is used to capture injection control voltage and calculate the injection quantity for
piezo actuators of SI engines.
2015
Introduction
Technical Details
Parameter
Specification
General
n
6 independent direct digital synthesis channels
Processor
Digital signal processor (DSP)
n
Texas Instruments TMS320VC33 floating-point DSP
n
150 MFLOPS
n
13.3 ns cycle time
Memory
n
16 K x 32-bit true dual-port RAM per channel
Application Fields
n
Used for program download and to read/write parameters (e.g., for communi
cation between DSPs)

DSP interrupts
n
On-board I/O (e.g., timer or DMA), external, other DSP channels
n
One interrupt to PHS-bus master per DSP channel
Plug-on modules
n
Plug-on DAC module (optional) (p. 394)
n
Plug-on ADC module for fast analog capturing (optional)
Digital I/O
Voltage range
n
TTL input/output levels
Output current
n
Max. -800 A/+1.5 mA
Further details
n
7 digital I/O lines per DSP
n
Programmable as input or output
n
One line programmable as external interrupt input
Software
n
APU (angular processing unit) slave interface for each channel
n
44-pin female high-density Sub-D output connector
Physical size
n
338 x 114 x 20 mm (13.3 x 4.5 x 0.8 in)
Ambient temperature
n
0 70 C (32 158 F)
Power supply
n
+5 V 5%, 4.0 A (with 6 DAC modules inserted)
Product
Order Number
n
DS2302
Hardware
Order Information
n
Texas Instruments C3X/4X Code Composer
n
TMDS3240130
n
n
RTI
n
Connector panel for DS2302 (p. 480)
n
CP2302
Hardware
Optional
Order Number
2015
393
Required
Order Number
Engineering
Software
Block Diagram
Processor
Board
PHS Bus
PHS-Bus
Interface
APU
Slave
Interface
PHS-Bus
Interrupt
Controller
Channel 6
Channel 5
Channel 4
Channel 3
Channel 2
Channel 1
Interrupt
Select
Register
Address
Register
I/O Boards
16K x 32
DPRAM
VC33
DSP
150 MHz
Analog
In/Out
Digital
I/O
..
..
Analog
In/Out
Digital
I/O
Plug-On
Module
Setup
Register
Data
Register
DS2302
DAC Module
Parameter
Specification
General
n
One D/A converter per channel
n
16-bit resolution
n
Reset on I/O error (programmable)
Analog output
(typical values at 25 C)
Voltage output range
n
10 V
Output current
n
Max. 5 mA
Initial offset error
n
1 mV
Offset drift
n
10 ppm of FSR/K (FSR = full scale range)
Initial gain error
n
0.5%
Gain drift
n
20 ppm of FSR/K
Settling time
n
0.8 s typ. at 0.012% of FSR
Slew rate
n
Approx. 25 V/s
n
1 LSB (least significant bit)
Monotonicity
n
14 bit
Total harmonic distortion
n
-90 dB (at 10 kHz)
Physical size
n
92 x 18 x 10 mm (3.6 x 0.7 x 0.4 in)
Ambient temperature
n
0 70 C (32 158 F)
Power consumption
n
1.45 W
Fast Analog Capturing Module

Up to 6 Fast Analog Capturing Modules1) can be used with
one DS2302 to capture injection control voltage and calculate injection quantity for piezo actuators of SI engines.
394
1)
2015
The Fast Analog Capturing Module is an additional I/O solution for the DS2302 Direct Digital Synthesis Board. It is neither
part of the dSPACE product range, nor part of any dSPACE releases. For more information, please contact dSPACE.
n 2 channels
n 10V input range
n Optional external trigger input
Application Fields
n 1 megasamples per second sampling rate
Software Details
n Integration (Euler) on DS2302 slave DSP in 8 ... 10s
n Threshold values for starting and stopping computation
included
n Capture of n injection pulses (currently n=3 per cylinder)
per 720 crankshaft revolution
n Values provided to the master via dual-port memory
Generating Signals
n PWM
n Incremental sensor simulator
Software
n Fourier synthesis
n Engine knock signals consisting of damped oscillation
overlaid by random noise

n Digital pulses with variable logic levels
Hardware
Typical Nontrivial Signals

Signal generation is based on algorithms, so there is virtually no limit to the variety of waveform signals, including
interdependencies between several signals. This list therefore
includes just a small selection of what is actually possible:
n Sinusoidal wheel speed signals
n Angle-based sinusoidal crankshaft and camshaft signals
n Missing teeth on toothed crankshaft sensor wheels
n Non-angle-equidistant pulses with stochastically
disturbed edge positions
n Crankshaft, camshaft, and knock signals
n Interferences such as spikes with variable waveforms,
periods or amplitudes
n Nonstationary noise of variable noise color depending
on engine speed or type

n Time-variant Fourier synthesis, i.e., for simulating
engine sound
Engineering
Common Signals
Software examples are included with the DS2302 for most
of these signal types:
n Sine-wave, square-wave and sawtooth
n Gaussian noise and PRBS
Real-Time Interface
The DS2302 Simulink read/write blocks and dialogs
provided by Real-Time Interface allow convenient parameter updates via the on-board dual-port memories.
2015
395
Hardware Details
n 16-bit resolution
Introduction
Programming the DS2302

C Code
C Code Programs
Programs in C code are available for various signals, but you can
also use them as a starting point for your own applications. Each
channel can run its own signal generator program. Channels
can also trigger each other with interrupts and access other
channels variables via their dual-port memories. To determine
the maximum sampling rate your application can reach, there
are utilities for execution time measurement and optimization.
Downloading an Application
When the development and test phase of your DS2302
applications has finished, you can include them in your master
application and download the complete application via the
processor board to the DS2302 by using dSPACEs Real-Time
Interface from your Simulink block diagram.
Host PC
Compiling +
Speed Optimization
MATLAB/Simulink +
Real-Time Interface
Indirect Download
Processor Board
PHS bus
DS2302
Controlling the DS2302

Controlling via Simulink block diagramm
The variables controlling signal generation, such as the
engine speed for a crankshaft signal, can be updated continuously via the master processor board, for example, from
your Simulink block diagram.
Simulink
Read/Write
Variables
Processor Board
Master Application
DS2302
Signal Generation
Use Cases
Sensor Simulation
Simulating Sensor Signals
The simulation of crankshaft, camshaft, and knock signals
plays an important role in HIL applications for testing engine
or powertrain control units. The ECU uses these signals to
determine the proper injection and ignition timing. The
396
simulated signals therefore have to meet rigorous quality

requirements. For example, a 0.1 angle resolution for the
crankshaft requires a 2.8 s timing resolution at a speed of
6,000 rpm.
2015
Introduction
Crankshaft, Camshaft, and Knock Signal Simulation

Testing an Engine ECU
While crankshaft and camshaft signals mainly depend on
the engine speed calculated by the processor board, the
knock signal also depends on various other parameters. To
test the engine ECU under different conditions, simply
change the engine type or introduce noise or spikes all
on-the-fly.
Application Fields
Application Areas
The DS2302 board is ideally suited for simulating crankshaft,
camshaft and knock signals. Channel 2 generates the sinusoidal crankshaft signal, including the gap for the two
missing teeth in the sensor wheel. This channel also computes the triggers for the camshaft pulses and the knock
signal, which are generated in channels 1 and 3. The knock
signal basically consists of damped oscillation, overlaid by
speed-dependent random noise.
To Processor Board
Engine Speed
DP-RAM 3
Knock
Parameters
Software
DSP 2
Crankshaft
DSP 3
Knock Signal
Simulating Angle-Based Sensor Signals

engine model. Each time a certain angle is reached, a pulse
edge is generated. The fast on-board DSPs make it possible
to check the crankshaft angle on a microsecond basis, thus
providing an extremely high resolution.
Engineering
Precise Sensor Simulation

In many applications, precise sensor simulation requires
the generation of angle-based sensor signals. To get the
angle of a crankshaft, for example, the DS2302 board can
autonomously integrate the engine speed coming from an
Angle-based signals
2015
397
PHS Bus or ISA Bus
Engine Speed
DP-RAM 2
DSP 1
Camshaft
Hardware
Engine Speed
DP-RAM 1
Modular Hardware / DS2401 Resistive Sensor Simulation Board

For simulating resistive sensors
Highlights
n Ideally suited to hardware-in-the-loop simulation
n 10 to 500 k resistance range
n Channels individually insulated from system ground
n 4 resistance output channels
Application Areas
In hardware-in-the-loop applications, the simulation of sensors plays an important role. While many sensors provide
voltages or currents, others have a resistance output for
example, thermistors or resistance temperature detectors
(RTDs) for temperature measurement. To simulate these
resistive sensors, precise resistance values must be provided.
Key Benefits
The DS2401 features four resistance output channels of
identical structure. All channels are insulated from system
ground individually. The application running on the processor board writes the desired resistance to the DS2401 board,
and the resistance is then simulated electronically between
the two output pins of that channel.
Block Diagram
Processor
Board
PHS Bus
I/O Boards
Resistor Channel 4
PHS-Bus
Interface
Resistor Channel 3
Resistor Channel 2
Resistor Channel 1
Opto
Isolation
12-bit
Multiplying D/A
Converter
Default
Resistance
CH4
CH3
Power
Supply
Insulated
Power Supply
Current Sense
& Ranging
CH2
Overload
Protection
CH1
DS2401
ISA Bus
398
PC
2015
Introduction
Modular Hardware / DS2401 Resistive Sensor Simulation Board
Technical Details
Parameter
Specification
General
n
4 simulated resistors
n
12-bit resolution
n
Default resistance output during power-down (determined by external resistor)
n
Overload relay state output
n
10 ... 500 k total resistance range (programmable)
n
Automatic range switching for each channel (by software): 10 ... 250 , 200
Cutoff frequency (-3 dB)
2 k ... 50 k, 20 k ... 500 k

n
15 kHz (10 kHz at R > 50 k)
Settling time to 1%
n
50 s
Voltage across resistor
n
Max. 20 V
Load current
n
Max. 20 mA
Initial offset voltage error
n
3 mV
Initial resistance error
n
0.3% + 0.5
Total linearity error
n
2 LSB
Monotonicity
n
12 bit
Offset drift
n
100 V/K
Resistance drift
n
40 ppm/K
Noise voltage
n
10 mVrms (at 1 k)
Isolation
n
All channels individually insulated from system ground
Overload relay state Voltage output range

outputs
Output current
n
TTL
DEF_EN output
Voltage output range
n
TTL
Output current
n
Max. -0.4 mA/+20 mA
... 5 k,
n
Max. -0.4 mA/+4 mA
Triggering
n
By software from master processor board; immediate output or simultaneous update
n
Host interface
n
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in)
Ambient temperature
n
0 ... 70 C (32 ... 158 F)
Power supply
n
+5 V 5%, 0.6 A
Hardware
Physical
characteristics
Application Fields
Resistance range
Software
Resistor terminals
n
+12 V 5%, 1 A
Product
Order Number
n
DS2401
Engineering
Order Information
Relevant Software
Required
Order Number
n
n
RTI
2015
399
Software
Modular Hardware / DS3001/DS3002 Incremental Encoder Interface Boards
DS3001/DS3002 Incremental Encoder Interface Boards

Essential for precise position control
Highlights
n Ideal for applications in robotics and drive control
n Up to 6 incremental encoder interface channels
n 24- or 32-bit position counters
n Measuring digital or sinusoidal position signals
Key Benefits for DS3001

The DS3001 is designed for position control applications
with sensors providing digital phase information. It comprises five parallel input channels, each providing everything
needed to connect an incremental encoder and process its
output signals: a regulated encoder power supply with sense
lines, differential or single-ended inputs for the encoders
two phase lines, and an index input.
Key Benefits for DS3002

If digital encoder information cannot provide the desired
position accuracy, or if you want to employ encoders with
fewer lines, sinusoidal position sensor signals can increase
accuracy and resolution significantly. The DS3002s six channels capture sinusoidal encoder signals and subdivide them
up to 4096 times. Each channel has its own 32-bit position
counter that can also be used for digital signals.
Main Differences Between DS3001 and DS3002
400
DS3001
DS3002
Number of channels
Position counter
24 bit
32 bit
Max. input frequency
1.25 MHz
750 kHz
Incremental encoder signal types
Digital (differential RS422, singleended TTL)
Digital (differential RS422, singleended TTL) and sinusoidal

(11 App or 1 Vpp)
Resolution
4fold subdivision
4fold subdivision (digital) or 4096fold subdivision (analog)

between encoder lines
2015
Introduction
DS3001 Incremental Encoder Interface Board

Technical Details
Parameter
Specification
General
n
5 independent incremental encoder interface channels
n
Differential inputs for encoder phase lines and an index line on each channel
Application Fields
n
Encoder power supply lines
n
Interrupt on index
n
Four-stage digital filter
n
5 index interrupts (one for each channel)
Encoder signal types
n
Digital signals: single-ended (TTL) or differential (RS422)
n
Selectable individually for each channel
n
Minimum index pulse width 200 ns
Position counters
n
24-bit counters
n
Max. 1.25 MHz input frequency, i.e., fourfold pulse count up to 5 MHz
n
Counter reset via hardware or software (asynchronous via PHS bus, synchronous via index-
pulse once or always)

n
5 V, 200 mA max. per channel
Software
n
Voltage regulation with sense lines
n
Separate index signal for each channel, via interrupt (edge-triggered) or flag (polling mode,
Index detection
level-triggered)
n
Index signal can be used for counter reset
Encoder interface
n
150 in series with 4.7 nF input impedance (RS422)
n
200 mV min. differential input voltage (differential mode only)
n
5 V max. common mode input voltage (differential mode only)
n
200 ns minimum encoder state width (programmable)
n
9.6 ms max. noise pulse width (programmable)
n
50-pin female Sub-D input connector
Host interface
n
Physical
characteristics
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in)
Ambient temperature
n
0 70 C (32 158 F)
Power supply
n
+5 V 5%, 2.5 A
Hardware
n
200 ns minimum index pulse width
n
+12 V 5%, 1.2 A
n
-12 V 5%, 150 mA
Product
Order Number
n
DS3001
Engineering
Order Information
Required
Order Number
n
n
RTI
n
n
CP3001
Hardware
Optional
Order Number
2015
401
Software

Technical Details
Parameter
Specification
General
n
6 independent incremental encoder interface channels
n
Differential inputs for encoder phase lines and an index line on each channel
n
Synchronized sampling of multiple channels
n
Encoder power supply line per channel
n
On-board line termination
n
Connector for measuring pulse widths and frequency of count/index pulses with other I/O
boards, e.g., DS5001

Encoder signal types
n
Sinusoidal signals: 11 App differential or 1 Vpp differential
n
Digital signals: single-ended (TTL) or differential (RS422)
n
Selectable individually for each channel
n
Minimum index pulse width 250 ns
n
32-bit counters
Position counters
n
Max. 750 kHz input frequency, i.e., fourfold pulse count up to 3 MHz
n
Counter reset or preload via software or automatically on index pulse
n
5 V, 200 mA max. per channel
n
Voltage regulation with sense lines
Input performance
n
12-bit resolution
ADC
n
800 ns data conversion time, 10 MSPS (pipelined)
Offset error (PHI0, PHI90)
n
4 mV for 1 Vpp (0.08 % position error)
n
75 nA for 11 App (0.14 % position error)
ADC nonlinearity
n
0.06 % resulting position error
n
No missing codes
Gain match (PHI0, PHI90)
n
0.25 % (0.025 % position error) of 1 Vpp
n
0.6 % (0.06 % position error) of 11 App
Common mode rejection ratio (PHI0, n

2.5 mV/V (0.05 %/V position error) each channel
PHI90 in 1 Vpp mode only)
n
Up to 4096 subdivisions between two encoder lines
Sinusoidal signal capture
n
Position calculation on processor board (look-up tables and interpolation)
n
62-pin female Sub-D input connector
Host interface
Physical
characteristics
n
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in)
Ambient temperature
n
0 70 C (32 158 F)
Power supply
n
+5 V 5%, 2.0 A
n
+12 V 5%, 200 mA plus 200 mA for each channel in use
Order Information
Product
Order Number
n
DS3002

Software
Required
Order Number
n
Hardware
Optional
402
n
RTI
Order Number
n
n
CP3002
2015
Introduction
How to Measure Encoder Signals
Application Fields
Measuring Digital Signals

Both the DS3001 and DS3002 boards support two kinds of
digital signals: differential RS422 and single-ended TTL. The
incremental encoder sends the phase-shifted digital signals
Ua1 and Ua2. These signals provide four pulse counts per
encoder line (fourfold multiplication). A position counter
stores the current value. The count direction depends on
the encoders rotation direction. The counter is initialized
from the processor board or by means of the encoders
index pulse. With the DS3002, sampling of count values
can be synchronized over multiple channels.
Start of
Conversion
Register
32 bit
+
12 bit
+
12 bit
Channel 6
Channel 5
Channel 4
Channel 3
Channel 2
Channel 1
Sensor
Power
32-bit
Position
Counter
Hardware
Index
Engineering
PHS-Bus
Interface
Block Diagram
I/O Boards
Phase
Decoder
12-bit
ADC
Phase 2
12-bit
ADC
Phase 1
Power
Supply
DS3002
ISA Bus
PC
2015
403
Processor
Board
PHS Bus
Software
Measuring Sinusoidal Signals

The DS3002 board supports 11 App signals as well as 1 Vpp
signals. With sinusoidal encoder signals, you can achieve a
much higher resolution than with digital signals.
The DS3002 board measures the analog values of the sinusoidal signals K1 and K2. This yields up to 4096 subdivisions
between two encoder lines. You can easily determine the
desired resolution and read the precise position value using
the included C functions.
Modular Hardware / DS4002 Timing and Digital I/O Board

Generating and capturing digital signals
Highlights
Captures digital signals for parameter measurement
n Generates flexible pulse patterns
n Comprehensive set of standard applications included
n Especially useful for automotive applications
n
Key Benefits
The DS4002 Timing and Digital I/O Board combines a
variety of digital I/O tasks on one board. It provides the
functionality you expect from an ordinary digital I/O board
plus additional features that help you perform specific control tasks easily. Eight channels can be programmed for
either capturing digital signals or generating flexible pulse
patterns. 32 additional I/O lines can be used for further
digital I/O tasks, for example, to control single input lines
(switches, sensors) or output lines (relays, displays).
Application Areas
The DS4002 Timing and Digital I/O Board is ideally suited
to all kinds of hardware-in-the-loop simulations and rapid
control prototyping. It captures digital signals for the measurement of parameters such as frequency or phase, and
generates digital signals such as PWM pulses to control
actuators or simulate sensors. It also performs many digital
I/O tasks, for example, controlling switches or displays.
A brief overview of applications:
n
n
n
n
n
n
Frequency measurement (F/D)

PWM duty cycle measurement
Phase shift measurement
1- and 3-phase PWM pulse pattern generation
Square-wave signal generation (D/F)
Monoflop signal generation
Further Features
The DS4002 Timing and Digital I/O Board can be used
together with the DS2211 HIL I/O Board to capture engine
signals angle-synchronously. The DS4002 can also be the
time base (angle master) in such a setup (DS2211, p. 386).
In many situations, the DS4002 board can be used as an
alternative to our DS5001 Digital Waveform Capture and
DS5101 Digital Waveform Output Boards (p. 428, p. 432).
404
2015
Introduction
Technical Details
Parameter
Specification
General
n
8 channels (timing I/O) with 200 ns resolution
n
Each channel individually programmable as input or output
n
Common 30 bit/200 ns time base
n
Fast dual-port RAM for data storage
n
32 additional digital I/O lines (TTL)
Application Fields
n
n
Time-base connector
n
1 read event interrupt
n
2 signal generation interrupts
Timing I/O
Signal capture mode
n
Time and polarity stored for each edge (time stamps)
n
Stores up to 512 30-bit time stamps per channel
n
Rising and/or falling edge detection programmable
n
Latchup protection
n
Interrupt to master processor after predefined number of edges
n
Minimum pulse widths: see table on p. 406
Signal generation mode
n
Signals described as a series of rising and falling edges
n
Stores up to 256 commands and 29-bit delay constants
Software
n
Minimum pulse width: see table on p. 406
n
All channels triggerable from channels 1 and 2
n
Interrupts programmable from channels 1 and 2
n
Loop counter
n
Update of time constants, output level, jump address, and loop counter during program execution
(swinging buffer mechanism)

n
Digital I/O
Voltage range
n
TTL input/output levels
Output current
n
Max. 75 mA
Input/output frequency
n
Max. 833 kHz (1 channel active)
Lines
n
32 lines with ESD (electrostatic discharge) protection:
Hardware
n
24 lines input/output (programmable in 8-bit groups, as direct input, strobed input or output)
n
4 lines fixed input mode
n
4 lines fixed output mode
n
1 strobe input
n
2 handshake lines for acknowledge and output ready
n
Direct and/or latched input mode
n
Max. -64 mA/+16 mA
External trigger input
n
2 lines with TTL input level
n
50-pin female Sub-D connector
Host interface
Physical
characteristics
n
Physical size
n
338 x 114 x 20 mm (13.3 x 4.5 x 0.8 in)
Ambient temperature
n
0 70 C (32 158 F)
Power supply
n
+5 V 5%, 3 A
Order Information
Product
Order Number
n
DS4002
2015
405
n
TTL input/output level
Output current
Engineering
n
Used to control single input or output lines
Voltage range

Software
Order Number
Included
n
C functions for accessing/controlling the DS4002
Required
n
Real-Time Interface (RTI), (p. 54)
Hardware
n
RTI
Order Number
Optional
n
n
CP4002
n
Connector/LED Combi Panel for DS4002 (p. 480)
n
CLP4002
Minimum Pulse Widths1)

The table below shows the minimum pulse widths for different numbers of channels in use, which are the same for
Capture and Generation mode.
1)
406
Channels
in Use
Pulse Width
(Capture Mode)
Pulse Width
(Generation Mode)
0.6 s
0.6 s
1.0 s
1.0 s
1.4 s
1.4 s
1.8 s
1.8 s
2.2 s
2.2 s
2.6 s
2.6 s
3.0 s
3.0 s
3.4 s
3.4 s
Speed and timing specifications describe the capabilities of the

hardware components and circuits of our products. Depending on
the software complexity, the attainable overall performance figures
can deviate significantly from the hardware specifications.
2015
Introduction
Block Diagram
Processor
board
PHS-bus
interface
I/O boards
Time-base
connector
Time base
Further DS5001/
DS4002/DS2211
Application Fields
PHS bus
Dual-port
memory
Channel 8
.
.
.
.
.
Controller
Timing I/O
unit
Channel 1
Interrupt
controller
Power
supply
Software
External
trigger
Digital I/O unit

32-bit
DS4002
PC
Hardware
ISA bus
2015
407
Engineering

The DS4002 Simulink blocks provided by Real-Time Interface allow convenient control of all timing and I/O lines: bit
in, bit out, PWM, F/D, D/F, signal capture mode, and hardware interrupt.
Creating Pulse Patterns in Generation Mode
You can create complex pulse patterns flexibly in Generation
mode. Functions for the most common applications, such
as PWM pulse pattern generation and square-wave signal
generation, are included. Or you can program your own
pulse patterns directly in C code.
Channels 1 and 2 can trigger other channels and send inter-
rupts to the master processor. In addition, all channels can

be controlled by two external trigger input lines. During
program execution, the delay constants, output level, jump
address, and loop counter can be updated synchronously
or individually per channel.
Changing Frequencies During Run Time

Square-wave signals, such as those for transmission speed
simulation, can be changed at any time simply by updating
the delay parameter. You have two options for doing this.
With delayed update, the new value dnew becomes active
after the old value dold has expired. With immediate update,
dnew replaces the current dold without any delays.
Recording Signals in Capture Mode

Using a channel in Capture mode, you can record any
digital signal you want. This is especially useful for evaluating signal parameters such as frequency, phase, or jitter.
Functions for standard applications, such as PWM pulse
evaluation or frequency measurement, are included.
The captured signals are described as a series of rising and
falling edges. The time and polarity are recorded for each
edge (rising and/or falling programmable) (time stamps).
The on-board dual-port RAM stores up to 512 time stamps
of 30 bits per channel. This data is used for further data
processing by a dSPACE processor board. Recording a predefined number of edges can trigger an interrupt to the
master processor.
408
2015
Modular Hardware / DS4003 Digital I/O Board
Introduction

Large number of digital I/O channels for various applications
Application Fields
Highlights
n 96 TTL lines (three 32-bit ports)
n 3 handshake control lines per port
Software
n 2 interrupts per port plus one on I/O error
Technical Details
Parameter
Specification
General
n
Release output for external release logic
n
I/O error monitor output and I/O error request input for error monitoring of external devices
n
Two customization module connectors (pinheaders) supporting digital I/O lines and power supply of two ports
Interrupt controller Interrupt sources
n
Three user interrupts, one per port
n
Three strobe interrupts, one per port
Digital I/O
n
TTL input level
Lines provided by
each port
n
32 I/O lines programmable in 8bit groups, usable as nonstrobed input, strobed input or output
Hardware
n
One interrupt on I/O error
Voltage range
n
One strobe input
n
Two handshake lines for acknowledge and output ready
Voltage range
n
TTL input level
Output current
n
15 mA out (high, 2.4 ... 5 V), 24 mA in (low, 0 ... 0.8 V)
Input current
n
0.12 mA in (high, 2.4 ... 5 V), 0.2 mA out (low, 0 ... 0.8 V)
n
Three 50pin male SubD connectors (three brackets required)
n
One 8 or 16bit ISA slot (power supply only)
n
The board requires three brackets
Ambient temperature
n
0 ... 70 C ( 32 ... 158 F)
Power supply
n
+5 V 5%, 1.5 A (without customization modules/external loads)
Order Information

Software
Required
n
RealTime Interface (p. 54)
Hardware
Optional
Engineering
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in)
Order Number
Product
Order Number
n
RTI
n
DS4003
Order Number
n
Connector Panel for DS4003 (p. 480) n
CP4003
n
Combined Connector/LED Panel for
n
CLP4003
DS4003 (p. 480)
2015
409
Host interface
Physical
Physical size
characteristics
Modular Hardware / DS4004 HIL Digital I/O Board
DS4004 HIL Digital I/O Board

96 bidirectional digital I/O channels with signal conditioning
Highlights
n 96 digital I/O channels with general signal conditioning
up to 60 V
n Measures and generates automotive signals and
TTL signals
n All channels configurable via software
n Flexible HIL simulation for widely varying configurations
of body electronics

Key Benefits
The DS4004 comprises 96 digital I/O channels with signal
conditioning for typical automotive systems with electrical
system voltages of 12 V, 24 V, 36 V, and 48 V, etc., as well
as for customary TTL levels. The 96 digital I/O channels of
the DS4004 are arranged in three identical groups, each
with two different voltage systems, ranging from 5 V to
60 V. Each of the 96 I/O channels of the DS4004 can be
configured via software as digital I/O for PWM measurement
or PWM generation, for frequency measurement, or for
square wave generation. The digital I/O channels can be
used individually, or synchronized in 32-bit words. You can
set the values of the I/O channels for the initialization phase
and for terminating the model.
410
Application Areas
The automotive signal conditioning on the DS4004 HIL
Digital I/O Board is a cost-efficient way to start using HIL
simulation for body electronics ECUs. The DS4004 can be
used hassle-free and at low cost in an expansion box, the
dSPACE Simulator Mid-Size and the dSPACE Simulator FullSize. These simulators are frequently used to test body
electronics ECUs with the DS4004.
2015
Introduction
Modular Hardware / DS4004 HIL Digital I/O Board
Technical Details
Parameter
Specification
I/O channels
n
96 bidirectional digital I/O channels with automotive signal conditioning, arranged in three
ports (P1, P2, P3) of 32 I/O lines each

n
Software-configurable as digital I/O or timing I/O (PWM I/O)
n
PWM functionality with up to 50 ns resolution
Digital Outputs
Input voltage
n
0 ... +60 V
Input impedance
Overvoltage protection
Output voltage
n
390 k
n
1 V ... 23.8 V (software-configurable)
Application Fields
Digital inputs
n
0 ... +60 V continuous
n
+5 V ... +60 V (supplied from external power source)
n
6 independent rails VBAT_Px_y (two rails for each port P1 ... P3)
n
Max. 50 mA; short circuit proof to GND and VBAT by self-resetting fuse
n
1 V ... 23.8 V (software-configurable)
n
VBAT -1.2 V; at +50 mA
n
0.4 V; at -50 mA
n
3 x 2 pins (shared with I/O channels)
n
Interrupt generation on falling edges, rising edges, or both edges (software-configurable)
n
Physical size
Software
Host interface
Physical
characteristics

Vout high, min.
Vout low, max.
Interrupt channels
Trigger source
n
340 x 125 x 19 mm (13.4 x 4.9 x 0.7 in)
n
The board requires three brackets
Ambient temperature
n
0 ... 55 C (32 ... 131 F)
Power supply (from host PC)
n
+5 V 5%, 1.5 A max. (from host PC or expansion box)
n
+12 V 5%, 0.4 A max. (without load on power supply outputs)
n
-12 V 5%; 0.01 A max.
Hardware
Power supply (from external power n

6 VBAT_Px_y rails (+5 V ... +60 V DC)
source)
n
Each supply rail (VBAT_Px_y): 0.2 A max. (0.05 A typ.) + load on digital outputs
Order Information
Product
Order Number
n
DS4004
Relevant Software
Order Number
n
n
RTI
Engineering
Required
2015
411
Software
Modular Hardware / DS4121 ECU Interface Board

Connects electronic control units with a dSPACE modular system
Highlights
n Real-time interface to ECUs with 8-, 16- and 32-bit
microprocessors
n Two LVDS channels for high-speed, low latency
communication
n Standard ECU interface blockset fully
integrated in MATLAB/Simulink
n Tailored for bypass applications and the
RTI Bypass Blockset
412
Application Areas
The DS4121 provides the link between your electronic
control unit (ECU) and a dSPACE modular system. Bypassing
individual ECU algorithms and calculating them on a
prototyping system is a typical application example. The
connection is made via a dual-port memory plug-on device
(DPMEM POD), on-chip debug interfaces like the DCI-GSI1
(p. 574) or an LVDS-Ethernet Link cable (p. 413) to establish
an Ethernet UDP/IP communication. Two independent
ECUs can be connected to the DS4121 at the same time.

This offers the flexibility to operate such things as powertrain
control modules containing the engine and transmission
controllers, or valve controls for 8- and 12-cylinder engines.
In addition, the DS4121 board provides the interface to the
LVDS-Ethernet Link cable allowing dSPACE modular systems
to be connected to Ethernet devices or networks.
Key Benefits
The DS4121 is designed to carry out bypassing exactly the
way you want. For example, the production-intent ECU can
remain in its final mounting position while the prototyping
system might be mounted virtually anywhere in the vehicle.
The standard board version of the DS4121 is connected
to the ECU via copper cable. The DS4121-FX uses a fiberoptic link which increases the possible distance between
board and ECU.
Bypassing with the DS4121

With the DS4121, you can either use one single hardware
interrupt from the ECU to the prototyping system, or you
can split one interrupt into up to 128 subinterrupts with
a specially designed ECU software porting kit, allowing full
multi-level, multitasking bypassing. The interrupts can be
specified via easy-to-use dialogs. You can also perform
service-based bypassing with the RTI Bypass Blockset
(p. 62).
2015
Introduction
Technical Details
Parameter
Specification
General
n
2 communication channels
Memory
n
16 K x 16 for each channel
n
16-bit word access, 8-bit low byte, 8-bit high byte
n
Bidirectional interrupts for synchronization of data transfer (for each channel)
Interrupts
n
Connection lost interrupt (for each channel)
Application Fields
n
16 subinterrupts (using RTI Bypass Blockset) via one interrupt line
n
FIFO-full and FIFO-empty interrupt (for each channel)
Target ECUs
n
Most kinds of 8-, 16- and 32-bit microprocessors
Communication with ECU
n
Two channels for connecting two ECUs or one dual-CPU ECU
n
Communication
between prototyping system and ECU via DPMEM plug-on

device (POD), on chip debug interfaces (e.g., use of Generic Serial interface
DCI-GSI1, p. 574) or an LVDS-Ethernet Link.
n
POD for SPI available
n
Customer-specific POD can adapt ECU signals to the DS4121 (PODs can be
integrated into the ECU enclosure)
n
Compatibility with PODs designed for MicroAutoBox
n
DS4121: twisted pair cable (CAT5 STP) suitable for close-to-engine location
Cabling
n
Full-duplex high-speed LVDS link (low-voltage differential signaling)
Transfer rate
n
250 Mbit/s LVDS interface between DS4121 and ECU
Software
n
DS4121-FX: connection between board and ECU via fiber-optic cable
Signaling system
n
80 Mbit/s effective data rate per channel in both directions
n
Host interface
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in.)
Ambient temperature
n
0 70 C (32 158 F)
Power supply
n
+5 V, 1.2 A
Hardware
Order Information
Product
Order Number
n
DS4121

Order Number
Included
n
ECU software porting kit
Required
n
Optional
n
RTI
n
RTI
Bypass Blockset (for service-based bypassing) n RTIBYPASS_BS

(p.62)
Order Number
n
Generic Serial Interface DCI-GSI1 (p. 574)
n
DCI-GSI1
n
Customer-specific Plug-On Devices (PODs) (p. 576)
Please inquire
n
LVDS-Ethernet Link cable
n
LVDS_CAB13/14
n
LVDS Link cable
n
LVDS_CAB2
2015
413
Hardware
Optional
Engineering
Software
Block Diagram
Processor
Board
PHS Bus
I/O Boards
PHS-Bus
Interface
Address
Register
Data
Register
Channel 1
DPMEM
16 K x 16
Channel 1
Reflective
Memory
Controller
High
Speed
Link
Channel 2
DPMEM
16 K x 16
Channel 2
Reflective
Memory
Controller
High
Speed
Link
POD
ECU
POD
ECU
Interrupt
Register
Power
Supply
DS4121
ISA Bus
414
PC
2015
Introduction
Software
Application Fields
Comprehensive Software Support

For service-based bypassing applications, the DS4121 can
be used together with the RTI Bypass Blockset and the
dSPACE Calibration & Bypassing Service. The service can be
integrated into the ECU code, and with the RTI Bypass
Blockset, you can easily access variables in the ECU via the
DS4121.
RTI Bypass Blockset:

Configuring bypass interfaces and
Hardware
bypass services for function prototyping.
Engineering
For address-based bypassing using PODs and for coupling

multiple real-time systems such as AutoBoxes, the DS4121
Blockset can be used.
Standard ECU Interface blockset
2015
415
fully integrated in MATLAB/Simulink.
Modular Hardware / DS4201 Prototyping Board

Integrates customized circuits into dSPACE systems
Highlights
n Provides all the required electronics for connection
to the dSPACE PHS bus
n Space for mounting custom devices
n Useful for additional I/O solutions
Technical Details
Parameter
Specification
Custom interface
n
Bidirectional buffered 32bit data bus
n
8 interrupt lines (programmable)
n
4 PHS bus address signals
n
13 predefined chip select outputs (for I/O ports)
n
1 board select signal; read/write signals; I/O signals
n
Up to 25 MB/s transfer speed
n
80pin custom connector
n
Power lines (ground, +5 V, +12 V, 12 V)
Timing
n
SYNCIN and SYNCOUT lines for input and output on several I/O boards
n
50pin male SubD connector for external devices
Host interface
n
One 16bit ISA slot
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in)
Custom board size
n
Up to 115 x 185 mm (4.5 x 7.3 in)
Ambient temperature
n
0 ... 70 C (32 ... 158 F)
Power supply
n
+5 V 5%, 500 mA (without custom module)
Order Information
Product
Order Number
n
DS4201
Relevant Software and Hardware for DS4201 and DS4201-S

Software
Order Number
Included
n
C library functions for serial communication (for DS4201S only)
Required
n
RealTime Interface (for DS4201S only) (p. 54)
n
RTI
n
Adapter cable with standard 9pin SubD (for DS4201S only)
n
SIO_CAB
Hardware
Optional
416
Order Number
2015
Modular Hardware / DS4201S Serial Interface Board
Introduction
DS4201S Serial Interface Board

Interface for serial communication between a dSPACE system and external devices
Application Fields
Highlights
Software
n Supports RS232, RS422, and RS485 line

transceivers
n Useful for connecting two systems over long
distances
Technical Details
Parameter
Specification
General
n
4 independent serial communication channels, each with a PC16550D UART (universal asynchro
nous receiver/transmitter)
n
Supported transceiver types: RS232C, RS422, RS485
Interrupts
n
Programmable interrupt control unit for up to 4 independent serial communication interrupts
Serial communication channels
n
4 RS232 transceiver channels
Hardware
n
RS422 and RS485 transceivers optional
n
Clock source: up to 24 MHz (optional for RS422 and RS485, custom clock source possible)
n
Modem control functions
RS232
n
1.8432 MHz clock: up to 115.2 Kbaud
n
24
RS422
n
n
24
MHz clock: up to 1.5 Mbaud
RS485
n
n
24
MHz clock: up to 1.5 Mbaud
Parity bits
n
Even, odd, or no parity
Stop bits
n
1, 1.5, or 2 bits
Word length
n
5, 6, 7, or 8 bits
FIFOs
n
16 byte input FIFO
MHz clock: up to 115.2 Kbaud

(limited by RS232 transceiver)
Engineering
Baud rate range
n
16 byte output FIFO
n
50pin male SubD connector
Host interface
n
One 8 or 16bit ISA slot (power supply only)
Physical
characteristics
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in)
Ambient temperature
n
0 ... 70 C (32 ... 158 F)
Power supply
n
+5 V 5%, 350 mA
Order Information
Product
Order Number
DS4201S Serial Interface Board

1)
1)
n
DS4201S
For information on relevant hardware and software see p. 416.
2015
417
n
+12 V 5%, 75 mA
Modular Hardware / DS4302 CAN Interface Board

Interface to CAN bus
Highlights
n Connects modular dSPACE systems to the CAN bus
n Features 4 CAN channels
Application Areas
The DS4302 CAN Interface Board has been designed to
operate in controller area network (CAN) environments as
used primarily in the automotive and automation industries.
Typical application fields of the DS4302 are:
n In-vehicle rapid control prototyping
n Hardware-in-the-loop tests
n Restbus simulation
n Automation tasks
Key Benefits
The DS4302 enables dSPACE systems to take part in CANbus traffic without the need for extra interface electronics.
Its three individual transceivers on each of the four independent channels cover almost all possible application areas.
They include a high-speed transceiver for hard real-time
communication and a fault-tolerant low-speed transceiver,
necessary for tasks such as comfort electronics. Every configuration of the DS4302 can be carried out in a Simulink
block diagram, thereby eliminating CAN controller programming.

With the RTI CAN Blockset, you can easily configure all CAN
interfaces in Simulink using a dialog-based method, without
any complicated CAN controller programming. The configuration options range from message setup to interrupt
configuration, right through to message time-stamping.
The easiest way is if you already have CAN-DB Editor files:
simply import them, and your CAN hardware is configured.
For efficient and dynamic handling of complex CAN setups
in hardware-in-the-loop (HIL) applications, we offer the RTI
CAN MultiMessage Blockset, which allows you to manage
large CAN message bundles (> 200 messages) from one
Simulink block.
418
2015
Introduction
Technical Details
Parameter
Specification
General
n
4 independent CAN channels
n
3 different on-board CAN transceivers per channel
n
Piggyback module socket for up to 4 customer-specific CAN transceivers
Processor
Slave DSP
Memory
On-board memory
n
TMS320VC33-150 from Texas Instruments (75 MHz, 150 MFLOPS, 75 MIPS)
n
Handles CAN controller communication
Application Fields
n
256 k x 32-bit SRAM
n
4 M x 32-bit flash memory
Dual port memory (DPMEM)
n
32 k x 32-bit dual-port memory (DPMEM) for communication between PHS-bus master
and slave DSP

n
CAN controller interrupt
n
PHS interrupt support
n
Various interrupt sources
Standards supported
n
CAN 2.0 A (standard frame format)
n
CAN 2.0 B (extended frame format)
n
ISO DIS 11898-2 high-speed CAN bus
n
ISO 11519-1 low-speed CAN bus, fault-tolerant
Transceiver chips
n
MAX3057 ISO11898 high-speed transceiver (up to 2 MBd), 80 V fault protected
n
TJA 1055 fault-tolerant low-speed transceiver supporting transmission rates up to 125 kBd
Software
On-board
CAN transceivers
n
SN75176 modified RS485 transceiver supporting baud rates up to 500 kBaud
n
Bus termination resistors (software selectable)
n
8 bidirectional I/O lines at customization module connectors
n
Full-CAN controller (BOSCH CC770)
Further details
n
Programmable controller clock
n
Host interface
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in.)
Ambient temperature
n
0 70 C (32 158 F)
Power supply (without piggyback

modules)
n
+5 V 5%, 1.2 A
n
+12 V 5% 20 mA
Hardware
Physical
characteristics
Order Information
Product
Order Number
n
DS4302
Order Number
Required
n
n
RTI
Optional
n
n
RTICAN_BS
n
n
RTICANMM_BS
n
Add-On: RTI CAN MultiMessage-J1939 Blockset
n
RTICANMM_J1939_BS
For connection of dSPACEs modular hardware

to a CAN FD bus system, see p. 424.
2015
419
Software
Engineering
Relevant Software
Block Diagram
Processor
Board
PHS Bus
I/O Boards
CAN 4
...
CAN 1
CAN
Controller
CC770
PHS-Bus
Interface
32k x 32-bit
DPMEM
TMS320VC33
DSP
Interrupt
Controller
Interrupt
Controller
ISO 11898
RS485
Channel 4
.
.
.
Channel 1
Fault-Tolerant
4M x 32-bit
Flash ROM
Power
Supply
256k x 32-bit
SRAM
Piggyback
Module
Termination
Resistor
DS4302
ISA Bus
420
PC
2015
Modular Hardware / DS4330 LIN Interface Board
Introduction
DS4330 LIN Interface Board

Interface to LIN bus
Application Fields
Highlights
Application Areas in
Hardware-in-the-Loop Simulation
Using dSPACE Simulator and a DS4330, you can test the
LIN network features of an electronic control unit. The
dSPACE system simulates the LIN nodes, which are connected to the LIN bus. The simulated LIN nodes behave in
exactly the same way as real bus members (restbus
simulation).
Test Scenarios
The DS4330 can be used in many different ways. Several
test scenarios are possible:

The DS4330 provides a LIN interface for the connection of
dSPACE systems to LIN buses. You can set up and control
these simulated LIN buses with the RTI LIN MultiMessage
Blockset (p. 73).
The RTI LIN MultiMessage Blockset (supporting LIN standards
1.3, 2.0, 2.1 and 2.2) is an extension for Real-Time Interface
and can be used for combining dSPACE systems with LIN
communication networks and for configuring these LIN networks. With the RTI LIN MultiMessage Blockset you can
handle complex LIN setups, which lets you control and configure all unconditional and event-triggered LIN frames from
one single Simulink block (configuration via database file).
2015
421
n Testing the transmission of message frames

n Testing communication timing constraints
n Testing against specification limits
n Testing diagnostic and failure conditions
n Testing energy-saving modes
Engineering
Hardware
Application Areas in Rapid Control Prototyping

The DS4330 and the corresponding software can be used
for developing and testing electronic control units (ECUs)
which communicate with LIN actors and sensors. For rapid
control prototyping purposes laboratory-based or vehiclebased real LIN slaves can be connected to the prototyping
system that simulates the ECU under development as the
master node.
Software
n LIN master and slave support

n 16 independent LIN channels
n Up to 16 LIN nodes per LIN channel
n Supports LIN 1.3, 2.0, 2.1 and 2.2
Technical Details
Parameter
Specification
General
n
16 independent LIN channels
n
One on-board LIN transceiver per channel
n
Simulation of up to 16 LIN slaves per LIN channel
n
Software-selectable individual baud rates from 1000 baud up to 20 kBd for each channel
n
Piggyback module socket for up to 16 custom LIN transceivers
n
Transmitting and receiving LIN data from within a Simulink model
Processor
Slave DSP
Memory
On-board memory
n
IBM PowerPC 405CR, 200 MHz
n
PowerPC can boot from DPMEM or flash memory (selectable by software)
n
64 MB SD-RAM, 100 MHz
n
8 MB flash memory
Dual port memory (DPMEM)
n
32 k x 32 bit dual-port memory for communication between PHS bus and slave
processor
n
UART interrupt for each LIN channel
n
LIN transceiver wake-up interrupt for each LIN
channel
n
All interrupts can be enabled/disabled separately by software
On-board LIN transceiver
Transceiver chip
n
Infineon TLE6259
n
Integrated pull-up resistors for TXD and RXD lines
n
On-chip termination resistor for LIN slave applications
n
2
Further details
additional bidirectional I/O lines per channel at customization module connectors

for general purposes
n
Thermally protected
n
External 1 k termination resistor for using the LIN channel as a master
(selectable via software)
n
Host interface
Physical size
n
340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in.)
Ambient temperature
n
0 70 C (32 158 F)
Power supply
n
+5 V 5%, 1.5 A
n
+12 V 5%, 750 mA (supplies the VCC12 pin on the interface connector only)
Order Information
Product
Order Number
DS4330 LIN Interface
n
DS4330
Relevant Software
Software
422
Order Number
Required
n
n
RTI
Optional
n
n
RTILINMM_BS
2015
Application Fields
Introduction
Software
The strong point of the RTI LIN MultiMessage Blockset

is handling complex LIN setups, allowing you to control
and configure all unconditional and diagnostic LIN frames
from one single Simulink block.
Block Diagram
Engineering
Hardware
I/O Boards
2015
423
PC
Modular Hardware / DS4505 Interface Board

Interface to FlexRay or CAN FD bus
Highlights
Connects dSPACEs modular hardware to
a FlexRay or a CAN FD bus system via additional
interface modules
n Supports up to 4 interface modules
n NEW: DS4342 CAN FD Interface Module (p. 427)
n
424
Application Area
The DS4505 Interface Board allows a dSPACE system with
modular hardware to be connected to a FlexRay and/or a
CAN FD communication system. It is ideally suited for testing applications with a dSPACE prototyping system or
Simulator. The board can carry up to four interface modules.
Key Benefits
There are two additional interface modules for the DS4505
Interface Board: the DS4340 FlexRay Interface Module (p.
426) for connection to FlexRay buses and the DS4342 CAN
FD Interface Module (p. 427) for connection to CAN FD
buses. The modular structure enables the use of both modules on one DS4505 simultaneously.
FlexRay Basics
FlexRay is a time-triggered communication system for
in-vehicle applications with demanding communication
needs. It is the standard for deterministic, high-performance
automotive communication networks. The basic principle
of time-triggered systems is that tasks are executed and
messages are sent according to a predefined schedule. In
FlexRay, activities are aligned to a global time base, whereas in nondeterministic communication protocols such as
CAN, they are mainly event-triggered at run time.
CAN FD Basics
The CAN FD (FD = Flexible Data Rate) protocol was introduced to enhance the classic CAN protocol in terms of data
rates and payload data length. With CAN FD, a multiplied
data rate allows an average data transmission speed of
several Mbit/s and payload lengths of up to 64 bytes (compared to 8 bytes in a classic CAN).
2015
Introduction
Technical Details
Parameter
Specification
General
n Access to a FlexRay or CAN FD communication bus from a test system or prototyping platform
n Supports the DS4340 FlexRay Interface Module (p. 426) and the DS4342 CAN FD Interface Module (p. 427)
n Provides 4 slots (for DS4340 or DS4342)
n Supports high-performance interfaces via a PHS++ bus
n Sub-D 50 connector to connect an external FlexRay or CAN FD bus with DS4505
Physical
characteristics
Physical size
n Full length ISA board, 340 x 125 x 15 mm (13.4 x 4.9 x 0.59 in)
Ambient temperature
n 0 ... 70 C (32 ... 158 F)
Power supply
n +12 V 5%, 20 mA (if 4 interface modules are inserted)
Application Fields
n One 8-bit or 16-bit ISA slot (for power supply only)
Host interface
n +5 V 5%, 150 mA (if no interface modules are inserted)

n +5 V 5%, 650 mA for DS4505 carrying 1 module (total power consumption depends on inserted modules)
Order Information
Order Number
n DS4505
Software
Product

Order Number
Included
Required
n RTI
n FCP
dSPACE RTI CAN MultiMessage Blockset (p. 70)
n RTICANMM_BS
Hardware
n DS4340
NEW: DS4342 CAN FD Interface Module (p. 427)
n DS4342
FlexRay Interface Cable for DS4505
n FR_CAB2
Engineering
Optional
Order Number
DS4340 FlexRay Interface Module (p. 426)
2015
425
Required
Hardware
Software
DS4340 FlexRay Interface Module

Module for interfacing to FlexRay buses
The FlexRay Interface Module can be used with the DS4505
Interface Board or MicroAutoBox II 1401/1505/15071),
1401/1507, 1401/1511/1512 or 1401/1512/1513. The module supports FlexRay protocol specification 2.1 and offers
downward compatibility to previous standards. It provides a
hardware-configurable, switchable termination circuit.
The dSPACE FlexRay Configuration Package (p. 76) is used
to integrate dSPACE hardware as simulation or monitoring
nodes in a FlexRay network.
Parameter
Specification
General
n
Supports FlexRay protocol specification 2.1
n
Supports the DS4505 Interface Board or MicroAutoBox II 1401/1505/15071), 1401/1507, 1401/1511/1512 and 1401/1512/1513
n
Automatic detection of Industry Package (IP) for MicroAutoBox and DS4501 or fast COM mode (depending on the carrier board)
n
Molex connectors for direct access to FlexRay bus lines
n
Switchable termination circuit (hardware-configurable)
n
Feed-through possibility for FlexRay bus lines in passive-linear-bus topology
n
Two FlexRay channels
Hardware
Details
n
Freescale MFR43xx Communication Controller Family
n
Dual PHY Interface with TJA1080
n
For wake-up, hardware modification of MicroAutoBox and DS4340 is required.2)
n
Requires one slot
Can also be used with MicroAutoBox 1401/1505/1506 or DS4501 IP carrier board.

For more information, please contact dSPACE.
1)
2)
426
2015
Introduction
NEW: DS4342 CAN FD Interface Module
Parameter
Specification
General
n
2 CAN/CAN FD channels
Application Fields
Module for Interfacing to CAN FD buses

The dSPACE DS4342 CAN FD Interface Module (FD = Flexible
Data Rate) can be used with the DS4505 Interface Board or
MicroAutoBox II 1401/1505/1507, 1401/1507, 1401/1511/1512
or 1401/1512/1513. The DS4342 provides two independent
CAN channels, each of which can be used for CAN FD or
for CAN. Network management functions such as wake-up
and sleep are also included.
n
Supports the DS4505 Interface Board and MicroAutoBox II 1401/1505/1507, 1401/1507, 1401/1511/1512 and 1401/1512/1513
n
Automatic detection of Industry Package (IP) for MicroAutoBox 1507 or fast COM mode for MicroAutoBox 1512 and DS4505 carrier board
n
Support by RTI CAN MultiMessage Blockset
n
Capable for ISO 118985 network management
Software
n
Capable for handling ISO 118982 CAN or CAN FD on every channel
n
NXP TJA1145T CAN Transceiver
Engineering
Hardware
n
Requires one slot
2015
427
Hardware
Details
Modular Hardware / DS5001 Digital Waveform Capture Board

Capturing digital signals
Highlights
Captures digital signals for parameter evaluation
n Standard functions for pulse analysis such as PWM
measurement included
n Ideally suited to control and hardware-in-the-loop
applications in automotives and drives
n
Application Areas
The application area of the DS5001 Digital Waveform Capture Board ranges from automotives through drives to robotics. The DS5001 is in active use in many hardware-in-theloop and rapid control prototyping applications. It can be
connected to the Engine Position Bus of the DS2211 HIL I/O
Board (p. 386). This allows you to perform angle-synchronous signal capturing, with the DS5001 as either a time-base
slave or the master. The board can also be connected to the
time-base connector of the DS4002 Timing and Digital I/O
Board or other DS5001 boards, and itself function as a
time-base master for other boards.
Key Benefits
Capturing digital signals is a part of most control and hardware-in-the-loop applications. However, with ordinary
timing I/O, the speed, resolution, or number of channels
often is not sufficient. And typically, complicated analysis
algorithms are required and these usually have to be programmed in assembler language, which most users would
prefer to avoid.
You can overcome these limitations with the DS5001. The
board records digital signals at high speed for extremely
flexible evaluation of frequency, phase, duty cycles, and other
signal parameters.
Further Functions
The DS5001 Digital Waveform Capture Board includes
16 input channels that let you capture digital signals with
a resolution of 25 ns. The board sees each signal as a series
of rising and falling edges. The time stamp and polarity of
each edge are stored. A processor board can use this data
to perform any analysis you need. Event counters and
sophisticated interrupt mechanisms enable you to evaluate
not only frequencies and phases, but also signal characteristics such as jitter and missing pulses.
428
2015
Introduction
Technical Details
Parameter
Specification
General
n
16 timing I/O channels (inputs)
n
Event storage with dual-port memory (DPMEM) and first-in-first-out memory (FIFO)
n
n
Time-base connector
n
Interrupt on predefined number of events
Application Fields
n
Interrupt on event buffer full
Time resolution
n
25 ns
Sampling rate
n
Max. 40 MHz
Input frequency
n
Max. 20 MHz
Pulse-width range
n
25 ns 53.68 s
Edge detection
n
Separate edge detector for each channel
Detection type
n
Programmable rising and/or falling edge detection
Input voltage range (trigger level)
n
10 V (programmable)
Input voltage protection
n
35 V (continuous)
Hysteresis
n
80 mV 2.8 V (selectable)
Input impedance
n
>12 k / 5 pF
Edge detection
Software
n
Interrupt on input FIFO full
Timing I/O channels
n
Rising and/or falling edge detection (programmable)
n
Trigger level -10 +10 V (programmable in 256 steps)
n
Dual-port RAM stores up to 512 events per channel
Event storage
n
Events include 31-bit time stamp and edge polarity
n
Access to event storage from processor board
n
3 up counters (32-bit)
Event counters
n
Each counter can be assigned to any channel
n
Counter read and reset from processor board
n
Host interface
n
Physical size
n
340 x 114 x 20 mm (13.4 x 4.9 x 0.8 in)
Ambient temperature
n
0 70 C (32 158 F)
Power supply
n
+5 V 5%, 2.5 A
Hardware
Physical
characteristics
Order Number
n
DS5001
2015
429
Product
Engineering
Order Information

Software
Order Number
Included
n
C functions for accessing/controlling the DS5001 (provided with the processor board)
n
Standard functions for pulse analysis (provided with the processor board), such as:
n PWM duty cycle analysis,

n Frequency measurement,
n Phase measurement
n Incremental encoder input
n Real-Time Interface (p. 54)
Required
n
RTI
Hardware
Order Number
Optional
n Connector Panel for DS5001 (p. 480)
n CP5001
Block Diagram
Processor
board
PHS bus
PHS-bus
interface
Interrupt
controller
Timing I/O Unit
Counter A
Counter B
I/O boards
Time
base
Further
DS5001/
DS2211/
DS4002
Time-base
connector
Counter C
16
...
1
Controller
FIFO
FIFO
Edge
detector
Comparator
Input
protect.
Chan. 16
.
.
.
Chan. 1
Trigger level
select
Dual-port
memory
Power
supply
DS5001
ISA bus
430
PC
2015
Introduction
Application Fields

Real-Time Interface provides Simulink blocks
for the convenient configuration of PWM
analysis, incremental encoder input and read
operations, frequency measurement, and
event counters. For example, the PWM dialog
lets you enter the desired trigger levels and
number of periods to include.
Channel 1...16
Hardware
Wheel Speed Measurement

Automotive control is a typical application field for the
DS5001 Digital Waveform Capture Board. In the example
shown here, the DS5001 board measures wheel speeds for
the rapid control prototyping of an ABS control unit. The
wheel speed sensor electronics provide a digital signal with
a frequency proportional to the speed. To calculate the
speed, the processor board needs the exact times, polarities,
and number of wheel speed sensor events that occurred
during the last simulation step. The DS5001 board detects
each event and stores its time and polarity. You can easily
determine the exact wheel speed with the included
frequency analysis functions. Since the DS5001 board stores
a complete event history, it is easy to apply special algorithms
for improved measurement quality, such as averaging the
last n pulse periods, where n can be variable.
Software
Application Example
CH 1
...
t1
t3
t5
t8
t10
t12
t13
CH 16
t2
t4
t6
t7
t9
t11
Edge Detect
Channel
1...16
CH
CH 1
1
tt1
1
tt3
3
tt5
5
tt8
8
tt10
10
tt12
12
tt13
13
Engineering
...
...
CH 16
16
CH
tt2
2
tt4
4
tt6
6
tt7
7
tt9
9
Edge Detect
Event RAM
...........................
Channel 1
CH 1
t1
t1
t3
t5
t8
...t3
t5
CH 16
t8
t2
t4
t6
t7 t9
t10
t12
t13
...........................
Event RAM
Channel 1
t1
t3
t5
t8
t10
t12
t13
...........................
tt11
11
Channel 16
t2
t10
t4 t12 t13
t6
t7
t9 t11
t11
Channel 16
t2
t4
t6
t7
t9
t11
dSPACE GmbH Rathenaustrae 26 33102 Paderborn Germany info@dspace.de

........................... www.dspace.com
2015
431
Capturing Events
Each input signal is captured with its own edge detector,
including programmable edge enables and trigger level. The
times and polarities of the detected events are stored separately for each channel in an event buffer in dual-port RAM.
You can then use this data to perform analysis on the processor board.
Modular Hardware / DS5101 Digital Waveform Output Board

For generating pulse patterns
Highlights
n Generates digital pulse patterns autonomously
n 25 ns resolution on 16 channels
n Standard pulse patterns such as PWM included
Application Areas
Digital pulse patterns are required in almost any control
application. The demands made on PWM resolution and
flexibility are very high, especially in drives control. With
ordinary timing I/O, you come up against the limits very
quickly. Digital signals in automotive applications usually
require less resolution, but the demands on flexibility can
nevertheless be high, for example, for the simulation of
crankshaft signals.
Key Benefits
The DS5101 autonomously generates any TTL pulse patterns
on up to 16 channels with high accuracy. With a time
resolution of 25 ns, the DS5101 meets even the toughest
requirements. The ability to change pulse widths in real time
combined with various trigger and interrupt mechanisms
give the DS5101 board unbeatable flexibility and programmability.
Pulse Pattern Library

A library with standard pulse patterns is supplied. However,
you can also program your own pulse patterns in an
intuitive high-level language.
n 1-phase PWM
n 3-phase PWM
n 3-phase/6-channel PWM (includes converted signals)
n Incremental sensor simulation
n Monoflop signal generation
432
2015
Introduction
Technical Details
Parameter
Specification
General
n
16 timing I/O channels
n
External reset input
n
Memory
n
DPMEM for program (states) and data (delays)
n
Stores 512 delay parameters (30 bits) and 128 program states (90 bits) for each channel
Application Fields
n
All timing I/O channels share a single physical interrupt to the processor board. Any channel
can generate an interrupt. Interrupt arbitration is performed by software.

n
Interrupt on external reset
Timing I/O channels
Time base
n
25 ns time resolution
n
40 MHz internal or 20 ... 40 MHz external common time base
n
2 MHz maximum output frequency
n
250 ns ... 26 s pulse widths
n
Mutual triggering of all channels
Triggering
n
TTL input/output level
Output current
n
Max. -15 mA/+64 mA
External reset input
n
TTL input level
n
Host interface
Physical
characteristics
Software
n
Output channels configurable as input channels for trigger signals
Voltage range
n
Physical size
n
340 x 125 x 20 mm (13.4 x 4.9 x 0.8 in)
Ambient temperature
n
0 ... 70 C (32 ... 158 F)
Power supply
n
+5 V 5%, 0,5 A
Product
Order Number
n
DS5101
Hardware
Order Information
Required
n
n
Intuitive high-level language for programming pulse patterns
n
n
RTI
n
n
CP5101
Hardware
Optional
n
Standard pulse patterns
Order Number
2015
433
Included
Order Number
Engineering
Software
Block Diagram
Processor
board
PHS bus
I/O boards
PHS-bus
interface
Channel 16
...
Interrupt
control
unit
Channel 16
Channel 1
Swinging
buffer
controller
Channel 1
Controller
Reset
logic
Dual-port
memory
Software
trigger / flag
unit
External
reset input
Power
supply
DS5101
ISA bus
434
PC
2015
Introduction
Working with the DS5101

n Conditional branching
n Synchronized update of parameters in real time
n Interrupt generation
Application Fields
Programming Language
n Intuitive high-level language
n Mutual triggering of all channels
n Loop counter
Definition
CH
Defines the current output channel for all states to follow.
DECCTR
Decrements the 8-bit channel loop counter.
DELAY
Defines a delay constant that defines the time after which the next state will be executed.
GOTO
Causes the current channel to continue execution at a state defined by a label.
IF ... ELSE
Allows conditional branches on flags, loop counter, or other channel I/O.

Loads the 8-bit channel loop counter with a specified value.
LOOP
Causes the current channel to continue execution with the first state.
LPHSINT
Generates an interrupt to the processor board.
RESET
Sets the output level low.
SET
Sets the output level high.
SYNCEN
Updates all delay constants simultaneously.
TOGGLE
Changes the basic time unit for all delays.
TR
Triggers other channels to proceed to their next state.
UNIT
Defines the basic time unit for all delays.
WAIT
Causes the current channel to wait for a trigger event before proceeding to the next state.
2015
435
Engineering
LDCTR
Hardware
Command
Software
List of Commands (Excerpt)
Use Case: Incremental Encoder Simulation

Generating Sensor Signals
A typical application is the generation of sensor signals, for
example, for hardware-in-the-loop simulations. The incremental encoder simulated in the first example can be used
for any number of lines per revolution. The output signals
are phi_0 (channel 1) and phi_90 (channel 2). Each period
is divided into four sections to ensure synchronous operation, for example, when the rotation speed is changed.
Controlling the Simulation

As you can see from the program listing below, controlling
the simulated rotation is an easy task. To change the direction, just set or reset flag 1. In this simulation, the direction
changes after 2000 time units. The speed can be influenced
simply by increasing or decreasing the delay t_enc.
Program listing for an example of sensor signal generation.
436
2015
Introduction
Connection to the Processor Board

The processor board transfers new parameters to a buffer
on the DS5101 board, and all new parameters become
effective simultaneously. This occurs once at the beginning
of each loop on channel 1. The wait statement switches a
channel to idle state until another channel sends a trigger
with the trx command.
Various Commands
In the example, the master clock on channel 1 sends triggers
to channels 2 and 3. The phsint command generates an
interrupt on the processor board, for example, to sample
analog inputs and execute the controller code. In the

example, phsint is executed once in a loop on channel 1.
Program listing
for a PWM signal
generation example.
2015
437
Engineering
Hardware
Software
Generating Digital Signals

The simulation result below shows the generated digital
signals for the two switches of a 1-phase PWM inverter. The
PWM carrier frequency selected is 10 kHz. Any other frequency could be chosen by modifying the delay t_master
in the program. The specified delays can be overwritten at
any time by applying the syncen mechanism.
Application Fields
Use Case: PWM Generation
Modular Hardware / DS5203 FPGA Board
DS5203 FPGA Board

FPGA programmable per application
Highlights
n Completely user-programmable via the RTI FPGA
Programming Blockset (p. 86)
n Utilizes the Xilinx System Generator (XSG) Simulink
Blockset
n Offline simulation in Simulink
n Basic set of I/O drivers on-board, I/O extendable
by piggyback modules
438
Application Areas
The DS5203 FPGA Board can be adapted to various tasks,
so you can react flexibly to tougher requirements, such as,
signal conditioning, using new interfaces, or speeding up
model parts. FPGAs are especially useful for relieving the
processor board of tasks such as signal preprocessing
during ECU development. Running at 100 MHz, the DS5203
board is ideal for application fields like engine knocking,
cylinder pressure analyses and electric drive projects. The
DS5203 works closely together with the XSG model library
(p. 249).
Key Benefits
A field-programmable gate array (FPGA) is a semiconductor
device consisting of logic elements that you can configure.
The DS5203 FPGA Board features a powerful, freely programmable FPGA, the Xilinx Virtex-5. In addition, it offers
6 ADC, 6 DAC and 16 digital I/O channels, and connection
to the processor board via PHS bus. The number of I/O
channels can be increased by piggyback modules.
Programming via the RTI FPGA Programming

Blockset
The DS5203 FPGA Board is programmed via the RTI FPGA
Programming Blockset (p. 86) from dSPACE and the Xilinx
System Generator. These let you develop applications for
the processor board and the DS5203 together. You can test
the interaction between the processor application and the
FPGA application in offline simulation before implementing
them on the real-time hardware. This lets you react flexibly
to new requirements such as new interfaces or having to
accelerate the execution of submodels.
You can also use the RTI FPGA Programming Blockset Handcode Interface to program the DS5203.
Two Variants
The DS5203 is available with two different FPGAs:
n The DS5203 LX 50 includes a Xilinx Virtex-5 LX50T-1C
FPGA, consisting of 46080 logic cells and 48 special
DSP blocks. This board offers a cost-effective solution
for smaller applications and starter systems.
n The DS5203 SX95 includes a Xilinx Virtex-5 SX95T-2C
FPGA, consisting of 94298 logic cells and 640 special DSP
blocks. The large amount of DSP blocks help by performing tasks such as fast, resource-saving multiplication.
2015
Introduction
Technical Details
Specification
Parameter
DS5203 LX50
DS5203 SX95
General
FPGA
n Xilinx Virtex-5 LX50T-1C
n Xilinx Virtex-5 SX95T-2C
n Logic cells: 46080 (Virtex-5 slices: 7200;
n Logic cells: 94298 (Virtex-5 slices: 14720;
DSP slices: 48)

n Distributed RAM:480 kbit
n Block RAM:2160 kbit
n Distributed RAM:1520 kbit
n
Only ISE
Device timing
n 100 MHz
Digital I/O
Application Fields
Xilinx software support
DSP slices: 640)

n Block RAM:8784 kbit
Input

n Digital input: Threshold adjustable for each channel from 1 V to 7.5 V
Analog I/O
Output
n Digital output: Push-pull drivers; one output voltage can be selected for all channels: 3.3 V or 5 V
Input
n 6 channels
n Resolution: 14 bit pipelined
n Sampling rate: 10 Msps
Software
Output
n 6 channels
n Resolution: 14 bit
n Update rate: 10 Msps
n Slot for one I/O module for extending the analog and digital I/O (p. 441)
Further interfaces
n Connection for the APU (angular processing unit) bus

n 2 connectors for inter-FPGA communication
n 340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in)
Ambient temperature
n 0 ... 55 C (32 ... 131 F)
Power supply
n +5 V 5%, 2.5 A
Hardware
Physical size
n +12 V 5%, 0.7 A

n -12 V 5%, 0.1 A
Inter-FPGA Communication
The DS5203 FPGA Board provides two inter-FPGA-communication connectors. Together, the two connectors provide
a 32-bit parallel data bus. Inter-FPGA communication allets
the user exchange data directly between two FPGA boards
without a detour via the PHS bus and the processor board.
One FPGA application can be triggered by another, that is
located on another FPGA board, e.g., to synchronize the
applications.
2015
Engineering
High-Precision Engine Angle Computation

During hardware-in-the-loop simulation, the DS5203 provides a connection for an APU (angular processing unit)
bus in addition to the user-programmable FPGA. The APU
calculates the engine angle with high precision as a basis
for providing I/O values to the HIL simulation.
The DS5203 can be used as a master or a slave. When it is
the APU master, the angle values for the simulation model
are computed and used on the FPGA itself, and, if necessary, transmitted to other I/O boards via the APU bus. As
the APU slave, it receives the engine angle values from another dSPACE I/O board, such as the DS2211 HIL I/O Board
(p. 386). The angle data can then also be used in the simulation models running on the DS5203.
439
Order Information
Product
Order Number
DS5203 FPGA Board (LX50)
n DS5203_LX50
DS5203 FPGA Board (SX95)
n DS5203_SX95

Software
Required
Order Number
n RTI
n RTI FPGA Programming Blockset FPGA Interface (p. 86) or
n RTIFPGA_BS
n RTI FPGA Programming Blockset Handcode Interface (p. 87)
n RTIFPGA_HC
n Xilinx ISE Foundation and System Generator for DSP1)
Optional
n XSG_ELECTRIC_BS
n XSG Utils Library (p. 94)
n FPGA_XSG_UTILS
n XSG ACMC Library (p. 96)
n FPGA_XSG_ACMC
Hardware
Optional
n XSG Electric Components Library (p. 249)
Order Number
n DS5203M1 Multi-I/O Module (p. 441)
n DS5203_M1
n EV1099: Resolver SC Module for DS5203 (p. 441)
n EV1099
n DS5203 Inter-FPGA Communication Cable
n DS5203_CAB1
Please note that due to the introduction of the Vivado software, Xilinx no longer supports the Xilinx System Generator for DSPs in combination
with the ISE Design Suite after MathWorks MATLAB and Simulink Release R2013b.
1)
440
2015
Introduction
DS5203M1 Multi-I/O Module
Application Fields
The DS5203M1 Multi-I/O Module is a piggyback module

for the DS5203 FPGA Board. It extends the available digital
and analog I/O to give you more flexibility.
Technical Details
Parameter
Specification
Digital I/O
Input

n Threshold for each channel adjustable from 1 V to 7.5 V
n Push-pull drivers
Software
Output
n One output voltage can be selected for all channels: 3.3 V or 5 V
Analog I/O
Input
n 6 channels
n Resolution: 14 bit pipelined
n Sampling rate: 10 MSPS
Output
n 6 channels
n Resolution: 14 bit
n Update rate: 10 MSPS
Sensor supply
n Adjustable
Hardware
n Output voltage range: 2 V to 20 V
EV1099: Resolver SC Module for DS5203
Engineering
The module can be installed in a dSPACE Simulator Full-Size

or Mid-Size. It is connected via ribbon cable to the DS5203
or DS5203M1, which are pin-compatible.
Additional features:
n Configurable audio transformer for each of the 6 DAC
channels
n Switchable 220 resistor for each of the 6 ADC
channels
2015
441
The EV1099 Resolver SC Module is a transfer element for the

DS5203 FPGA Board or the DS5203M1 Multi-I/O Module.
It offers special signal conditioning for electric drive applications, such as transformers for resolver simulation.
Modular Hardware / SCRAMNet+ Interface
SCRAMNet+ Interface
Interface to SCRAMNet+ networks
Highlights
n Connects dSPACE systems to SCRAMNet+ networks
n Provides standard SCRAMNet+ fiber-optic connections
n Supports standard features of SCRAMNet+
n RTI SCRAMNet+ Blockset for MATLAB/Simulink
442
Application Areas
This interface allows dSPACE Simulators to be integrated in
existing simulator environments where SCRAMNet+ (Shared
RAM Network) is the chosen node-to-node communication
standard. It enables dSPACE prototyping systems to be the
platform for distributed control systems and helps you
satisfy high-speed requirements when developing real-time
applications. SCRAMNet+ is ideally suited to applications
including simulation, telemetry, robotics, data acquisition,
instrumentation, industrial process control, digital video,
and virtual reality.
Key Benefits
With a SCRAMNet+ Interface, dSPACE Simulators and RCP
solutions can take advantage of the very high speed and
deterministic performance of shared memory in a SCRAMNet+ network. SCRAMNet+ interfaces are available for
various bus architectures such as VME, PCI, PMC, and
CompactPCI, so dSPACE systems can integrate with nondSPACE systems at high speed and in real time. Since this
interface can share data and interrupts, accurate real-time
synchronization can be achieved between dSPACE and nondSPACE systems. Data and interrupts are communicated at
memory speeds, a huge improvement over typical messagepassing networks. The result is interprocessor communication that is 100% deterministic and very low-latency.
SCRAMNet+ Network
The SCRAMNet+ network is an ultra-fast data communication system designed for use in real-time computer systems.
SCRAMNet+ is optimized for the high-speed transfer of
small packets of data between computers when lowlatency data transmission and precise timing are critical.
SCRAMNet+ Blockset
A special SCRAMNet+ Blockset for MATLAB/Simulink is available for the SCRAMNet+ Interface board. The blockset serves
as a graphical interface that allows you to configure the
SCRAMNet+ node, read from and write to the SCRAMNet+
shared memory, and handle interrupts, both memory- and
error-based. This blockset gives you the ability to read and
write to SCRAMNet+ memory in two ways: by specifying a
starting address and the number of consecutive values to
read or write, or by entering one or more addresses as an
array that does not have to be sequential.
2015
Introduction
Modular Hardware / SCRAMNet+ Interface
Technical Details
Parameter
Specification
General
n
Standard fiber-optic media connectors
n
1 MB shared SCRAMNet+ memory
n
Auxiliary connector for Fiber Optic Bypass Switch
n
Supports all standard SCRAMNet+ features
Application Fields
n
Status LEDs
Software support
n
Multiple protocol support:
n
Burst
n
Burst Plus
n
Platinum
n
Platinum Plus
n
Network timeout support
n
Write-me-last mode support
n
Control of Fiber-Optic Bypass Switch
n
Read and write access to entire 1 MB memory
n
Data type handling
Software
n
Network interrupt generation
n
Incoming network interrupt handling
n
Error interrupt generation and handling
n
Memory interrupt generation and handling for each 32-bit location
n
Virtual paging (ability to integrate with any memory configuration)
Supported standards
n
SCRAMNet+
Host interface
n
One 8- or 16-bit ISA slot (for power supply only)
Physical size
n
Full-length ISA board
Ambient temperature
n
0 +70 C (32 158 F)
Power supply
n
+5 V 5%, 1.36 A
Hardware
Physical
characteristics
Order Information
Product
Order Number
SCRAMNet+ Interface Board
Please inquire
Software
Order Number
Included
n
RTLib C driver library
Required
n
n
RTI
n
RTI SCRAMNet+ Blockset
Please inquire
Order Number
n
DS4503 carrier board
n
1 MB SCRAMNet+ rehostable module
n
Standard Fiber Optic Media Card module
2015
443
Hardware
Included
Engineering
Modular Hardware / PROFIBUS Interface
PROFIBUS Interface
Interface to a PROFIBUS communication bus
Highlights
n Connects dSPACE systems to the PROFIBUS Network
n Dual-port memory for data exchange with processor
board
n Master or slave PROFIBUS modules available
n Communication without load on the host system
Application Areas
Processing closed-loop and open-loop control information
for machinery and systems with the aid of powerful microchips is widespread in modern automation technology. As
a rule, the processors are connected by one or more communications networks. The PROFIBUS interface connects
dSPACE Simulator and dSPACE prototyping systems to
PROFIBUS networks to develop controller technologies for
factory automation, decentralized peripherals, and motion
control, for example.
Key Benefits
The PROFIBUS Interface is equipped with the PHS++ bus
interface and can therefore communicate with the dSPACE
modular hardware at very high speeds. The maximum
possible baud rate for PROFIBUS communication is 12 Mbaud.
A sample setup with a ControlDesk experiment comes with
the interface to explain the basic implementation of dSPACE
modular hardware in PROFIBUS environments.
PROFIBUS
The PROcess-FIeld-BUS is a vendor-independent, open field
bus standard for a wide range of applications in manufacturing and process automation. Vendor independence and
openness are ensured by the international standards
IEC 61158 and IEC 61784. PROFIBUS allows communication
between devices from different manufacturers without any
special interface adjustment. PROFIBUS can be used for both
high-speed time critical applications and complex communication tasks. It utilizes a nonpowered two-wire (RS485)
network and can have up to 126 nodes.
444
2015
Introduction
Modular Hardware / PROFIBUS Interface
Technical Details
Parameter
Specification
General
n
Direct connection to the field bus
n
Communication without load on the host system
n
Dual-port memory for data exchange with processor board
n
9-pin Sub-D connector for connection to PROFIBUS
Application Fields
n
C device driver functions for communication
n
PROFIBUS access and message composing via S-functions, based on dSPACE
examples
Technical data
Free potential
n
RS485
Transmission rate
n
12 Mbaud
Diagnostic interface
n
RS232C, nonisolated
Supported standards
n
PROFIBUS
n
Host interface
Physical size
n
Ambient temperature
n
0 +55 C (32 131 F)
Power supply
n
+5 V 5%, 0.7 A
Software
n
12 V 5%
Order Information
Product
Order Number
PROFIBUS Interface
Please inquire
Software
Hardware

Order Number
Included
n
Hilscher SyCon configuration software
Required
n
dSPACE Software Release with RTI1)
n
dSPACE PROFIBUS Solution1) (DS1005, DS1006, DS1007)
Included
Order Number
n
DS4502 carrier board
n
Hilscher Module COM-PB (master) or COM-DPS (slave)
Engineering
Hardware
n
DS4502
2015
445
1)
Modular Hardware / Interface to MILSTD1553
Interface to MILSTD1553
Interface to MILSTD1553 networks
Highlights
Connects a modular dSPACE real-time system
to a MIL-STD-1553 network
n For hardware-in-the-loop simulation and rapid
control prototyping
n Supports MIL-STD-1553B
n Comprehensive Simulink Blockset
n
Application Areas
The interface to MIL-STD-1553 connects a modular dSPACE
real-time system to a MIL-STD-1553 network. It is used in
hardware-in-the-loop (HIL) simulation and rapid control
prototyping (RCP) to test and develop control systems that
use MIL-STD-1553. Examples are HIL simulation for satellite
avionics integration testing and component validation of
aircraft flight surface actuator and engine controllers
(FADECs). This interface is based on the industry-proven
QPC-1553 module from GE Intelligent Platforms.
Hardware and Software

The interface is based on the DS4504 PMC Carrier Board,
which acts as a carrier for an Embedded Technology
eXtended (ETX) module and a MIL-STD-1553 PCI Mezzanine
Card (PMC). Data exchange between the ETX and the
dSPACE processor board runs via the PHS++ (peripheral
446
Key Benefits
The interface to MIL-STD-1553 enables you to connect your
MIL-STD-1553 network directly to the real-time application
running on the dSPACE processor board. It supports the
DS1005 PPC Board and DS1006 Processor Board, and is also
multiprocessor-capable.
Each channel can be configured independently as Remote
Terminal (RT), Bus Controller (BC), or Bus Monitor (BM).
When configured as Remote Terminal, each channel supports
up to 31 remote terminals, and in BC functionality, schedule
lists are supported, with the ability to change lists dynamically during run time to facilitate fault testing for RTs.
high-speed) bus and a 2-MB dual-port memory (DPMEM).

A Compact Flash (CF) card contains the QNX run-time
operating system and the ETX application. The I/O connection to the Simulink model is configured graphically by
means of the MIL-STD-1553 blockset.
2015
Introduction
Modular Hardware / Interface to MIL-STD-1553
Technical Details
Parameter
Specification
General
n
Up to 4 RX/TX single-function dual-redundant MIL-STD-1553B Notice II Channels supported
n
Each channel can be configured as BC, RT, or BM
n
Up to 31 RTs supported per RT channel
n
1 MB of RAM per channel
n
45-bit message time-tagging
Application Fields
n
User-selectable direct or transformer output coupling
n
Bus voltage user-configurable at a static or variable level during run time
n
Mode code support
BC (bus controller) features
n
BC messaging schedule lists supported
n
Control of major and minor frame content and timing
n
User-configurable No Response timeout
n
User-configurable Late Response timeout
n
User-configurable minor frame period
n
Data and mode code transmit and receive
n
Precise time-stamping of TX and RX data
n
Multiple RT simulation (up to 31 RTs) per channel
RT (remote terminal) features
n
RT31 configurable as a broadcast node
Software
n
32 transmit and 32 receive subaddresses (SAs) per RT, 32 words of data per SA
n
RT node configuration supports changing status word during run time
n
Blocks for RX/TX of data and mode codes, including broadcast (RT31)
n
45-bit, microsecond resolution time-tagging
BM (bus monitor) features
n
Using the real-time processor of the DS1005 or DS1006 Processor Board, up to 100 messages
can be monitored and captured simultaneously with the Bus Monitoring Block
n
Transition cable to MIL-STD-1553 jacks provided
Supported standards
n
PMC Mezzanine Card
n
MIL-STD-1553B Notice II
n
Physical size
n
Ambient temperature
n
0 ... +70 C (32 ... 158 F)
Power supply
n
+5 V 5%, 7-10 A
Hardware
Host interface
Product
Order Number
Interface to MIL-STD-1553
Please inquire
Engineering
Order Information

Software
Required
Order Number
n
n
RTI
n
DS4504 MIL-STD-1553B Interface (DS1005, DS1006)1)
Hardware
Required
Order Number
n
DS4504 PMC Carrier Board
n
DS4504
n
QPM-1553-2S, QPM-1553-4S (2 or 4 channel module,
GE Intelligent Platforms)
n
CF card with QNX OS Kontron ETX module
2015
447
1)
Modular Hardware / ARINC 429 Interface
ARINC 429 Interface

Interface to the ARINC 429 avionics data bus
Highlights
Connects modular dSPACE real-time systems to
the ARINC 429 data bus
n Supports up to 32 transmit and receive channels
n Simulink block library
n
448
Application Areas
The ARINC 429 Interface is used to connect dSPACE simulators and prototyping systems to the ARINC 429 avionics
data bus. It enables dSPACE HIL simulators to be used for
testing aircraft electronics, at both the subsystem and the
complete-vehicle level (Integrated Flight Testing facilities),
and dSPACE prototyping systems to be used for developing
new control functions in areas such as engine management
(FADEC), flight surface actuation, guidance, and navigation.
Key Benefits
n Easy configuration of each IP module via a setup block
n Data manipulation blocks
n Supports advanced testing by inducing predefined
errors in a message
n Full software support for C handcoded applications

The interface consists of the IndustryPack (IP) module carrier board DS4501 and the IP-429HD-44P module from GE
Intelligent Platforms. On the real-time model side, a Simulink
block library and S-functions are provided to access the IP
module and its receive and transmit channels. The block
library provides access to the ARINC 429 bus on raw value
level, i.e., transmit and receive blocks in the model work
with 32-bit ARINC 429 words without distinguishing between data bits.
ARINC 429 Bus

The ARINC 429 specification defines how avionics equipment
and systems should communicate with each other. It is an
industry standard that is used on virtually all commercial
aircraft. The resulting bus system is the most commonly
used data bus for commercial and transport aircraft. It
employs unidirectional transmission of 32-bit words over
two twisted pairs. Messages are transmitted at a bit rate of
either 12.5 or 100 kilobits per second to other system
elements that monitor the bus messages. It supports one
transmitter and up to 20 receivers per channel.
2015
Introduction
Technical Details
Parameter
Specification
General
n
Up to 4 ARINC 429 IP modules supported
n
8 receive and 8 transmit channels per module
Application Fields
n
Adjustable receiver thresholds and transmitter output voltages
n
Automatic slew rate adjustment
Receive features
Data rates
n
12.5 kbit/s
n
100 kbit/s
Transmit features
Standard input levels
n
6.5 to 13 VDC
Parametric threshold levels
n
0.1 to 13.5 VDC (A to B)
Data rates
n
12.5 kbit/s
n
100 kbit/s
Standard output level
n
10 VDC (A to B)
Parametric output voltages
n
0 to 10 VDC (A to B)
Scaling
n
Adding a scaling factor based on the data format type to increase the resolution of the 19-bit
Transmission rates
n
Multiple transmission rates for multiple labels
Error injection
n
Supports BCHI, BCLO, GAP error injections per channel and PARITY error injection per label
Failure simulation
n
Label failure simulation by enabling/disabling labels during run time
Supported standards
Software
data of a 32-bit ARINC-word
n
IndustryPack
ARINC 429
n
n
Host interface
Physical
characteristics
Physical size
n
Full length ISA board
Ambient temperature
n
0 ... +70 C (32 ... 158 F)
Power supply
n
+5 V 5%, 36 mA (plus 77 mA per IP module)
Hardware
n
12 V 5%, 11 mA per IP module
Order Information
Product
Order Number
ARINC 429 Interface
Please inquire
Software
Required
Optional
Engineering

Order Number
n
Real-Time Interface (RTI) (p. 54)1)
n
RTI
n
dSPACE ARINC 429 Block library1) (DS1005, DS1006)
n
Bus Tool ARINC 2.61 from GE Intelligent Platforms
Hardware
Included
Order Number
n
DS4501 IP carrier board
n
ARINC IP-429HD-44P module, version 4
n
DS4501
(GE Intelligent Platforms)2)

For support of further ARINC 429 modules, please contact dSPACE.
2)
2015
449
1)
ARINC 717 Interface

Interface to the ARINC 717 avionics data bus
Highlights
n Connects modular dSPACE real-time systems
to the ARINC 717 data bus

Application Areas
The ARINC 717 Interface is used to connect dSPACE simulators and prototyping systems to the ARINC 717 avionics
data bus. ARINC 717 is used in avionics systems to communicate with flight data recorders. The interface enables
dSPACE systems to be integrated with such network communication, a typical example being the HIL simulation of
an aircraft for testing avionics in integrated flight testing
(ITF) applications. The ARINC 717 interface supports multiple channels and even multiple buses, so control applications
can comprise several devices.
Key Benefits
n Easy configuration of each IP module via a setup block
n Data manipulation blocks
n Supports advanced testing by inducing predefined
errors in a message
n Full software support for handcoded C applications

The interface consists of the DS4501 IP Carrier Board and
the IP-717-HBP from GE Intelligent Platforms. On the realtime model side, a Simulink block library and S-functions
are provided to access the IP module and its receive and
transmit channels. The block library provides access to the
ARINC 717 bus on raw value level, i.e., transmit and receive
blocks in the model work with 12-bit ARINC 717 data words,
with a user-configurable number of words at a specific
frequency.
450
2015
Introduction
Technical Details
Parameter
Specification
General
n
Up to 4 IP modules supported
Transmit features
Bit rates
n
768, 1536, 3072, 6144, 12288 or 24576 bit/sec
n
5 V differential
User-selectable subframe size
n
64, 128, 256, or 512 words (12-bit word size)
Receive buffer
n
4 KB
User-selectable receive rate
n
4 times subframe size received at specified rate
Wrap mode supported
n
User-selectable per channel
Bit rates
n
768, 1536, 3072, 6144, 12288 or 24576 bits/sec
n
5 V differential
User-selectable slew rate
n
1.5 or 10 s
User-selectable subframe size
n
64, 128, 256, or 512 words (12-bit word size)
Receive buffer
n
4 KB
Application Fields
n
1 RX and 1 TX channel per IP module
Receive features
User-selectable transmission rate

Enable/disable during run time
Supported standards
Software
n
Industry Pack
n
ARINC 717 HBP (Harvard Bi-Phase)
n
Host interface
Physical size
n
Full length ISA board
Ambient temperature
n
0 ... +70 C (32 ... 158 F)
Power supply
n
+5 V 5%, 36 mA (plus 83 mA per IP module)
n
+12 V, 39 mA per IP module
Hardware
n
-12 V, 39 mA per IP module
Order Information
Product
Order Number
ARINC 717 Interface
n
Please inquire
n
n
RTI
n
DS4501 ARINC 717 Interface (DS1005, DS1006)
Hardware
Included
Order Number
n
DS4501 IP Carrier Board
n
ARINC IP-717-HBP module (GE Intelligent Platforms)
n
DS4501
2015
451
Required
Order Number
Engineering
Software
Modular Hardware / FPGA Base Board
FPGA Base Board

For highresolution signal preprocessing
Highlights
n FPGA application-specific-programmable on
a per project basis
n Piggyback module with application-specific I/O drivers
n S-functions programmed on a per project basis to access
I/O from real-time applications
Application Areas
The FPGA Base Board has been designed for applications
that require very fast, high-resolution signal preprocessing,
for example:
n High-precision digital capturing of 3-phase PWM
signals.
n Simulation of engine speed/position sensors for electric
motors.
n Fast current/voltage measurements, connection of diverse
position encoders and control of AC motors
n Electric motor simulation
n Connection of dSPACE real-time systems to EtherCAT
networks as slaves
452
Key Benefits
The FPGA code and the piggyback module for the
FPGA Base Board are always tailored to specific applications, according to customers specifications, and can
be adapted to other projects. Algorithms for real-time
applications with high sampling rates can be shifted to the
FPGA (field programmable gate array). The time resolution
of the signals depends on how the FPGA is programmed.
The reference frequency for the control loop is set in the
digital frequency synthesizer (DFS). Even with complex FPGA
algorithms, the typical working range is 40 ... 80 MHz. The
piggyback module allows flexible integration of I/O drivers
and special combinations of analog/digital inputs/outputs
and bus drivers.
2015
Introduction
Modular Hardware / FPGA Base Board
Technical Details
Parameter
Specification
General
n Customization module site for a piggyback module providing customer-specific I/O adaptations
n 180
I/O lines from piggyback module to FPGA

I/O channels from piggyback module to a Sub-D connector on the boards rear bracket
n Additional I/O channels available via an additional bracket to a Sub-D connector
n Xilinx Spartan-3 XC3S4000
n System gates: 4 million
n Equivalent logic cells: 62,208
n CLBs: 6912
n Distributed RAM: 432 kbit
n Block RAM: 1728 kbit
n 96 dedicated multipliers
n 4 digital clock manager (DCMs)
n One 16-bitISAslot (power supply only)
Host interface
Physical
characteristics
Physical size
n 340x125xapprox. 20mm
(13.4x4.9xapprox 0.8in). The actual height depends on

the specific piggyback module.
Piggyback module size
n 123.5x114.3mm (4.86x4.5in)
Ambient temperature
n 0...70C (32...158F)
Power supply
n +5V5%, 500mA (without piggyback module)
Software
FPGA
Application Fields
n 18
n Power supply lines to piggyback module: 12 V, +5 V, and +3.3 V. Power consumption of
the piggyback module depends on the implemented application
Order Information
Order Number
FPGA Base Board
n DS5202
Hardware
Product

Software
n Engineering by dSPACE
Hardware
Order Number
n Piggyback module
Please inquire
Engineering
Required
See p. 580 (dSPACE Engineering Services)
2015
453
Required
Order Number
Modular Hardware / PWM Measurement Solution

Capturing of PWM signals
Highlights
n High-precision digital capturing of 3-phase
PWM signals
n Fast signal measurement and analysis
n RTI blockset for MATLAB/Simulink
Purpose
dSPACE offers you a PWM measurement solution based
on the DS5202 FPGA (field programmable gate array) Base
Board. It is specially designed for high-precision digital capturing of 3-phase PWM signals such as those typically used
for controlling a 3-phase AC electric motor.
Efficient testing of electronic control units (ECUs) for electric
machines requires fast measurement and analysis of several
closely associated signals. The challenge is to capture these
signals with a very short sample time, e.g. <20 s.
Application
The DS5202 PWM solution combined with a simulation
model allows you to measure the signals of up to 4 electric
machines with up to 8 power switch control signals each,
for example, IGBTs (insulated-gate bipolar transistors). The
combined signals of up to 4 inverter legs can be evaluated
for verifying the ECUs functions. For example, if the dead
time does not reach the predefined minimum, an error flag
454
Use Case
A typical use case is a hardware-in-the-loop (HIL) simulation,
where the electric motor including the electronic power
stage is simulated by means of the dSPACE modular realtime hardware. Simulation models like dSPACE Automotive Simulation Models ASM Electric Components Library
(p. 247) are used for simulating electric components. The
gate driver signals (typically PWM signals) coming from a
controller are measured by the DS5202 PWM measurement
solution The calculated motor current signals are sent back
to the controller by means of analog voltage signals.
is generated and an interrupt is triggered. To measure the

gate time, there are three operating modes to choose from:
software polling, external interrupt source, and internal pulse
center interrupt source, meaning clock generation based on
the measured PWM signals. If you do not have access to the
ECUs clock rate, PWM-based clock generation is the most
suitable way of avoiding beat effects in the simulation.
2015
v1
u1
v1
u2
v2
w1
v1
w2
v2
v2
Application Fields
Introduction
Modular Hardware / PWM Measurement Solution
u1 ...
IGBT control signals
Model of 3 inverter legs
Features
n Measuring duty cycles and periods of up to 32 PWM
signals
n Separate group access via Simulink interface. Capture
mode adjustable for each group independently.
n Measuring phase shifts between two half-bridges
n Evaluating dead time between adjacent channels
n Interrupt generation if the measured dead time is
less than a predefined value
n Generating interrupts and triggers to external devices
at the center position of the PWM period
Software
HIL simulation
n Multiple interrupt generation in one period (oversampling)

n Reducing the sampling rate of generated interrupt signal
(downsampling)
n Using an external trigger as a latch source for the time
measurement
n Using an external trigger as an interrupt for the real-time
model
n High timing resolution
n Adjustable debounce time
Hardware
ECU
Electric machine model
Technical Details
Timing resolution
Digital input
Number of channels
Input voltage range
Two adjustable threshold values
Input resistance
Resolution
Digital output
Number of channels
Used for
Frequency range
n
n
n
n
n
25 ns
32
0 ... +15 V
2.5 or 7.5 V
10 k
25 ns ... 400 ns (adjustable)
4 (shared with digital inputs)

n 0 ... +5 V
n PWM center trigger generation
n
39 Hz to 40 MHz
Order Information
Engineering
Specification
Software
Order Number
FPGA Base Board
DS5202
I/O piggyback module for DS5202 PWM application
DS5202_PWM
Simulink Interface for DS5202 PWM application
DS5202_PWM_BS
Relevant Software
Hardware
Required
Order Number
RealTime Interface (RTI)
RTI
2015
455
Parameter
Modular Hardware / Position Sensor Simulation Solution
Position Sensor Simulation Solution

Highlights
n Simulation of various position sensors
n RTI blockset for MATLAB/Simulink
Purpose
The PSS (position sensor simulation) solution is based on
the DS5202 FPGA Base Board. It is specially designed for
simulating typical position sensors such as resolvers or
incremental encoders.
Use Case
A typical use case is a hardware-in-the-loop (HIL) simulation incorporating electric motor simulation. The PSS
solution provides the necessary position signals for
the ECU.
Application
The board is equipped with four independent angular processing units (APUs) that receive the angular velocity from
the model and calculate the position signal. Since each
APUs sample time is 25ns, it provides a position signal
with a high timing and angular resolution. You can define

the APUs offset position freely for every sensor and adjust
the board precisely to your requirements by configuring all
the important parameters.
Features
n Two digital and two analog sensors (three signals each)
can be simulated in parallel.
n
Different sensor types are possible
n
Analog type: resolver, sinus encoder, user-defined
waveform
n
Digital type: TTL encoder, Hall position sensors,
user-defined waveform
n The analog and digital sensor simulation groups can be
arbitrarily allocated to up to four independent simulated
shafts (APUs). Four sensors can be simulated per simulated shaft.
456
n Resolver failure simulation:

n Amplitude deviation: (dos degradation of signal)
n Angle deviation: (lot loss of position tracking)
n APU-angle-dependent arbitrary waveform generation:
n Analog: 16384 values (-10 V ... 10 V)
n Digital: 8192 values TTL
n High precision and high timing resolution
n On-board signal conditioning
n Full differential I/O
2015
Introduction
Software
Application Fields
Resolver simulation:
One primary analog input and two modulated
analog outputs (sines and cosines).
2015
457
Engineering
Hardware
Digital incremental encoder simulation:

Two 90 phase-shifted digital signals and one
index signal.
Technical Details
APU (Angular Processing Unit)
Parameter
Specification
Number of independent APU units
n 4
APU angle precision
n 32 bit
APU update rate
n 25 ns / 40 MHz
APU speed range
n Up to 292,969 rpm
Analog Sensor Simulation

Parameter
Specification
Number of analog sensors
n 2
Sensor types
n Resolver, sine encoder, user-defined waveform
Number of pole pairs
n 1 ... 16,383
Adjustable angle offset
n -360 ... +360
Resolver accuracy
n 0,1 (depending on the settings)
Resolver transformation ratio
n 0 ... 16 (typically 0.5)
Resolver Failure Simulation

Additional delay for resolver feedback signals
Amplitude error (degradation of signal (dos))
Phase error (loss of position tracking (lot))
458
n Up to 409.6 s
n -100 ... +100%
n -90 ... +90
User-defined waveform resolution (16384 values)
n 0.02197
Analog Inputs
Input range
Resolution
Protection
Resolver excitation-coil simulation
n 2 channels
Analog Output (Cosine/Sine)

Output range
Resolution
Sampling rate
Output mode
Protection
n 4 channels
Analog Output (Index)

Output range
Resolution
Sampling rate
Output mode
Protection
n 2 channels
n 30 V (differential)
n 14 bit pipelined
n 60 V
n 220 / 2 W
n 10 V single-ended (20 V differential or transformer mode)
n 12 bits (of user-specified output range)
n 10 MSPS
n Transformer or direct output
n 60 V
n 10 V
n 12 bit
n 10 MSPS
n Single-ended output
n 60 V
2015
Introduction
Parameter
Specification
Number of digital densors
n 2
Sensor types
n TTL encoder, Hall encoder, user-defined waveform
n 1 ... 16,383
User-defined waveform resolution

(8,192 values)
n 0.0439
Digital Output
Output range
Sample rate
Output current
Protection
n 6 channels (each with inverted output stage)
Application Fields
Digital Sensor Simulation
n 0 ... +5 V
n 25 ns / 40 MHz
n 20 mA
Software
n 60 V
Order Information
Product
Order Number
FPGA Base Board
n DS5202
I/O piggyback module for DS5202 PSS application
n DS5202_PSS
Simulink Interface for DS5202 PSS application
n DS5202_PSS_BS
Software
Order Number
n RTI
Engineering
2015
459
Required
Hardware
Relevant Software
Modular Hardware / AC Motor Control Solution

Highlights
n
Fast current/voltage measurements
n
Control of AC motors, e.g., asynchronous motors (ASMs),
brushless DC motors (BLDCs) and permanent magnet

synchronous motors (PMSMs)
n
Suitable PWM generation for electric drives
n
Connection of diverse position encoders
n
RTI Blockset for MATLAB/Simulink
Purpose
The AC Motor Control Solution is based on the DS5202
FPGA Base Board or on the MicroAutoBox with DS1512
I/O board.
These are specially designed for fast current / voltage measurements, connecting diverse position encoders and controlling AC motors such as ASMs, BLDCs and PMSMs. Rapid
Use Case
Typical use cases for the AC Motor Control Solution are
highly dynamic control systems for different types of AC
motors.
Some scenarios:
n Field-oriented control of PMSMs or ASMs
n Control of BLDCs
n Prototyping new methods for sensorless control
n Using RapidPro Power Unit with suitable modules or
customer-specific power converters
To use the AC Motor Control Solution in a vehicle, you can
install it in the dSPACE AutoBox or use the MicroAutoBox
variant. For stationary use, it can be installed in an expansion box.
460
control prototyping of AC motors requires fast I/O, which is

fullfilled by using an FPGA Base Board and the appropriate
piggyback module, with the control algorithms running on
the main processor. The interface between the user's control
model and the AC Motor Control hardware is implemented
by using the AC Motor Control Solution RTI Blockset.
Applications
n Measurements (of phase currents and/or voltages,
and DC link currents or voltages) and ADC starts can
be synchronized to PWM signals.
n Position and speed measurements using typical
sensors such as Hall sensors or incremental encoders,
resolvers, or typical single/multiturn encoders with
serial interfaces (EnDat or SSI)
n Generation of gate driver signals (center-aligned
3/6 PWMs for sinusoidal commutation or PWM signals
for block commutation or advanced customer-specific
PWM patterns)
n Synchronization of ADC measurement with centeraligned PWM signals (regular sampling)
n Model synchronization by interrupt generation at the
center position of the PWM or at user-defined motor
angles.
n Trigger signal to external devices at the center position
of the PWM.
2015
Introduction
PHS Bus
DS1005/DS1006/
DS1007
or
Application Fields
Control signals
Current signals
Piggyback module
used inside
MicroAutoBox II
DS5202
Software
Hall / Encoder
Resolver, SSI,
EnDat
EV1048
RapidPro Power Unit

RTI Blockset
Motor
2015
461
Engineering
Hardware
For more information about installing piggyback modules

with MicroAutoBox II, please see p. 522.
Technical Data (AC Motor Control Solution for Modular System)

Parameter
Specification
Digital input
n 8 channels, 0 ... 5 V, differential or single-ended. Default: 3 x single-ended for Hall sensor, 3 x differential for
Digital output
n 10 channels, 0 ... 5 V, single-ended; 6 gate driver signals, 4 generic digital outputs (e.g. PWM synchronization
incremental encoder, 2 x single-ended for bit in, frequency and duty cycle measurement
signals or bit out)
n Gate driver frequency 10 Hz ... 1 MHz
n 12 additional gate driver signals available by using the ACMC Extension Board
ADC
n 8 channels, software-configurable inpult voltage range ( 5 V, 15 V, 30 V), differential, 10 MSPS
DAC
n 2 channels, -10 ... 10 V (single-ended) or -20 ... 20 V (differential, reference to GND)
Resolver interface
n Max. position resolution 16 bits (depending on motor velocity). Generation of excitation signal (3,7,10 Vrms);
excitation frequency from 2 ... 20 kHz within 250 Hz steps (software-configurable)

n SSI or EnDat for connection of single/multi turn encoder
RS422/RS485
n 4 RS485 transceivers for connecting 2 serial angle meters (EnDat or SSI interface)
Power supply for sensors
n 5 V and 12 V, 140 mA
Order Information
Product
Order Number
DS5202 AC Motor Control
n DS5202_ACMC
DS5202 ACMC PWM Extension Board
n DS5202_ACMC_EXT
DS5202 AC Motor Control Blockset
n DS5202_ACMC_BS

Software
Order Number
Included with DS5202

Required
FPGA firmware for AC motor control application

Hardware
Order Number
Included with I/O piggyback module
462
n RTI
Bracket for connection of I/O and mating connectors
2015
Introduction
Parameter
Specification
Digital input
n 8 channels, 0 ... 5 V, differential or single-ended, configurable by software
ADC
Example: 3 x single-ended for Hall sensor, 3 x differential for incremental encoder, 2 x single-ended for bit in,
frequency and duty cycle measurement
n 16 channels, 0 ... 5 V, single-ended to generate gate driver signals, PWM synchronization signals, bit out
n 8 additional channels by modifying IP-module pins
n Gate driver frequency 10 Hz ... 1 MHz
n 8 channels, software-configurable inpult voltage range (5 V, 15 V, 30 V), differential, 10 MSPS
DAC
n 2 channels, -10 ... 10 V (single-ended) or -20 ... 20 V (differential, reference to GND)
Resolver interface
n Max. position resolution 16 bits (depending on motor velocity). Generation of excitation signal (3,7,10 Vrms;
RS422/RS485
n SSI or EnDat for connection of single/multi-turn encoder
Digital output
Application Fields
Technical Data (AC Motor Control Solution for MicroAutoBox II)
excitation frequency from 2 ... 20 kHz in 250 Hz steps (software-configurable)

n 4 RS485 transceivers for connection of 2 serial angle meters (EnDat or SSI interface)
n 12 V: max. 50 mA
Software
n 5 V: max. 50 mA (use the MicroAutoBox II VSENS-PIN for currents up to 250 mA)
Order Information
Order Number
DS1553 ACMC Module
n MABXII_ACMC
MicroAutoBox II AC Motor Control Solution Blockset
n MABXII_ACMC_BS
Hardware
Product
Relevant Software
Software
Order Number
FPGA firmware for AC motor control application
n RTI
2015
463
Engineering
Included with DS1553

Required
Modular Hardware / EMH Solution
EMH Solution
Highlights
n High-precision digital capturing of
3-phase PWM signals
n Fast signal measurement and analysis
n Simulation of various position sensors
n Various additional multipurpose signals
n RTI Blockset for MATLAB/Simulink
Purpose
The EMH (electric motor HIL) solution is based on the DS5202
FPGA Base Board. It gives you all the I/O channels that are
needed for HIL simulation of electric motors, such as highprecision digital capturing of 3-phase PWM signals and
position sensor simulation, plus several digital and analog
I/O channels. It combines the features of the DS5202 PWM
and PSS solutions with many additional multipurpose channels, and enables efficient testing of electronic control units
(ECUs) for electric motors on a single I/O board.
Application
The DS5202 EMH solution combined with a simulation
model allows you to measure the signals of up to 2 electric
machines with up to 8 power switch control signals each,
for example, IGBTs (insulated-gate bipolar transistors). There
is a choice of three operating modes: software polling,
external interrupt source, and internal pulse center interrupt
source, meaning clock generation based on the measured
PWM signals, which is the most suitable way of avoiding
beat effects.
464
Use Case
A typical use case is a hardware-in-the-loop (HIL) simulation
where the electric motor including the electronic power
stage is simulated by means of the dSPACE modular real-time
hardware. Simulation models like dSPACE Automotive Simulation Models ASM Electric Components Library (p. 247) are
used for simulating the electric components. The gate driver
signals (typically PWM signals) coming from a controller are
measured by the DS5202 EMH solution, and calculated
motor current signals are sent back to the controller by
means of analog voltage signals, which can also be provided
by the DS5202 EMH solution. In addition, the DS5202 EMH
solution provides the necessary position sensor signals for
the ECU.
The current feedback signals for the ECU can be simulated

by using the boards fast analog output channels. For position sensor simulation, the board is equipped with four
independent angular processing units (APUs) that receive the
angular velocity from the model and calculate the position
signal. Since each APUs sample time is 25 ns, it provides a
position signal with a high timing and angular resolution.
2015
PHS bus
Introduction
DS1005/DS1006/DS1007
DS5202
Application Fields
Gate control signals
I/O module
Current signals
ECU
Hall/encoder
Software
Resolver
PWM Measurement
n Oversampling and downsampling for interrupt generation
n Using an external trigger as a latch source for the time
measurement and interrupt for the real-time model
n 16 channels can alternatively be used as general purpose
inputs (digital or PWM inputs)
n Adjustable debounce time
n Measuring phase shifts between two half-bridges
Hardware
Features
n Measuring duty cycles and periods of up to 16 PWM
signals
n Separate access by groups of 8 channels via Simulink
interface. Capture mode adjustable for each group
independently
n Evaluating dead time between adjacent channels
n Generating interrupts and triggers to external devices
at the center position of the PWM period
Features
n One digital and one analog sensor (three signals each),
one protocol-based sensor and three independent anglebased digital signals can be simulated in parallel.
n Different sensor types are possible:
n
Analog type: resolver, sinus encoder, user-defined
waveform
n
Digital type: TTL encoder, Hall position sensors,
user-defined waveform
n Protocol type: SSI, Hiperface or EnDat sensor simulation
Engineering
Position Sensor Simulation

n All sensor simulation groups can be arbitrarily allocated
to up to four independent simulated shafts (APUs).
n Resolver failure simulation (please refer to PSS solution)
n APU-angle-dependent arbitrary waveform generation
(please refer to PSS solution, p. 456)
n High precision and high timing resolution
n On-board signal conditioning
n Full differential I/O for all analog signals
2015
465
RTI Blockset
Multipurpose Channels
Features
n 7 analog output channels
n 4 analog input channels
n 10 digital output channels
n 1 digital input
Channels of the PWM measurement and position sensor

simulation can alternatively be used as standard multi
purpose I/O.
Shared I/O:
n 3 analog output channels
n 2 analog inputs channels
n 16 digital/PWM input channels
n 6 digital output channels
n 3 digital/PWM output channels

n RS485 full duplex UARTS used for serial sensor simulation or LTI ServoOne TWINsync communication
Technical Details PWM Measurement
466
Parameter
Specification
Number of channels
n 16
Resolution
n Max. 12.5 ns (80 Mhz) - 400 ns (adjustable)
Center-aligned capture groups
n 2 (each group has 8 channels)
Input voltage range
n 0 ... +30 V
Adjustable thresholds
n +1 ... +8.5 V
Input resistance
n 24 k
Protection
n 50 V
2015
Introduction
Technical Details Position Sensor Simulation
Parameter
Specification
Number of independent APU units
n 4
APU angle precision
n 32 bit
APU update rate
n 25 ns / 40 MHz
APU speed range
n Up to 292,969 rpm
Application Fields
APU (Angular Processing Unit)
Parameter
Specification
Number of Analog Sensors
n 1
Sensor types
n Resolver, sine encoder, user defined waveform
n 1 ... 16,383
Adjustable angle offset
n -360 ... +360
Resolver accuracy
n 0.1 (depending on the settings)
Resolver transformation ratio
n 0 ... 16 (typ. 0.5)

n Up to 409.6 s
n -100 ... +100%
n -90 ... +90
n 1 channel
Analog Output (Index)

Output range
Resolution
Sampling rate
Output mode
Protection
n 1 channel
Hardware
n 0.02197
Analog Input (Resolver Excitation Input)

Input range
Resolution
Sampling rate
Protection
Resolver excitation-coil simulation
Analog Output (Cosine / Sine)
Output range
Resolution
Sampling rate
Output mode
Protection
n 30 V (differential)
n 14 bit pipelined
n 10 MSPS
n 50 V
n 220 / 2 W
n 2 channels
n 10 V single ended (20 V differential / transformer mode)
n 12 bit (of user specified output range)
n 10 MSPS
n Transformer or direct output
Engineering
n 50 V
n 10 V single ended (20 V differential)
n 12 bit
n 10 MSPS
n Direct output (with inverted output stage)
n 50 V
2015
467
Resolver Failure Simulation

Additional delay for resolver feedback signals
Amplitude error (dos ... degradation of signal)
Phase error (lot ... loss of position tracking)
User defined waveform resolution (16,384 values)
Software
Analog Sensor Simulation
Digital Sensor Simulation

Parameter
Specification
Number of digital sensors
n 1 (+3
Sensor types
n TTL encoder, hall encoder, user defined waveform; (+3 independent angle-based outputs)
independent angle based outputs)
n 1 ... 16,383
User defined waveform resolution (8,192 values)
n 0.0439
Digital Output
Output range
Sample rate
Output current
Protection
n 6 channels (3 channels with inverted output stage)

n 0 ... +5V
n 25 ns / 40 MHz
n 20 mA
n 50 V
Serial Sensor Simulation

Parameter
Specification
Number of serial sensors
n 1
Sensor types
n SSI-Encoder, Hiperface Encoder, EnDAT Encoder
Number of multi turn bits
n 0 to 14
Number of single turn bits
n 1 to 18
RS485
Maximum data rate
Protection
n 2 full-duplex channels
n Up to 10 Mbps
n 50 V
Technical Details Multipurpose Channels

Parameter
Specification
Analog outputs
n 6 channels; 10 V output voltage range;
12 bit; 10 MSPS; differential; Protection 50 V

n 1 channel; 10 V output voltage range;
14 bit; 1 MSPS; single ended; Protection 50 V

n 3 channels; 10 V output voltage range;
12 bit; 10 MSPS; Protection 50 V; shared with analog sensor simulation

Analog inputs
n 4 channels; 30 V input voltage range;
Digital inputs
16 bit; 1 MSPS; differential; Protection 50 V

input voltage range;
14 bit; 10 MSPS; differential; Protection 50 V; shared with resolver simulation
n 1 channel; 0 ... +30 V; Protection 50V
n 16 channels; 0 ... +30 V; Digital or standard PWM inputs; 12.5 ns (80 MHz) resolution;
Protection 50 V; shared with center aligned PWM measurement units
n Global adjustable threshold voltage +1 ... +8.5 V
Digital outputs
n 10 channels; 0 ... +5V output voltage range;
n 2 channels; 30 V
Protection 50 V
n 6 channels; 0 ... +5 V output voltage range; Protection 50 V; shared with digital sensor
simulation
n 3 channels; 0 ... +5 V output voltage range; Protection 50 V; shared with digital sensor
simulation; Mode: Digital out or PWM out (25 ns resolution)

RS485
n LTI ServoOne TWINsync; 4 Mbaud; (To control a ServoOne inverter by dSPACE real-time
hardware; shared with serial sensor simulation)

Prepared control modes: PWM control; Torque control; Speed control; Position control
468
2015
Introduction
Product
Order Number
FPGA Base Board
n DS5202
I/O piggyback module for DS5202 EMH application
n DS5202_EMH
Simulink Interface for DS5202 EMH application
n DS5202_EMH_BS
Application Fields
Order Information
Relevant Software
Software
Order Number
n RTI
Engineering
Hardware
Software
2015
469
Required
Modular Hardware / EtherCAT Slave Interface

Slave interface to an EtherCAT communication bus
Highlights
n Connects dSPACE real-time systems to EtherCAT
networks as slaves
n Dual-port memory for data exchange with processor
board
n RTI EtherCAT Blockset for MATLAB/Simulink
470
Application Areas
The dSPACE EtherCAT slave interface connects a dSPACE
real-time system to the Ethernet fieldbus EtherCAT as a
slave. Typical use cases for the EtherCAT slave interface are
real-time applications in automation technology, such as
process automation or test benches.
Key Benefits
The dSPACE EtherCAT slave interface enables you to take
advantage of the very high performance of an EtherCAT
network, which supports 100 Mbit/s and cycle times down
to 50 s.
EtherCAT
EtherCAT is an open, high-performance, Ethernet-based
fieldbus system and is especially designed for automation
applications which require short cycle times and low communication jitter. The EtherCAT slave device reads the data
addressed to it and also inserts input data while the telegram
passes through. The frames are only delayed by a fraction
of a microsecond in each node, and many nodes can be
addressed with just one frame. EtherCAT is an international
standard (for more information, see www.ethercat.org).

The EtherCAT slave interface consists of the DS5202 FPGA
Base Board with a piggyback module, which carries up to
two Beckhoff EtherCAT modules FB1111-0140. The bracket
features two RJ45 plug sockets for connection to the
EtherCAT network.
The EtherCAT blockset mainly consists of a base library and a
template model generator. A model containing all the necessary blocks is generated from a configuration M-structure
that has to be created by the user.
2015
Introduction
Modular Hardware / EtherCAT Slave Interface
Technical Details
Parameter
Specification
General
n Direct connection to the field bus

n Dual-port memory for data exchange with processor board
n Two RJ45 connectors for connection to the network
n Two slave modules
n Object dictionary can be created according to CiA DS404
Application Fields
n Up to 6 sync managers per module whose type (input/output) can be defined freely
Cyclic communication
n Static PDO mapping and PDO assignment

n 7 KB can be used for cyclic communication (3-buffer mode)
CAN application layer over EtherCAT communication
n Input and output mailbox with 512 bytes each
Template model generation
n Template model and device description file (DDF) are generated according to configuration script
and base library

n Ensures consistency between DDF and template model
n Generation process contains consistency checks on users configuration
n Each sync manager block can be placed in its own task
Multirate modeling
n EtherCAT interrupts (distributed clocks, sync manager interrupts) are available to synchronize
the model to EtherCAT events

n EtherCAT
Supported standards
Host interface
n One 8- or 16-bit ISA slot (power supply only)
Physical size
Software
Physical
characteristics
n Full-length ISA board

n 2 slots required (3 slots when using two connector adapters)
Power supply
n +5 V 5%
Product
Order Number
n Please inquire
Hardware
Order Information

Order Number
Included
n EtherCAT Slave Blockset
Required
Included
Order Number
n FPGA Base Board
Engineering
Hardware
n RTI
n DS5202
n I/O piggyback module for EtherCAT
n Two Beckhoff EtherCAT modules FB1111-0140
n Bracket for connection to EtherCAT network
2015
471
Software
Modular Hardware / 100 Mbit/s Ethernet Interface (UDP/IP, TCP/IP)
100 Mbit/s Ethernet Interface (UDP/IP, TCP/IP)

Interface to an Ethernet network
Highlights
Connects a modular dSPACE real-time system
to an Ethernet network
n For projects that need intelligent data processing
n Data transmission for customer-specific bus system
n Easy-to-use, comfortable Simulink blockset
n
Application Areas
The 100 Mbit/s Ethernet Interface connects a modular
dSPACE real-time system to an Ethernet network. It enables
you to transmit data between dSPACE processor boards
(DS1005, DS1006, or multiprocessor system) and a remote
computer system. Its application areas are hardware-in-theloop simulation and rapid control prototyping, where simultaneous communication runs via one or more network
nodes. Data transmission between the processor board and
a customer-specific bus system can also be implemented by
using an appropriate gateway computer connected to the
Ethernet network.
Key Benefits
The dSPACE Ethernet Solutions supports variable length
frames for sending and receiving with datagram up to a
payload size of 65507 bytes. It also supports TCP (Transmission Control Protocol) single point-to-point communication.
The UDP/IP and TCP/IP protocols are executed on the ETX.
The dynamic or static IP address of the ETX module comes
with auto negotiations features. Your Ethernet configuration
is downloaded to DS4504 and initialized by startup.

The dSPACE Ethernet Solution is based on a DS4504 PMC
Carrier board with an Embedded Technology eXtended (ETX)
module. The ETX module provides a 100 Mbit/s Ethernet
interface. The solution requires a DS381 Ethernet Connector
Board for connection to the DS4504 via a standard RJ45
network connection. The solution and the connection to
the Simulink model are configured graphically by means of
the DS4504 Ethernet Basic Blockset, which is based on
S-functions.
472
2015
Introduction
Modular Hardware / 100 Mbit/s Ethernet Interface (UDP/IP, TCP/IP)
Technical Details
Parameter
Specification
General
n
DS4504 ETX carrier board with ETX module
n
Simultaneous communication with one or more networks
n
Communication with processor board via PHS++ (Peripheral High Speed) bus
n
Multiprocessor-capable
n
Dynamic or static IP address with auto negotiation features
Receive/transmit features
Application Fields
n
TCP single point-to-point (client/server) communication
n
Variable length frames for sending and receiving
n
Support of datagram up to payload size of 65507 bytes
n
Sending and receiving (multiple) TCP and UDP frames to user-defined IP addresses and ports
Physical
characteristics
Physical size
n
95 x 114 mm (3.7 x 4.7 in)
Ambient temperature
n
0 ... +60 C (32 ... 140 F)
Power supply
n
+5 V 5%, 6-9 A
Product
Order Number
100 Mbit/s Ethernet Interface
Please inquire
Software
Order Information

Software
Required
Order Number
n
n
RTI
n
DS4504 Ethernet Basic Blockset1)
n
DS4504_ETH_SOL
Hardware
Order Number
n
DS4504
n
Kontron ETX module
n
DS4504_ETX_CD166_2GB
n
DS381 Ethernet Connector Board
n
DS381
Engineering
n
DS4504 PMC Carrier Board
For information about our 10 Mbit/s Ethernet Interface

(UDP/IP), please see p. 475.
For information about our DS1006 Advanced Support
Package, please see p. 475.
2015
473
Required
Hardware
1)
Modular Hardware / Additional I/O Solutions

I/O to your specifications
Highlights
n Solutions for I/O and buses not covered by
our standard boards
n Development of customer-specific I/O boards
for nonstandard I/O
n Programming of advanced I/O functions and
Simulink S-functions
Key Benefits
The list of I/O solutions which dSPACE has developed in
response to customer requirements is extensive. The need
for such solutions arises when situations cannot be covered
by our off-the-shelf boards. Some I/O solutions establish
connections to field-bus-based systems and industrial or
aerospace buses. In general, I/O solutions typically consist
of integrated hardware and software.
I/O Solutions
The following pages give just a few examples of dSPACEs
additional I/O solutions:
n DS1006 Advanced Support Package
n 10 Mbit/s Ethernet Interface (UDP/IP)
n VME Interface
n Programmable Generic Interface (PGI1)
n Battery Cell Voltage Measurement and Balancing
n Resolver Interface
You can also create your own solution based on the DS4201
Prototying Board (p. 416), or dSPACE can provide a solution
for you.
Order Information
474
Product
Order Number
Additional I/O solutions
Please contact dSPACE if you are interested in additional I/O solutions.
2015
Introduction
DS1006 Advanced Support Package

n Uses the 4th core of the DS1006 Processor Board for
Application Fields
a Linux application to establish an Ethernet interface or

to implement customer-specific solutions
Software Details
n Interface software based on a Linux application
n Data exchange between real-time application and
Linux application
Software
Hardware Details
n DS921 connector bracket for direct mounting
on the DS1006 Processor Board
n 1 GBit/s Ethernet interface
n 2 USB interfaces
n The DS921 can be used in conjunction with the
DS911 Gigalink Module (p. 361) on the same
DS1006.
For an overview of dSPACE products for establishing

an Ethernet connection, please see p. 88.
Hardware
10 Mbit/s Ethernet Interface (UDP/IP)

n Connects dSPACEs modular hardware to Ethernet
bus (UDP/IP)
Engineering
Hardware Details
n Carrier hardware DS4502 with additional Ethernet
communication module (10 Mbit)
n Dual-port memory for data exchange with master
processor
n 9-pin Sub-D connector with RJ45 adapter for
connection to Ethernet network
Software Details
n Suitable for MotionDesk Multi-PC Interface Kit
(without master processor load)

n C functions for UDP/IP communication
n Simulink S-function blockset available
For an overview of dSPACE products for establishing

an Ethernet connection, please see p. 88.
2015
475
n UDP/IP protocol stack executed by module firmware
VME Interface
n Connects dSPACEs modular hardware to
VME bus systems

Hardware Details
n Connection to dSPACE system via reflective memory
on a special version of the DS4121 ECU Interface
Board (p. 412)
n VME bus side: reflective memory IP module
n 8-MHz and 32-MHz IP clock supported
Software Details
n dSPACE side: MATLAB/Simulink support
n VME bus side: limited MATLAB/Simulink support,
adaptation necessary
n No VME-specific software support
476
2015
Introduction
Programmable Generic Interface (PGI1)

n Generic interface box for decentralized connection of
Application Fields
sensors and actuators to dSPACE systems via diverse

serial interfaces and protocols (250 Mbit/s LVDS
interface for PHS- and MicroAutoBox-based (p. 522)
dSPACE systems, or Ethernet for SCALEXIO-based
(p. 296) dSPACE systems)
n Emulation of sensor signals (e.g. of yaw rate or crash
sensors) with hardware-in-the-loop (HIL) simulation
n Highly flexible adaptation to customer requirements
via piggyback modules and special FPGA firmware
SPI Master Solution (supports up to 4 masters)
PHS- and MicroAutoBox-based systems
SCALEXIO
(Configuration via Simulink Blockset)
(Configuration via ConfigurationDesk)
IC Master/Slave Solution (supports up to 16 masters and

256 slaves)
Interface for direct coupling of dSPACE real-time platforms

with LTi Drives servo controllers (LTi TWINsync protocol)
PSI5 Master/Slave Solution (supports up to 4 masters and

10 slaves)
Example of configuration via ConfigurationDesk for a SCALEXIO-based dSPACE system (a PSI5 sensor simulation)
2015
477
Engineering
SPI Slave Solution (supports up to 16 slaves)
Hardware
Solution
Software
Platform
Battery Cell Voltage Measurement and

Balancing
Application Areas
The Battery Cell Voltage Measurement and Balancing system
enables highly precise measurement and control of cell
voltages in lithium-ion batteries and allows the development
of algorithms for battery management. The system can be
installed directly in a vehicle and features cell-balancing
functions that maintain the charge states of individual cells
at the same level to ensure safe operation. This maximizes
battery capacity and extends battery life.
Manual and Automatic Balancing
Two operation modes are available: The manual balancing
mode gives users complete freedom to balance cells individually or collectively, and at any desired intervals. The
automatic balancing mode is a comfort function that
specifies target voltages and switch-off times, leaving users
free to focus on the more important algorithms.
Reliable Safety Features
Because of the high voltages of Li-ion batteries, the system
provides various safety features. These include warnings
about hardware, communication and synchronization errors,
and also about overheating, isolation faults, and cell undervoltages and overvoltages.
Technical Details
n Modular system supporting 4 to approx. 200 cells,
installable in a vehicle
n 24 cell voltages per module
n 24 cell temperatures per module
n Intersil ISL78600 BMS IC
n Cell voltage measured with up to 2 mV accuracy
n Synchronized measurement of cell voltages,
temperatures and current independent of the
number of cells
n High sampling rate of 1 kSPS
n Plug-on modules for quick replacement of balancing
resistances. Resistance values of up to 10
n S-function-based Simulink blockset (RTI Ethernet
(UDP) blockset additionally required)
n Two balancing modes:
n
Manual mode with full user control
n
Configurable automatic mode
n Comprehensive error detection features
n Isolation monitoring device connectable to each
module
For the emulation of high-voltage batteries, please
refer to the EV1077 Battery Cell Voltage Emulation
board (p. 514).
For battery simulation via dSPACEs Automotive Simulation Models, see p. 246.
478
2015
Introduction
Resolver Interface
n Connects dSPACEs modular hardware to resolver
Application Fields
sensors
n DS4501 IP Carrier Board hosting an IP module for
resolver-to-digital conversion from TEWS Technologies
(TIP150-41)
Software Details
n Configuration of each IP Module via a setup block
n Synchronous or asynchronous reading of resolver
If you would like to simulate a resolver, please see

p. 456 for the Position Sensor Simulation Solution based
on the FPGA Base Board.
If you would like to control an AC motor with a resolver,
see p. 460 for the AC Motor Control Solution based on
the FPGA Base Board, which provides both capabilities.
2015
479
Engineering
Hardware
channels
n Supports multiple range options
n Supports single- or dual-channel reading
Software
Hardware Details
n DS4501 supports up to 4 IP modules
n Each IP module can support 2 resolver sensors
n Supports adaptable signal conditioning
n Excitation signal can be set from 2kHz ... 20kHz,
11.8V rms (max), 70mA
n Detection of lost signals
Accessories / Connector and LED Panels
Connector and LED Panels

Easy access to I/O signals with BNC and SubD connectors
Highlights
Access analog signals via BNC connectors
n Access digital signals via standard Sub-D connectors
n Sub-D connectors are grouped according to I/O
channels or functional units
n LED panels indicate the status of the boards digital
signals
n
All Panels at a Glance

Board
Sub-D Connectors
LED Panel
Connector/ LED
Combi Panel
Width1)
Width1)
Width1)
DS2001
5 ADC inputs
2 MU
DS2002
32 ADC inputs
10 MU
DS2003
32 ADC inputs,
1 trigger
10 MU
DS2004
16 ADC inputs,
4 triggers
7 MU
DS2101
5 DAC outputs
2 MU
DS2102
6 DAC outputs
2 MU
DS2103
32 DAC output
10 MU
DS2201
20 ADC inputs,
8 DAC outputs
Digital I/O capture/

compare
DS2302
6 DAC/ADC Outputs/
Inputs
Digital I/O
3 MU
10 MU
4 MU
DS3001
5 incremental encoders
2 MU
DS3002
6 incremental encoders
3 MU
Digital I/O
4 MU
12 MU
3 digital I/O
4 MU
7 MU2)
DS4002
DS4003
8 timers,
2 triggers
DS5001
16 waveform inputs
5 MU
DS5101
16 waveform outputs,
1 reset
5 MU
1)
2)
480
BNC Connectors
Connector Panel
MU = measurement unit (1.2/30.5 mm), height for 19 rack: 2/51 mm (3 MU), depth for 19 desktop box: 2/51 mm.
Each CLP4003 serves only one of the three ports (32 lines).
2015
Introduction
Physical Dimensions and Weights

Connector/LED Combi Panel
Approx.
weight
DS2001
61 x 129 x 51 mm
(2.4 x 5.1 x 2 in)
0.45 kg
(1 lb)
DS2002
305 x 129 x 51 mm
(12 x 5.1 x 2 in)
1.9 kg
(4.1 lb)
DS2003
305 x 129 x 51 mm
(12 x 5.1 x 2 in)
1.9 kg
(4.1 lb)
DS2004
213 x 129 x 51 mm
(8.4 x 5.1 x 2 in)
1.2 kg
(2.6 lb)
DS2101
61 x 129 x 51 mm
(2.4 x 5.1 x 2 in)
0.2 kg
(0.45 lb)
DS2102
61 x 129 x 51 mm
(2.4 x 5.1 x 2 in)
0.25 kg
(0.55 lb)
DS2103
305 x 129 x 51 mm
(12 x 5.1 x 2 in)
0.9 kg
(2 lb)
DS2201
305 x 129 x 51 mm
(12 x 5.1 x 2 in)
1.7 kg
(3.7 lb)
0.2 kg
(0.4 lb)
DS2302
91 x 129 x 51 mm
(3.6 x 5.1 x 2 in)
0.7 kg
(1.5 lb)
DS3001
61 x 129 x 43 mm
(2.4 x 5.1 x 1.7 in)
0.35 kg
(0.8 lb)
DS3002
91 x 129 x 43 mm
(3.6 x 5.1 x 1.7 in)
1.1 kg
(2.4 lb)
DS4002
122 x 129 x 51 mm
(4.8 x 5.1 x 2 in)
0.45 kg
(1 lb)
365 x 129 x 51 mm
(14.4 x 5.1 x 2 in)
0.8 kg
(1.8 lb)
DS4003
122 x 129 x 43 mm
(4.8 x 5.1 x 1.7 in)
0.9 kg
(2 lb)
213 x 129 x 43 mm 1)
(8.4 x 5.1 x 1.7 in)
0.6 kg
(1.3 lb)
DS5001
152 x 129 x 51 mm
(6 x 5.1 x 2 in)
0.5 kg
(1.1 lb)
DS5101
152 x 129 x 51 mm
(6 x 5.1 x 2 in)
0.5 kg
(1.1 lb)
122 x 129 x 40 mm
(4.8 x 5.1 x 1.6 in)
Approx.
weight
Size (w x h x d,
without enclosure)
Approx.
weight
Application Fields
Size (w x h x d, without
enclosure)
Software
LED Panel
Size (w x h x d, without
enclosure)
Hardware
Connector Panel
Board
1)
2015
481
Engineering
(LED only
Order Information
Products
Order Number
Connector Panel
n CP2001
n CP2002
n CP2003
n CP2004
DS2101 D/A Board
n CP2101
n CP2102
n CP2103
DS2201 Multi-I/O Board
n CP2201
n CP2302
n CP3001
n CP3002
n CP4002
n CP4003
n CP5001
n CP5101
LED Panel
DS2201 Multi-I/O Board
n LP2201
Connector/LED
Combi Panel
n CLP4002
n CLP40031)
1)
Order Information
482
Products
Order Number
Required
19 rack for connector and LED panels (14MU)
(only one of these is required) 19 desktop box for connector and LED panels (14MU)
n CP_Rack
n CP_Desk
2015
Introduction
Enclosure Options
Application Fields
Rack or Desktop Box?

There are two enclosure options for installing your
connector panel or LED panel:
n 19 rack (16.8 or 14 measurement units
(MU) usable, height 3 U)
n 19 desktop box (16.8 or 14 measurement units
2015
483
Engineering
Hardware
Software
(MU) usable, depth 2/51mm without connector)
Accessories / Expansion Boxes
Expansion Boxes for Modular Hardware

Boxes for expanding the host PC for dSPACE systems
Highlights
n Space for 3, 9 or 19 dSPACE boards
n Including Link Board for connection to host PC
n Several options for connection to host
n AutoBoot option for stand-alone operation
n Low noise emission and efficient vibration handling
Technical Details: PX4 Expansion Box

Parameter
Specification
Chassis
n
Desktop box
n
4 full-size 16-bit ISA slots
n
1 slot reserved for Link Board
n
1 additional slot required if AutoBoot option is used
n
Low-noise fan cooling
n
Can be used for rapid control prototyping only
Power supply
n
100 ... 240 V AC, 50 ... 60 Hz
n
80 W
n
10 A at 5 V
Maximum output current1)
n
3 A at 12 V
n
0.8 A at -12 V
Grounding
n
Circuit ground is connected to the chassis and through that to the power
systems protective ground.

1)
2)
484
Physical size
n
99 x 165 x 428 mm (3.9 x 6.5 x 16.8 in)
Weight (without boards)
n
3.5 kg (7.7 lb)
Ambient temperature2)
n
0 ... 50 C (32 ... 122 F)
Humidity
n
0 ... 95%, noncondensing
The sum of the output currents of the rails must not exceed the maximum output power.
The dSPACE processor and I/O boards have different maximum ambient temperatures. When they are installed together, the lowest maximum
ambient temperature is applicable.
2015
Introduction

Parameter
Specification
Chassis
n
Desktop box
n
19 rack-mount version available (height: 4 U, 4 HE)
Application Fields
n
n
1 slot reserved for Link Board or slot CPU board for Ethernet connection
n
n
Low noise emission and efficient vibration handling
Power supply
Parameter
n
100 240 V AC, 50 ... 60 Hz
n
40 A at 5 V
Specification
n
250 W
n
10 A at 12 V
n
1 A at -12 V
n
Grounding

n
183 (includes 6 mm rubber feet) x 343 x 430 mm (7.2 x 13.5 x 16.9 in)
Physical size
n
10.8 kg (23.8 lb)
Ambient temperature
n
0 50 C (32 ... 122 F)
Humidity
n
0 95%, noncondensing
2)
1)
2)
Software
Parameter
Specification
Chassis
n
Desktop box
Hardware
n
19 rack-mount version available (height: 4 U, 4 HE)
n
n
1 slot reserved for Link Board or slot CPU board for Ethernet connection
n
n
Low noise emission and efficient vibration handling
Power supply
n
100 ... 240 V AC, 50 ... 60 Hz
n
400 W at 100 ... 170 V AC
Engineering
n
450 W at 170 ... 240 V AC
n
75 A at 5 V
n
12 A at 12 V
n
4 A at -12 V
Grounding
n

n
183 (includes 6 mm rubber feet) x 443 x 535 mm (7.2 x 17.4 x 21.1 in)
Physical size
n
15.6 kg (34.4 lb)
Ambient temperature
n
0 ... 50 C (32 ...122 F)
Humidity
n
0 ... 95%, noncondensing
2)
2)
1)
2015
485
Order Information
Order Number
Product
PCMCIA Link
Ethernet Interface1)
PX4
n
PX4/814/815
PX10 Desktop Box
n
PX10N1
n
PX10/814/815
PX10 Rack-Mount Version
n
PX10N1/Rack
n
PX10/814/815/Rack
PX20 Desktop Box
n
PX20N1
n
PX20/814/815
n
PX20N1/Rack
n
PX20/814/815/Rack
1)
Implemented via the host PCs own Ethernet port.
Order Information
Order Number
Product
486
PCI Bus Link
ExpressCard: DS821
PCI Express
PX4
n
PX4/814/817/Opto
n
PX4/814/821
n
PX4/814/819/Opto
PX10 Desktop Box
n
PX10/814/817/Opto
n
PX10/814/821
n
PX10/814/819/Opto
n
PX10/814/817/Rack/Opto
n
PX10/814/821/Rack
n
PX20 Desktop Box
n
PX20/814/817/Opto
n
PX20/814/821
n
PX20/814/819/Opto
n
n
PX20/814/821/Rack
n
2015
Introduction
Connection to the Host PC
2015
487
Engineering
Hardware
Software
Application Fields
Several Options for Connection

To connect your expansion box to your host PC, you have
several options: The physical connection between the host
PC and expansion box is established via a high-speed serial
or optical link. There are Link Boards for connecting host
PCs with ISA, PCI, PCI Express, PCMCIA, ExpressCard or
Ethernet connections (p. 492).
Accessories / AutoBox
AutoBox
Expansion boxes for invehicle use
Highlights
n Robust housing
n Power supply via car battery
n NEW: For 12 V, 24 V and 48 V electrical systems
n NEW: Improved cold-start behavior
Application Areas
AutoBox is the ideal enclosure for using your modular
dSPACE real-time system for in-vehicle control experiments
such as test drives in the development of powertrains, ABS
or chassis control. You can install AutoBox quite easily in
your test car, like in the trunk or the passenger cabin.
488
Key Benefits
AutoBox is a robust box for mounting processor boards and
I/O boards. It provides space for dSPACE hardware (7 slots
in the AutoBox, 14 slots in the Tandem-AutoBox). One of
the strengths of AutoBox is that it can operate in various
electrical systems such as 12 V, 24V and 48 V.
2015
Introduction
Technical Details
Specification
Parameter
General
AutoBox
Tandem-AutoBox
Enclosure
n
Compact aluminum chassis, shock mounts with rubber shoes
Slots
n
n
slot reserved for Link Board or slot CPU board for Ethernet connection (both not required for
PHS-bus systems based on DS1007)
Power supply
Cooling
n
Temperature-controlled fan with dust filter
Input voltage
n
10 V ... 60 V DC normal operating range
Load dump protection1)
n
Two power supplies. The following input
n
6 V ... 10 V DC undervoltage crank condition,
voltage values apply to each of them:
time-limited (> 10 s at 6 V DC, measured at

input connector)
n
8 V ... 60 V DC normal operating range
n
60 V 70 V DC
Application Fields
n
1
(10 V ... 60 V DC continuous operation

(> 30 min.) fully equipped, measured at
max. ambient temperature)
n
Load-dump protection up to 120 V
Fully operational, not time-limited

Meets transient test case of 48 V
vehicle onboard power supply system
n
70 V 100 V DC1)
n Delayed shutdown depending on input
overvoltage level and load
n
Reverse polarity protection up to -100 V DC1)
n
Max. input current2)
Software
n
30 A at 12 V input voltage
n
20 A at 12 V nominal
n
15 A at 24 V input voltage
n
10 A at 24 V nominal
n
7.5 A at 48 V input voltage
Input protection
n
Adaptive overcurrent/short-circuit protection
Start-up current
n
Max. 6 A
n
32 A foldback current line
n
60 A external fuse
n
50 A
n
Soft start
n
< 1 mA with remote off at 12 V
Hardware
n
230 ms at 12 V DC start-up time
Quiescent current
n
< 1 mA with remote off
n
< 3 mA with remote off at 48 V
n
40 A, +5 V
n
40 A, +5 V
n
10 A, +12 V
n
7 A, +12 V
n
3 A, -12 V
n
3 A, -12 V
Max. output power2)
n
300 W
n
270 W at 12 V nominal input voltage
Efficiency
n
85% within input voltage operation range
n
60% at 12 V nominal input voltage
Max. output currents2) 3)
n
Approx. 90 % at 48 V input voltage
n
100 V
Power input connector
n
7-pin male connector
n
250 V
General
n
Overvoltage-protected remote on/off input. Overvoltage protection of the remote pin is also 100V.
Engineering
Remote control
Input/output isolation1)
If the remote pin is connected directly to the vehicle battery, AutoBox will always be on, and the
vehicle battery will soon be exhausted if the engine is not running. A switch is therefore highly
recommended.
Input resistance at remote input n 44 k tied to GND
n
47 k tied to GND
Remote on voltage
n
>4V
Remote off voltage
n
<1V
Maximum voltage between any input pins or any output pins and output ground must not exceed 100 V.
Cannot be reached in the standard AutoBox configuration (DS1005 or DS1007 with various I/O boards).
3)
2)
2015
489
1)
Specification
Parameter
AutoBox
Shock and vibration test EN 60068-2-6
Tandem-AutoBox
n
Mechanical vibration test
n
Test conditions: sinusoidal vibration, 3-axis test, 5 ... 2000 Hz, up to 9 g, 30 min per axis
n
During this test, AutoBox continuously executed a program incl. I/O without any failures
EN 60068-2-27
n
Mechanical test of shock resistance
n
Test conditions: shock, 3-axis test, 11 ms at 15 g
n
During this test, AutoBox continuously executed a program incl. I/O without any failures
Mounting positions
n
Horizontal position (with shock mounts below)
n
Vertical position
n
Not allowed: upside-down position
Grounding
n
Circuit ground is connected to the backplane ground, which is isolated from the vehicle battery
Physical size
n
195 x 220 x 480 mm (7.7 x 8.6 x 18.9 in) incl. n 195
ground
shock mounts
n
Approx. 6.5 kg (14.3 lbs)
n
Approx. 10.6 kg (21.2 lbs)
Ambient temperature1)
n
0 ... 55 C (32 ... 131 F)
n
0 ... 55 C (32 ... 131 F)
1)
490
x 400 x 495 mm (7.7 x 15.7 x 19.5 in)

incl. shock mounts
ambient temperature applies.
2015
Introduction
Order Information
Only AutoBox
(without host
interface)
Ethernet
Interface
PCMCIA Link
PCI Bus Link
PCI Express Link
ExpressCard Link
AutoBox
n
ABX_BOX_ONLY
n
ABX1
n
ABX/814/815
n
ABX/814/817/Opto
n
ABX/814/819/Opto
n
ABX/814/821
Tandem
AutoBox
n
TABX1
n
TABX/814/815
n
TABX/814/817/Opto
n
TABX/814/819/Opto
n
TABX/814/821
2015
491
Engineering
Hardware
Software
Product
Application Fields
Order Number
Accessories / Link Boards
Link Boards
Connecting a host PC with dSPACE systems
Highlights
n Connection via different link types
(ISA, PCI, PCI Express, PCMCIA, ExpressCard or Ethernet)
n Partitioning the peripheral high-speed (PHS) bus
Several Connection Options

There are several options for connecting an Expansion Box
or AutoBox to your host PC/notebook: The physical connection is established via a high-speed serial or optical link.
There are Link Boards for connecting host PCs via ISA,
PCI, PCI express, PCMCIA, ExpressCard or Ethernet with
100 megabit/s technology1).
Host PC
AutoBox/
Expansion Box
Ethernet
Ethernet
Interface
492
1)
2015
PCMCIA
DS815
PCI bus
DS817
PCI Express
DS819
ExpressCard
DS821
High speed serial link
Optical connection
Optical connection
High speed serial link
Slot CPU
DS814
DS814
DS814
DS814
This is the capability of the hardware components and circuits of our products. Depending on the software, the achievable
performance figures can deviate significantly from this hardware specification.
Introduction
Accessories / Link Boards
Partitioning the PHS Bus with the DS802 PHS Link Board
Board is for adding and removing a simulators slave systems
in response to changing tasks. Slave systems can be replaced
within one simulator or exchanged between simulators. This
setup is ideal for all applications that do not need processing
power in every expansion box and ensures optimal utilization
of your simulator resources. Master-slave systems can of
course be combined with multiprocessor systems.
Application Fields
Modular I/O
With the DS802 PHS Link Board, you can spatially partition
the PHS bus by arranging the I/O boards in several expansion
boxes. The box which contains the processor board is the
master box. Boxes which contain only I/O boards are
slave boxes. One DS802 must be installed in the master box
and one in every slave box. The DS802 boards provide the
necessary link between the boxes via fiberoptic cable (up
to 100 m). A typical use scenario for the DS802 PHS Link
Slave-Box
DS802
PHS
I/O
Software
Optical
connection
I/O
Master-Box
Processor
Board
DS802
Slave-Box
I/O
DS802
PHS
I/O
PHS
I/O
Gigalink
DS802
Hardware
Slave-Box
(Additional slave-boxes)
2015
493
Engineering
With the DS802 PHS Link Board, you

can partition the PHS bus by arranging
the I/O boards in several expansion
boxes up to distances of 100 m apart.
Only the master box contains a processor
board, ensuring optimal utilization of
your simulator resources.
PHS
Accessories / DS830 MultiLink Panel

Connection of several dSPACE systems to one host PC
Highlights
Three variants: For up to 4, 8, and 16 connections
n Support of ISA, PCMCIA, and PCI host connection
n
Application Areas
Flexibility is crucial when it comes to extending the
topology of your dSPACE system. With the DS830 MultiLink
Panel, you have the advanced option of linking up to
16 dSPACE systems to only one host PC. The linked systems
might be expansion boxes, AutoBoxes or MicroAutoBoxes1). Your benefit: All parts of the dSPACE system are
under the supervision of only one host PC.
Only One Slot Needed

To connect the DS830 MultiLink Panel to your host PC, you
need only one PCI express, ExpressCard, PCMCIA or PCI slot.
This link features a transfer rate of 100 Mbit/s. Depending
on your cable length requirements for the system to be
linked, you can establish a connection via a crossed patch
cable or fiber-optic cable. To connect the DS830 to the host
PC as well as to the dSPACE boxes, you can use any combination of crossed patch cables and fiber-optic cables. For
example, you can connect the DS830 to the host PC and an
expansion box via a fiber-optic cable, and to a MicroAutoBox1) via a patch cable.
1)
1)
...
494
2015
1)
Introduction
Accessories / DS830 MultiLink Panel
Technical Details
Parameter
Specification
Physical connection
n
Host PC connection: High-speed up-link interface (100 Mbit/s)
DS830/4
DS830/8
DS830/16
n
Host PC connection requires only one dSPACE link board (p. 492)
n
Expansion hardware connection: High-speed down-link interface (100 Mbit/s)
n
Up to 4 expansion boxes and/ n
Up to 8 expansion boxes and/ n
Up to 16 expansion boxes and/
Protocol
n
High-speed serial link (proprietary)
Max. transfer rate
n
100 Mbit/s1)
or MicroAutoBoxes
Status LEDs
or MicroAutoBoxes
Application Fields
n
Link medium: Fiber-optic cable (multi mode 50/125 m) or crossed patch cable (twisted pair CAT5 STP)
Connectable boxes
or MicroAutoBoxes
n
Various LEDs displaying the current status of each connection and the power supply
Enclosure
n
Aluminum box
Physical size
n
201.6 x 56.0 x 108.6 mm
(7.9 x 2.2 x 4.3 in)

Approx. weight
n
0.75 kg (1.65 lb.)
Ambient temperature
n
0 ... 50 C (32 ... 122 F)
n
288.0 x 56.0 x 108.6 mm
n
460.8 x 56.0 x 108.6 mm
(11.3 x 2.2 x 4.3 in)

n
1.10 kg (2.43 lb.)
n
1.70 kg (3.75 lb.)
n
24 W
n
40 W
(18.1 x 2.2 x 4.3 in)
n
16 W
Power supply
n
+6 V ... +58 V DC
Software
n
Active cooling (fan)
Power consumption
n
Power supply via mains socket or a car battery (power supply cables are part of the DS830
hardware package)
n
Mains socket cable includes a power supply unit (15.0 V, 4.0 A)
1)
The transfer rate describes the capabilities of the hardware components and circuits of dSPACE products. Depending on the software complexity
the attainable overall performance can deviate significantly from the hardware specification.
Product
Order Number
DS830/4 MultiLink Panel
n
DS830-4
n
DS830-8
n
DS830-16
Hardware
Order Information
Relevant Hardware
2)
Order Number
n
Expansion boxes
See p. 484
n
Link Boards
See p. 492
n
AutoBoxes
See p. 488
n
MicroAutoBoxes2)
See p. 522
Engineering
Optional
2015
495
Hardware
Simulator Hardware / dSPACE Simulator MidSize
dSPACE Simulator MidSize

Standardized, offtheshelf HIL simulator based on DS2202 or DS2211 HIL I/O Board
Highlights
n For ECU function and integration tests
n Ideally tailored for testing powertrain, vehicle
dynamics and body ECUs
n Signal conditioning, load simulation and
electrical failure simulation
n Open and scalable
496
Open Hardware Concept

dSPACE Simulator Mid-Size is a ready-to-use, standard
hardware-in-the-loop (HIL) simulator for testing automotive ECUs systematically and automatically.
The simulation model runs on the processor hardware
(single-processor or multiprocessor systems). dSPACE Simulator Mid-Size generates and measures I/O signals via the
integrated dSPACE I/O boards. The function range is complemented by load and failure simulation.
Typical Fields of Application

n Engine, transmission, vehicle dynamics and body
electronics HIL
n Open-loop or closed-loop environment
n Realistic unit tests
n Function integration tests, release tests, and ECU
diagnostics tests
n Automated testing
n Real-time simulation
n Electric drives applications (combined with Electric Motor
HIL Solution (p. 464) or DS5203 FPGA Board (p. 438))
Hardware Details
The hardware of dSPACE Simulator Mid-Size is mounted in
a 19 desktop rack (standard height: 6 -12 U).
The DS1005 PPC Board, DS1006 Processor Board, and
DS1007 PPC Processor Board can be used as processor
boards. The DS2202 or DS2211 HIL I/O Board generate and
measure the I/O signals. The signal conditioning, loads, failure insertion units (FIU) and power supply are also mounted
in the 19 rack. Additional I/O, signal conditioning, fault simulation, and current measurement can be added on request.
Connection to Host PC
All dSPACE software for experiment setup and control or
test automation runs on your PC or notebook. The dSPACE
Simulator hardware is connected to your PC via link boards
(p. 492).
2015
Introduction
Simulator Hardware / dSPACE Simulator Mid-Size
Hardware Summary1)
Hardware
Description
Form factor
n 19 desktop rack
Processor hardware
n DS1005 PPC Board or

n DS1006 Processor Board or
n DS1007 PPC Processor Board
n DS2202 HIL I/O Board or
I/O hardware
Application Fields

n Additional I/O optional
Signal conditioning
Substitute loads
Real-load connector
Failure insertion unit for actuator signals
Failure insertion unit for sensor signals
Integration of additional signal conditioning
Integration of third-party hardware, e.g., load panels
ECU connectors
n Three 90-pin connectors for each load/FIU unit
Software
n Additional connectors for additional I/O optional
Break-out box
OBDII diagnostic connector /

connection to diagnostic tools
n Sub-D connector with optional CARB adapter

n CAN connector
Truck-application-capable (24V/36V)
48 V-capable
Power supply (remote-controlled)
n One or two power supplies for simulating 1-or 2-voltage systems
included
optional
Hardware
Examples of Rack Variants

Single Mid-Size (6 HU)
DS1005 PPC Board or

DS1006 Processor Board or
DS1007 PPC Processor Board
DS2202 HIL I/O Board or
Double Mid-Size (12 HU)
(1 x)
(2 x)
Failure insertion units for actuator signals
Load cards
Power supply
Second power supply
Free ISA slots for expansion
n 1 (PX5 version, only for DS1005 PPC Board
Engineering
n 2 (PX10 version), 12 (PX20 version)
and DS1007 PPC Processor Board)

n 6
Height units
n 12
included
optional
not available
1)
Devices connected to the dSPACE HIL system, for example, electronic control units, can feed in high currents and high voltages (voltages
over 60 V DC or 30 V ACRMS), which can be dangerous for the user. This can happen, for example, in systems for piezoelectric or hybrid
applications. Such currents and voltages can result in property damage, personal injury, or death. Under all circumstances, you must observe
all the safety precautions described in the documentation. Please contact dSPACE for additional safety-related equipment, such as electrically
safe interface cables.
2015
497
Hardware Components
Signal Conditioning
n On-board for DS2202/DS2211 HIL I/O Board signals
n Spare slots for additional signal conditioning (e.g., current
measurement for direct injection applications, lambda
probe simulation or signal conditioning for additional
I/O boards)
Rack for Load and FIU simulation with

external connectors for real loads
Load Capabilities
n Five load boards (per load/FIU unit), 10 single-ended
loads or 5 double-ended loads each
n Cascading of loads/FIU units with additional DS2211/
DS2202 boards
n Extendable by electrically equivalent loads or low-power
resistor loads (2W maximum continuous power per load)
n Front connector for measurement or connection of
real loads
n 6A maximum load current per pin (real loads)
n LED indicators displaying current load states (display
mode selectable)
Spare slot for additional

signal conditioning
ECU connectors
Adapter for OBDII connector
Modular hardware: processor board and
I/O board with signal conditioning
Remote-controlled power
supply (battery simulation)
Power Supply
n Simulation of car battery
n Programmable switched-mode power supply
n Remote-controlled
n Up to two power supply units for 2-voltage systems
n VBat1: 0 ... 30 V output voltage range
n VBat2: 0 ... 60 V output voltage range
n 48 V and truck-capable using VBat2
n Three switched battery rails for each battery voltage,
e.g., main relay, ECU-controlled high rail
n 16A maximum current for each rail of first battery
voltage
n 6A maximum current for each rail of second battery
voltage
498
Connectors
n Three 90-pin connectors for the ECU
n One Sub-D CARB connector (SAE J1962) for diagnostic
tools (an adapter to the standard CARB connector
is optionally available)
n One CAN connector for access to the CAN bus
n Jacks for battery voltage (for power supplies 1 and 2)
and ground
n External load connectors
2015
Introduction
n Broken wire simulation (open circuit)

n Simulation of short circuits: from ECU pins to ground or
battery voltages
n Simulation of cross-wired short circuits between ECU
pins via common fail planes
n Simultaneous activation of multiple failures (latch mode)
n dSPACE Simulator Mid-Size is also available without FIU
cards on request
Application Fields
Failure Insertion Units

A standard dSPACE Simulator Mid-Size supports electrical
failure simulation on all ECU output pins connected to the
HIL I/O Board. A hardware extension allows electrical failures
to be simulated on ECU inputs as well. The host PC controls
both types of failure simulation via an RS232 interface.
n ECU outputs (per load/FIU unit1)): DS791 failure insertion
units (FIUs)
n ECU inputs: optional DS793/DS794 failure insertion
units
n Remote-controlled with ControlDesk Failure Simulation
and automated with AutomationDesk
For more information on High-Current Failure Simulation,

please see p. 508.
Actuator-FIU
Sensor-FIU (Optional)
FIU cards
n DS791
n DS793/DS794
Number of cards per load/FIU unit
n5
n Up to 2
Number of channels per card
n 10
n Up to 81
Switch type
n Relay
n CMOS switch
Max. continuous current
n6A
n 0.5 A
Cable break
Short circuit to battery

voltage VBAT1 or VBAT2
Short circuit to another ECU

pin via common plane
Simulation of loose contact

or switch bouncing
Short circuit to ground
Hardware
Possible failure types
Software
Failure Simulation Overview
included
Other Hardware Components

n Break-out box (optional)
Expandability
n Two or more HIL I/O Boards2)
n Integration of additional dSPACE I/O board possible
n Signal conditioning for additional I/O boards
n Custom signal conditioning
n Connection of real loads, dummy resistive loads or electrical equivalent loads
n Customer-specific modifications/extensions possible, for

example larger 19" rack with break-out boxes, ECU subracks, real load drawers, etc.
n 1- or 2-voltage systems
The number of load/FIU units depends on the number of HIL I/O Boards.
Requires larger 19" rack.
1)
2)
2015
499
Engineering
not available
Simulator Hardware / dSPACE Simulator FullSize
dSPACE Simulator FullSize

Modular simulator concept, with offtheshelf
components according to your needs
Highlights
n HIL systems tailored to your needs
n No limit regarding application range
n For testing complex single ECUs to large ECU networks
in any kind of application field
n Flexible and open hardware concept
n Freely expandable by any dSPACE I/O board
n High current applications (hybrid drives)
500
Hardware Details
dSPACE Simulator Full-Size is mounted in a 19 cabinet
whose height depends on your requirements. The dSPACE
processor boards and I/O boards are mounted in a standard PX20 Expansion Box (p. 484). The PX20 Expansion
Box provides 20 slots for dSPACE boards. An additional
Expansion Box can be integrated on request. Several PX20
Expansion Boxes can be integrated in a multirack system,
so you never face restrictions on expandability.
Typical Fields of Application

n Engine, powertrain, chassis, and body
n Comprehensive closed-loop tests on ECUs, release/
acceptance tests
n Networked ECUs
n Special requirements, e.g., with high system flexibility,
or high current applications
n Truck applications
n Racing applications (Formula One, rally)
n Electric motor simulation for hybrid or electric powertrains
and electric steering systems
n Battery management systems
n Mechanical test benches
Open Hardware Concept

The simulation model runs on the processor hardware
(single-processor or multiprocessor systems). dSPACE Simulator generates and measures I/O signals via the integrated
dSPACE I/O boards. The signal conditioning, loads, failure
insertion units and power supply are also mounted in the
19 cabinet. The number of components, and their types,
depend on your requirements and are configured to fit your
application.
Connection to Host PC
All dSPACE software for setting up and controlling experiments or test automation runs on your host PC or notebook.
The dSPACE Simulator hardware is connected to your PC
via Link Boards (p. 492).
2015
Introduction
Simulator Hardware / dSPACE Simulator FullSize
Hardware Summary1)
Hardware
Description
Form factor
Processor hardware
19 cabinet, 17 ... 42 U
DS1005 PPC Board or

DS1006 Processor Board or
n DS1007 PPC Processor Board
n
n
Any number and type of dSPACE I/O boards
Signal conditioning
Substitute loads
Realload connector
Failure insertion unit
Integration of simulator extensions (p. 505)
Integration of thirdparty hardware, e.g., load panels

ECU connectors
Application Fields
I/O hardware
One or more 90pin connectors for each ECU (standardized)

n Additional connectors optional
n
Breakout box
Truck applicationscapable (24 V/36 V)
Software
OBDII diagnostic connector / connection to diagnostic tools n Standard 16pin CARB connector
n Diagnostic connectors (CAN, Kline)
n Others on request
48 Vcapable
Power supply (remote controlled)
One or two power supplies for simulating 1 or 2voltage systems
included
optional
1)
2015
501
Engineering
Hardware
Simulator Hardware / dSPACE Simulator Full-Size
Hardware Components
Current measurement boards FIU
RSIM module
Sub-D connector (for CAN measurements)
Main power supply unit (AC)

Power switch for ECU power supply
SC (signal conditioning) power unit

Power supply unit for battery simulation (DC)
OBD diagnostic connector
Range for FIU/load/current measurement,

power switches (everything except signal
conditioning)
BOB (break-out box)

ECU and (optional) external real loads
Real load drawer,
Pull-out rack for measurement devices
(optional)
Sub-D connectors
Signal conditioning
Power outlet strip (optional)

Modular hardware:
processor boards and I/O boards
Modular Hardware
n Single-processor or multiprocessor systems
n Freely expandable by any dSPACE I/O board (Modular
Hardware, p. 348), according to your requirements
n PX20 Expansion Box for modular hardware (processor
and I/O boards)
n Modular signal conditioning concept (customer-specific
configuration)
n Expandable, e.g., with hardware for failure insertion
and load simulation (customer-specific configuration)
502
Signal Conditioning
n Signal conditioning for all dSPACE I/O boards
n Supports almost any signal type: e.g., digital in,
digital out, analog in, analog out, relay simulation,
current sink/source, LVDT simulation, resistance simulation and linear lambda probe simulation
n Further modules on request
2015
Introduction
Power Supply
n Simulation of car battery
n Programmable switched-mode power supply
n Remote-controlled
n 48 V and truck-capable: 0 ... 60 V voltage range
Other Hardware Components

n Break-out box (optional, integrated in cabinet or external)
n Optional inclusion of third-party hardware; e.g., load
panels, signal routing units, GPIB instruments
n Power switch modules (p. 506)
Load Capabilities
n Modular load concept (customer-specific configuration)
n Support of single-ended and double-ended loads
n Resistive loads or other kinds of equivalent loads
n Connection of electrically equivalent loads or lowpower resistive loads
n Connection of real loads, can optionally be integrated
in the cabinet
n Integration of customers load panels
n High-speed electronic loads (e.g. for emulation of
electric motor)
Software
Hardware
Engineering
n Simulation of cross-wired short circuits between ECU pins

n Simultaneous activation of multiple failures (latch mode)
For more information on High-Current Failure Simulation
please see p. 508
2015
503
Failure Insertion Units

n Modular FIU concept (customer-specific configuration)
n Failure insertion unit (FIU) for ECU inputs and outputs
n Remote-controlled with ControlDesk Failure Simulation
(or optionally with AutomationDesk)
n Broken wire simulation (open circuit)
n Simulation of shorts: shorts from ECU pins to ground,
battery voltage, or switched rail
Application Fields
Expandability
n Maximum flexibility through modular concept
n Minimum hardware modification when requirements
change
n Supersets with spare signals, allowing tests on several
ECU variants, even after ECU pinout changes
n All signals accessible on terminal strips for additional
measurement tasks and for flexible response to changing specifications
n Clear and transparent system architecture
n Multirack systems possible
Failure Simulation
Failure Simulation Variant 1
Our standard variant for failure simulation on dSPACE Simulator Full-Size supports failure simulation on all ECU input
and output pins. All digital and analog I/O boards from
dSPACE are supported by failure simulation. The relay boards
(DS291) for failure simulation can be used on their own for
failure simulation on sensor signals (ECU inputs) or in conjunction with load boards (DS281) on actuator signals (ECU
outputs). Failure relays are controlled via a serial RS232.

Our second failure simulation variant uses a central relay
switching matrix (DS293) for failure simulation on ECU
inputs and outputs. 5 different system potentials (for example, Terminal 30, Terminal 31, Terminal 15) can be switched
in on three different rails via load modules (DS282). Further
devices that can be connected include various measurement devices (Meas0-4), an electronic source (Source), and
Rsim modules for transition impedance. Failure simulation
is controlled via a CAN interface.
Failure Simulation Summary

dSPACE Simulator Full-Size
FIU cards
n DS291
n DS282
Number of cards per simulator
n Configurable
n Configurable
n 10
n 10
Switch type
n Relay
n Relay
Central modules
n 1 x DS293
Simulation of transition impedance
n 1 x DS289 Rsim Module (simulates a
n8A

resistance in the range 1 ...131k

in steps of 1)
n8A
Cable break
Short circuit to battery voltage
Short circuit to another ECU pin via common

fail plane
Cable break with additional hardware (Rsim,

Meas or Source) inseries
Short circuit to another ECU pin via additional

hardware (Rsim, Meas or Source)
Short circuit to 5 reference points (potential

0 ... 4) directly or via additional hardware
(Rsim, Meas or Source)
included
not available
504
2015
Simulator Hardware / Simulator Extensions
Introduction
Simulator Extensions1)
Examples of simulator extensions
Application Fields
Highlights
1)
Engineering
Hardware
The list shown below is typical of many application areas,

and you can also add or remove as many components as
you like.
n Interfaces to diagnostic and calibration hardware to
supplement the default interfaces
n Real system components
n Break-out boxes
n Failure insertion units
n Programmable power supplies
n Power switch module
n Signal conditioning
n Simulation of linear lambda probes
n CAN gateway
n Electronic loads
n Battery cell voltage emulation
n Others
2015
505
Tailor-made solutions
Further simulator-specific hardware can be integrated into
your dSPACE Simulator in addition to the modular hardware
listed in this catalog. This simulator-specific hardware can
include real system components, as well as measurement
and diagnostic tools. The components and tools can be built
and integrated by dSPACE, or you can do it yourself.
dSPACE Simulator Full-Size can be equipped with simulatorspecific hardware for optimum tailoring to your specific
needs. dSPACE Simulator Mid-Size can also be similarly
equipped to a certain extent.
Software
n Power switch
n CAN gateway
n Bus FIU
n Electric drives
n Custom adaptation
n Break-out boxes
Examples of Simulator Extensions

Customized Interfaces to Diagnostic and
Calibration Hardware
Many companies already have their own diagnostic and
calibration hardware to perform tasks such as reading out
internal ECU variables from the failure memory. If you do
not intend to run this functionality on dSPACE Simulator, the
hardware is connected to dSPACE Simulator via appropriate
interfaces, which might in some cases need a little engineering. You can connect any kind of measuring device, digital
scope, and diagnostic device you like with special protocols
such as GPIB or RS232.
Real System Components

In some cases, the real system components (such as injection valves, hydraulic components, and sensors) have to
be integrated into dSPACE Simulator. This is necessary, for
example, if these components come from different suppliers
for one and the same ECU and have to be checked together
with the ECU within the simulated environment. Moreover,
not every vehicle component can be simulated precisely
enough with a justifiable amount of time and money, and
some ECUs require real loads at their outputs in order to
function at all.
Power Switch Module

ECUs consume power even when the vehicle is parked.
Many modern ECUs have a sleep mode to avoid draining the
vehicles electrical system unnecessarily. Some ECUs therefore
contain a CAN transceiver capable of wake-up/sleep mode,
which allows the ECU to run only if it is needed and switches
it off otherwise. Power switch modules provide the possibility to connect each ECU to the standard battery terminals
(e. g. T30, T15, T50) and to measure the current consumption of each ECU separately in different current ranges from
A up to 50 A. Moreover, systems with networked ECUs
often require different power supply voltage levels. Each
power switch module can therefore handle two power supply lines to simulate different vehicle electrical systems within
dSPACE Simulator. Even the sequence when a vehicle is
starting up can be simulated.
A measurement unit allows the precise current measurement
of each ECU supply line in different current ranges, even
in the microampere range. For example, current consumption during ECU sleep mode can be compared with normal
operation mode consumption. The module is controlled by
software via a CAN interface.
Programmable Power Supplies

The programmable power supply unit supplies the components to be tested and allows the simulation of real voltages such as a vehicles battery voltage during start-up.
The power supply unit is remote-controlled from within
the real-time model.
Various power supplies are available for different applications, for example:
n 0 ... 20 V (e.g., passenger cars)
n 0 ... 60 V
506
Break-Out Boxes
An optional break-out box makes all ECU pins directly
accessible. This simplifies the measurement and input of
signals. The break-out boxes can be integrated into dSPACE
Simulator, or take the form of external desktop boxes.
Third-party break-out boxes can also be included.
2015
Introduction
Simulator. Signal manipulation by software allows you

to manipulate any CAN messages from any ECU, with a
predefined effect on the other ECUs in the CAN network.
The CAN software (RTI CAN MultiMessage Blockset, p. 70)
offers a huge range of typical error situations right up to
message or individual signal level.
Application Fields
CAN Gateway
In large-scale CAN networks, the testing of bus communication plays a key role. Engineers need to test the behavior
of ECUs and distributed functions when an expected CAN
message fails to arrive or contains unexpected signals.
To simulate errors, a CAN gateway module is inserted into
the CAN network (see graphic). Each ECU can be connected
individually to one of the two CAN controllers in the dSPACE
CAN gateway software

Signal manipulation
Tx
Rx
CAN
controller 1
ECU 1
Tx
CAN
controller 2
ECU 2
Hardware
Rx
Software
Signal
manipulation
ECU n
CAN gateway hardware
The LSU module allows Nernst cell voltage to be generated

on four independent channels, according to pump current
and Nernst cell inner resistance. The module functions as a
linear probe or as a jump probe. Parameters such as maximum/minimum Nernst cell voltage can be adjusted.
2015
507
Simulation of Linear Lambda Probes

LSU (Lambda-Sonde universal, universal lambda probe) is a
signal conditioning module for dSPACE Simulator Full-Size
and Mid-Size that simulates the behavior of linear lambda
probes. These probes measure the air-fuel ratio in a cars
exhaust system. The engine ECU reacts by varying the injection time so that the catalytic converter can operate at an
optimal performance rate.
Engineering
CAN gateway for simulating errors in large ECU networks.
Failure Simulation
DS1450 Bus FIU Board
Offers the essential options of electrical failure insertion for
the physical layer of buses such as FlexRay. These options
include short circuits, open circuit, and varying termination
resistance.
DS1450 Bus FIU Board
Specification
Hardware
n Supports 4 bus channels in parallel

n Usable for dSPACE Simulator Mid-Size and Full-Size as well as
HIL systems based on expansion boxes

n Suitable for differential bus sytems (FlexRay, CAN, etc.)
n Relay-based
Software
n Uses a specialized ControlDesk Next Generation failure pattern (p. 106)
Failure insertion options
n Short circuit to ground and to any user-defined potential (typically UBAT)

n Open circuit
n Varying termination resistance

n Switching cross short-circuits
High-Current Failure Simulation

Our high-current failure simulation unit on dSPACE Simulator supports failure simulation on ECU inputs and outputs.
One FIU controller card (DS5355) supports up to 19 signal
channels on two High Current FIU Relay Trays (DS5390). Due
to its modularity, the FIU controller card can be expanded
to increase the number of channels. These relay trays allow
failures with currents up to 50 A and voltages of up to 300 V.
The FIU is controlled from ControlDesk Next Generation via

a serial RS232 or CAN and can be combined with dSPACE
Simulator Mid-Size and Full-Size.
High-Current FIU for dSPACE Simulator

FIU cards
n DS5355/DS5390
Number of cards per simulator
n Configurable
n Up to 19
Switch type
n Relay
n 50 A
Possible failure types Cable break
Short circuit to battery voltage
Short circuit to another ECU pin via common fail plane
included
508
2015
Introduction
dSPACE External Failure Insertion Unit (FIU) is an easy way

to upgrade a simulation system with a failure insertion unit.
The external FIU can be interconnected between the ECU
(electronic control unit) and the hardware-in-the-loop (HIL)
system without further configurations. The external FIU
offers 90, 180 or 270 channels, which can be used for
actuator failure simulation and also for sensor failure simulation. The external FIU can optionally be equipped with an
integrated Break-Out-Box (BOB).
For designing and controlling the failure patterns, the Failure Simulation Model of ControlDesk Next Generation
is used (p. 106).
Application Fields
External Failure Insertion Unit
These failure patterns can be activated and processed with

AutomationDesk (p. 156). You simply integrate the needed
failure pattern into you test sequence. During the execution of the test sequence, the failure pattern is activated
on the ECU.
Parameter
Specification
Software
Technical Details
No. of cards per rack
No. of channels per card
10
Rack variants
(each with BreakOutBox (BOB) optional)
Switch type
Relay
Control
RS232 interface via Failure Simulation Module of ControlDesk Next Generation
Connection interface
90 channels
180 channels
n 270 channels
Hardware
Front: female Hypertac connector for connection to ECU

Rear:
n Male hypertac connector for connection to simulator hardware (cable length max 1.5 m)
n Plug connector for VBat and GND
n
8 A per channel
Cable break
n Short circuit to battery voltage
n Short circuit to another ECU pin via common fail plane
n
20 at the same time
Physical characteristics (depend on the variant)
Form factor: 39 U
External power supply
12 V / 100 W
Product
Order Number
External Failure Simulation with BreakOut Box

(90, 180 or 270 channels)
External Failure Simulation without BreakOut Box

(90, 180 or 270 channels)
EXTFIU90PINS_B
EXTFIU180PINS_B
n EXTFIU270PINS_B
n
EXTFIU90PINS
EXTFIU180PINS
n EXTFIU270PINS
n
2015
509
Max. failure patterns
Engineering
Electronic Load Emulation

Combination with dSPACE Simulator and SCALEXIO
dSPACE offers two variants of electronic load modules for
different voltage ranges. The DS5380 (up to 30 V) and the
DS5381 (up to 60 V) can be used for HIL simulation with
dSPACE Simulator (p. 496) or a SCALEXIO system (p. 296).
Eletcronic load emulation covering a voltage range up to

800V is possible on request.
DS5380 Electronic Load Module (Voltage Range: 30 V)

Electronic Load Module
For the hardware-in-the-loop emulation of electrical machines, such as motors or generators, dSPACE offers the
Electronic Load Module. The module is optimized for highspeed operation as required for emulating electric motors
such as those in electric steering systems. It can work as both
a current sink and a current source to provide bidirectional
current flow, i.e., it generates or consumes real current on
ECU motor outputs. The Electronic Load Module can be
Key Features
n Current sink and source capability
n High-speed current regulation ideal for loading PWM
power stages
n Simulation of current ripple
n Different types of electric motors
n Remote-controlled by standard 10 V analog signals
combined with the DS5203 FPGA Board (p. 438) used in a

dSPACE Simulator or the DS2655 FPGA Base Board (p. 311)
used with SCALEXIO. In combination with the XSG Electric
Components Library (p. 249), they provide the fast reaction
times required for controlling electrical machines. In both
cases the FPGA computes parts of the simulation model for
the electrical machine, e.g., from the XSG Electric Components Library, and operates the Electronic Load Module.
Technical Details
The Electronic Load Module DS5380 contains two independent load channels, which can control a unipolar current
through its output stage. It provides high-speed current
regulation of less than 5 s. Each module can provide continuous current of 30 A and 300 W, and a maximum voltage
of 30 V can be applied. Several modules can be connected
in parallel to increase the current. Cooling is performed by
a temperature-controlled fan. The modules are protected
against overload and overtemperature. The control options
can be configured via jumper switches. The two channels can
be used as a sink and source device (bidirectional current)
or they can be switched in parallel to double the maximum
current if a current flow in only one direction is required.
This expands the range of applications beyond electric motor simulation.
For further information, please refer to
n DS5203 FPGA Board (p. 438)
n DS2655 FPGA Board (p. 311)
n XSG Electric Components Library (p. 249)
510
2015
Introduction
The module is perfect for emulating three-phase electric

motor units. Energy recuperation is also included to boost
the energy efficiency of the overall system. Typical test application areas are electrically supported steering, starter and
generator systems, and mild hybrid drives. Several loads can
be operated in parallel to achieve higher electric currents.
Power Recovery
The Electronic Load Module DS5381 uses the same supply
voltage as the device under test (ECU). It is equipped with
bidirectional working voltage regulators so that the current
that is sunk on one pin can be sourced to another pin. This
means that the effective power which is simulated on the
Load pins can be much higher than the power consumption of the electronic load.
Operation Modes
The Electric Load Module can be operated in three diffe
rent modes:
n Current control mode (typically used for motor appli
cations, not BLDC motors)
n Voltage control mode (general-purpose applications)
n Mixed current and voltage control mode (BLDC motor
applications)
Software
This dSPACE Electronic Load Module emulates motor and

generator currents at voltages of up to 60 V for the hardware-in-the-loop (HIL) simulation of electric motors. Highly
dynamic switching between the current and voltage control
modes enables emulation of floating brushless DC (BLDC)
motor phases without additional booster components.
With a voltage range up to 60 V, the module is also ideal
for use with higher on-board vehicle voltages of 48 V.
Application Fields
DS5381 Electronic Load Module (Voltage Range: up to 60 V)
2015
511
Engineering
Hardware
The mode parameter can be set from the host via protocol.
DC-link+
Microcontroller +
MOSFET driver
FPGA + MOSFET driver
E-load
type-B
Battery
ECU
DC-link-
dSPACE host system
ECU diagnostics
DS5831 Electronic Load Module Data Sheet
512
Control supply voltage
12 V
Control supply current consumption
3.8 A (includes fans at full speed)
Load supply voltage (battery voltage) for operation
6 ... 60 V
Load supply current consumption
Approx. 20% of the nominal load current (48 V battery voltage / 50 Arms
motor phase current on 3 phases)
Internal DClink voltage
1680 V
Motor phase current
050 Arms continuous, 100 A peak
Maximum power output (threephase motor simulation)
3,300 W
Dimensions
483 x 88 x 645 mm (19.0 x 3.5 x 25.4 in)
Weight
15.5 kg
2015
Introduction
Electronic Load Emulation (Voltage Range: up to 800 V)
2015
Application Fields
Software
Hardware
How the Electronic Load Emulator is Implemented

The load emulator uses inverters from the ServoOne series
by LTi. The electric motor model for computing the induced
voltages is implemented on a dSPACE real-time system by
means of Simulink.
The model components that can be simulated include
the drivetrain. Various sensor and actuator simulations
are added to the real-time system for this, according to
project-specific requirements. A hybrid ECU requires at
least one appropriate simulation of an engine speed sensor
(such as a resolver).
Applications
The concept of the electronic load emulator can be used
for simulating all types of motor. The physical properties of
each motor, such as motor inductivity, torque generation
and power consumption, are represented very realistically.
For variable inductivities (such as in an interior permanent
magnet or IPM motor, or with saturation effects), mean values
have to be used in the load emulator due to the constant
substitute inductivities. Nevertheless, correct representation of the torque and
the power is possible.
Any desired hybrid
and electrical vehicle
configuration can be
simulated by using
different electric motor
models in conjunction
with variable drivetrain
models (for example,
Automotive Simulation
Models from dSPACE).
The concept
is also suitable for various industrial
HIL applications.
Engineering
How the Electronic Load Emulator Works

The electronic load emulator emulates the variable, active
parts of the voltages uEMK induced in the motor coils, while
the inductive behavior of the motor coils is represented
by equivalent substitute inductivities LMotor. The induced
voltages uEMK are calculated in real time by an electric motor
model and implemented by the electronic load simulator.
and safer to operate. Tests can be run at a very early stage,

even if the real drive motor is not yet available. Moreover,
it is also possible to simulate different motor types. Unlike
mechanical test benches, these simulators have no restrictions on dynamic processes.
The electronic load emulator covers voltages of more than
800 V and power outputs of up to 100 kW. Thus, it is suitable for the HIL simulation of current and future electrical
drive systems.
513
Electronic Load Module for Simulating an Electric

Motor at Power Level at High Voltages
If the HIL tests for an electric drive system have to include the
power stages, testing at signal level is not enough. Testing
at electrical power level is essential. One way is to operate
a real drive motor on a test bench. Another is to simulate
the electric motor at the electrical power level. This involves
simulating the electrical behavior of a real motor by mapping the real terminal voltages and currents and feeding
them to the ECU. Compared with a mechanical drive test
bench, a purely electrical test bench of this kind is easier
Battery Cell Voltage Emulation

For the HIL test for battery management systems (BMS),
high-voltage batteries have to be simulated at cell level.
To make this possible dSPACE provides the high-precision
EV1077 battery cell voltage emulation board.
Due to its compact size, up to 32 cells can be combined in
one 19'', 3-U module or up to 128 cells in a 19'', 12-U rack.
The EV1077 battery cell voltage emulation board emulates a

controllable, highly precise terminal voltage for single battery cells.
Emulation Electronics Setup

Cell voltage emulation is performed with several EV1077s.
The number of these controllable buffer amplifier boards
is configured to match the battery type. The boards supply
a continuously adjustable voltage, in the range 0 to 6 V.
This relatively wide range means that damaged cells can be
emulated. For example, a voltage higher than the nominal
voltage simulates a cell's increased internal resistance during charging.
The voltage is output with a precision of 1.5 mV across
the entire working temperature range, and with a precision
of better than 1 mV within a reduced temperature range.
Compact Systems
For battery management solutions dSPACE offers compact
systems with one 19'' Full-Size Simulator rack including all
required components. The systems contains:
n Up to 200 cells for battery voltage emulation
n The real-time computing system
n A safety compartment for the ECU
514
The voltage is galvanically isolated, allowing the modules

to be connected in series up to a voltage of 800 V. A reference value step is corrected completely in less than 500 s.
Fast data transmission means that a change to all the cell's
voltages takes less than 1 ms.
The maximum current that can be supplied or sunk is 1 A,
which enables testing of passive and active cell balancing
strategies. For special requirements, up to four modules can
be connected in parallel to quadruple the maximum current.
dSPACE's Automotive Simulation Models are ideal battery
simulation models, see p. 236.
To meet safety regulations, a safety compartment prevents

accidental contact with the ECU, preventing harm due to
high voltages. With everything combined in one system,
users do not have to think about the ECU connection, but
can concentrate on their project.
2015
Introduction
Technical Data
Hardware structure
n 32 cells per 19" 3-U module
Output voltage
n 0 ... 6 V
Resolution
n 120 V
Precision (across working temperature range)
n 1.5 mV
Working temperature (environment)
n 10 ... 50 C
Maximum current (sink/source)
n 1 A, switchable in parallel
Isolation
n 60 V between the cells of a module
Application Fields
EV1077 Battery Cell Voltage Emulation Board1)
n 1000 V between cell and environment
Connection
n Ethernet, e.g., as interface to SCALEXIO
Maximum update rate for all cells
n 1 kHz
Fault simulation
n Broken wire between ECU and battery

n Short circuits between cells
Engineering
Hardware
Software
Technical modifications possible.
2015
515
1)
MicroLabBox Hardware / MicroLabBox
NEW: MicroLabBox
Compact prototyping unit for the laboratory
Highlights
n Compact all-in-one development system
for laboratory purposes
n Dual-core real-time processor at 2 GHz
n More than 100 channels of high-performance I/O
n Dedicated electric motor control features
n Ethernet and CAN bus interfaces
n Easy I/O access via integrated connector panel
Application Areas
With MicroLabBox, dSPACE introduces a fully new system
category: a compact development system for the laboratory that combines compact size and low system costs with
high performance and versatility. MicroLabBox lets you set
up your control, test or measurement applications quickly
and easily, and helps you turn your new control concepts
into reality. More than 100 I/O channels of different types
make MicroLabBox a versatile system that can be used in
mechatronic research and development areas, such as robotics, medical engineering, electric drives control, renewable
energy, vehicle engineering, or aerospace.
Key Benefits
High computation power combined with very low I/O latencies provide great real-time performance. A programmable
FPGA gives you a high degree of flexibility and lets you run
even extremely fast control loops, as required in applications such as electric motor control or active noise and
vibration cancellation.
MicroLabBox is supported by a comprehensive dSPACE
software package (see options on p. 519), including, e.g.,
Real-Time Interface (RTI) for Simulink for model-based I/O
integration and the experiment software ControlDesk Next
Generation, which provides access to the real-time application during run time by means of graphical instruments.
Two Connector Panel Variants

MicroLabBox is available in two connector panel variants
(see p. 518), each offering a different position for the I/O
connectors. The top panel variant provides Sub-D and BNC
connectors and allows easy access to the I/O when the
MicroLabBox sits on the user's desk. The front panel variant
provides Sub-D connectors, so you can use MicroLabBox
when it is stacked with other laboratory equipment, for
example. For easy wiring and signal tracing, the pinout information is shown on the units themselves and is referred
to in the I/O blockset of RTI.
516
2015
Introduction
Technical Details
Parameter
Specification
MicroLabBox
Front Panel Variant
Processor
Real-time
processor
n Freescale QorlQ P5020, dual-core, 2 GHz
Host
communication
co-processor
n Freescale QorlQ P1011 800 MHz for communication with host PC
Top Panel Variant
Application Fields
n 32 KB L1 data cache per core, 32 KB L1 instruction cache per core, 512 KB L2 cache per core, 2 MB L3 cache total
n 1 GB DRAM
Memory
n 128 MB flash memory

n Autonomous booting of applications from flash (depending on application size), ~5 s for a 5 MB application
Inter
faces
Host interface
n Integrated Gigabit Ethernet host interface
Ethernet realtime I/O interface
n Integrated low-latency Gigabit Ethernet I/O interface
USB interface
CAN interface
n USB 2.0 interface for data logging ("flight recorder") via USB mass storage device (requires a separate license)
Serial interface
LVDS interface
n 2 x UART (RS232/422/485) interface
n 2 CAN channels
n 1 x LVDS interface to connect with the Programmable Generic Interface PGI1 (support planned for a later release)
Programmable FPGA1)2)
n Xilinx Kintex-7 FPGA
Analog
input
n 8 14-bit channels, 10 Msps, differential
Resolution and
type
Software
Boot time
n 24 16-bit channels, 1 Msps, differential
Input voltage range n -10 ... 10 V

Analog
output
Resolution and type n 16 16-bit channels, 1 Msps

Output voltage range n -10 ... 10 V
Output current
Digital I/O
n 8 mA
n 48 bidirectional channels, 2.5/3.3/5 V (single-ended)
n 12 bidirectional channels (RS422/485 type) to connect sensors with differential interfaces
Electric motor control I/O

functionality (for up to
2 electric motors)
Hardware
n I/O functionality: Bit I/O, PWM I/O, SPI Master, functionality for electric motor control
n 2 x differential encoder interface
n 2 x Hall sensor input
n 2 x resolver interface2)
n 2 x SSI interface2)
n 2 x EnDat interface2)
n Multi-channel PWM
n Block commutational PWM
n 1 x 12 V, max. 3 W/250 mA (fixed)
Sensor supply
n 1 x 2 ... 20 V, max. 1 W/200 mA (variable)

n Programmable buzzer
Engineering
Feedback elements
n Programmable status LEDs
Theft protection
n Kensington lock
Cooling
n Active cooling (temperature-controlled fan)
n 4 x Sub-D 50 I/O connectors
n 48 x BNC I/O connectors

n 3 x RJ45 for Ethernet (host and I/O)

n 2 x 2 banana connectors for sensor supply
n Power supply
User-programmable via RTI FPGA Programming Blockset (p. 86). Using the RTI FPGA Programming Blockset requires additional
software.
2)
SSI, Endat, and resolver interface support are planned for a later release.
1)
2015
517
n USB Type A (for data logging)
Parameter
Specification
MicroLabBox
Front Panel Variant
Top Panel Variant
Physical
Enclosure size
characteristics Temperature
n Approx. 310 x 250 x 110 mm (12.2 x 9.8 x 4.3 in)
n 0 ... 50 C (ambient temperature)
Power supply
n 100 ... 240 V AC, 50 ... 60 Hz
Power consumption
n 125 W
Panel Variants
MicroLabBox, front panel variant
518
MicroLabBox, top panel variant
2015
Introduction
Products
Order Number
NEW: MicroLabBox, front panel variant
n MLBX_1302F
NEW: MicroLabBox, top panel variant
n MLBX_1302T
Application Fields
Order Information

Software
Optional
n Comprehensive C libraries (e.g., digital I/O support)
n For Simulink
-based use cases:

n RTI
n GNU C Compiler for Power PC (p. 98)
n MLBX_COMP
See p. 108
n For multi-core applications: ControlDesk Next Generation
n CDNG_MP
Software
Required
Order Number
n Data retrieval utility for flight recorder read-out
n For multi-core applications: RTI-MP (p. 60)
n RTI_MP
n RTICAN_BS
n RTICANMM_BS
n
NEW: RTI Electric Motor Control Blockset
n RTI_EMC_BS
n RTI USB Flight Recorder Blockset
n RTI_USB_FR_BS
n RTI Ethernet Blockset (p. 88)
n RTI_ETH_BS
n RTI FPGA Programming Blockset (p. 86)
See p. 87
n PLATFORM_API
Hardware
Order Number
n One Ethernet patch cable (HSL_PATCH) for host connection
and one power supply cable are already included with each
purchased MicroLabBox.
Additionally included with each purchased MicroLabBox
front-panel variant:
n Set of Sub-D plugs
Engineering
Included
Hardware
Multiprocessor Module (p. 126)
2015
519
Included
MicroLabBox
Block Diagram
PC
Ethernet
Controller
Ethernet
switch
USB 2.0
PGI
Interface1)
RAM
256 MB
Host
communication
co-processor
(P1011)
Interrupt
Interrupt
Controller
controller
Real-time
clock (RTC)
Local bus
Flash
64 MB
RAM
2 x 512 MB
Timer A (32 bit)

Timer
A (32
bit)bit)
Timer
B (32
Timer
B (32
bit)bit)
Timer
D (32
Timer D (32 bit)
Real-time
processor
(P5020)
Flash
128 MB
DS1202
DS1302
RAM
2 x 18 MB
Sensor
supply
I/O FPGA
I/O CPLD
ADC
DIG I/O
LED
DAC
Buzzer
CAN
UART
Connector panel
1)
520
Support of the LVDS interface to connect with the PGI1 planned for a later release
2015
Introduction
Use Cases (Examples)

net synchronous motors (PMSM). The RTI blocks for electric
motor control (p. 519) ensure convenient and comprehensive
configuration options for the I/O interfaces.
Application Fields
Developing Control Strategies for

Electric Motors
MicroLabBox is ideal for developing control functions for
many different electric motors, such as asynchronous
motors, brushless DC (BLDC) motors, and permanent mag-
Control signals
Software
Current measurement
Hall / Encoder
MicroLabBox
Hardware
Motor
Rapid Control Prototyping in Robotics

Its numerous interfaces make MicroLabBox ideal for many
kinds of robotics applications. In this example, MicroLabBox
replaces the robot's position controller and receives the robot's incremental encoder signals for determining the current
position of the robot. Then, the real-time processor calculates

the control algorithm and sends the controller output with
position and velocity data back to the robot. Thus, you can
implement and test different control algorithms very quickly.
Engineering
RTI Blockset
RapidPro Power Unit

(optional)
MicroLabBox
2015
521
Power signals
MicroAutoBox Hardware / MicroAutoBox II
MicroAutoBox II
Compact, standalone prototyping unit
Highlights
n Comprehensive I/O including CAN, LIN, K/L line,
FlexRay, Ethernet, and LVDS/bypass interfaces
n Robust and compact design ideal for in-vehicle use
n Variant with Simulink1)-programmable FPGA
n MicroAutoBox Embedded PC (p. 530)
n AC Motor Control Solution (p. 534)
n FPGA-based cylinder pressure indication (p. 533)
n Multistage watchdog mechanism (p. 529)
n NEW: Optional CAN FD module (p. 539)
Application Areas
MicroAutoBox is a real-time system for performing fast
function prototyping in fullpass and bypass scenarios.
It operates without user intervention, just like an ECU.
MicroAutoBox can be used for many different rapid
control prototyping (RCP) applications such as:
n Powertrain
n Chassis control
n Body control
n Advanced driver assistance systems (ADAS)
n Electric drives control
n X-by-wire applications
n Aerospace applications
More Features
MicroAutoBox can start up autonomously after power-up,
with ECU-like boot-up times. A PC or notebook can be
easily connected (hot-plugged) for application download,
model parameterization, and data analysis via Ethernet.
Application programs are stored in nonvolatile memory.
MicroAutoBox contains signal conditioning for automotive
signal levels and an integrated flight recorder for long-term
data acquisition (incl. support of USB mass storage devices).
522
2015
1)
Key Benefits
The special strength of the MicroAutoBox hardware is its
unique combination of high performance, comprehensive
automotive I/O, and an extremely compact and robust design
(extreme shock and vibration tests according to ISO 167503:2007, see p. 536) all for a favorable price. This lets you equip
several vehicles or a whole test fleet to check the reliability
of your control functions. With dSPACE's combination of
comprehensive software and hardware support, you can also
keep overall system costs low. In addition to the standard
I/O, MicroAutoBox offers variants with FPGA functionality for
application-specific I/O extensions and for user-programmable
FPGA applications. Moreover, there are MicroAutoBox variants
with interfaces for all major automotive bus systems: CAN,
CAN FD, LIN, K/L line, FlexRay, and Ethernet. As an option, an
additional embedded PC (p. 530) can be integrated into the
MicroAutoBox II.
Eight Standard Variants

MicroAutoBox is available in eight standard variants, each
with different interfaces and I/O functionalities. An ideal
extension for the MicroAutoBox is the RapidPro hardware
(p. 529) with its off-the-shelf signal conditioning and power stage modules. All standard variants can integrate an
additional embedded PC (p. 530).
User-programmable via RTI FPGA Programming Blockset. Using the RTI FPGA Programming Blockset requires additional software.
Parameter
Specification
MicroAutoBox II
1401/1511
Processor
Memory
n IBM PPC 750GL, 900 MHz (incl. 1 MB level 2 cache)
1401/1513
1401/1511/1512
Introduction
Technical Details (Variants 1401/1511, 1401/1513, 1401/1511/1512, 1401/1512/1513)

1401/1512/1513
n 16 MB main memory
n 6 MB memory exclusively for communication between MicroAutoBox and PC/notebook
n 16 MB nonvolatile flash memory containing code section and flight recorder data
n Depending on flash application size. Measurement examples: 1 MB application: 160 ms; 3 MB application: 340 ms
n 100/1000 Mbit/s Ethernet connection (TCP/IP). Fully compatible with standard network infrastructure. LEMO connector.
n Optional XCP on Ethernet interface to support third-party calibration and measurement tools
Ethernet real-time
I/O interface
n 100/1000 Mbit/s Ethernet connection UDP/IP (TCP/IP on request). RTI Ethernet (UDP) Blockset (optional) for read/write
USB interface
CAN interface
n USB 2.0 interface for long-term data acquisition with USB mass storage devices. LEMO connector.
access. LEMO connector.

n 6 CAN channels (partial
n 4 CAN channels
n 6 CAN channels (partial
networking supported)
Serial interface
(based on CAN
processor)
n 2 x RS232 interface
n 2 x serial interface usable
ECU interface
IP module slot for
FlexRay and CAN FD
n 2 x dual-port memory interface
as K/L line or LIN interface
n 2 slots1) for FlexRay modules (i.e., 4 FlexRay channels) or
(NEW) CAN FD modules (p. 539). Combination possible.
n 16 16-bit channels
n Xilinx Spartan-6 LX1502)3)

(additional channels with

DS1552, p. 533)
n 16 parallel channels with
1 Msps conversion rate

multiplexed channels
with 200 Ksps conversion
rate
n -10 ... 10 V
n 0 ... 5 V
n 8 16-bit channels
n 4 12-bit channels
DS1552, p. 533)

DS1552, p. 533)
n 16 multiplexed channels
with 200 Ksps conversion
rate
n -10 ... 10 V
n 8 16-bit channels
DS1552, p. 533)
n 0 ... 4.5 V
n -10 ... 10 V
n 0 ... 4.5 V
n -10 ... 10 V
n 5 mA max.
n 8 mA max.
n 5 mA max.
n 8 mA max.

n 16
Input voltage range

Analog Resolution
output
n 0 ... 5 V
n 4 12-bit channels
n FPGA-based digital I/O

n RTI software support for bit I/O, frequency, and PWM generation/measurements
PWM generation/
measurement
On-board sensors
Signal conditioning
n 40 inputs
n 24 inputs
n 40 outputs, 5 mA output
n 24 outputs, 5 mA output
n
40 inputs (additional
n
24 inputs (additional
channels with DS1552,
channels with DS1552,
p. 533)
p. 533)
current
current
n
40 outputs, 5 mA output n 24 outputs, 5 mA output
current (additional
current (additional
channels with DS1552)
channels with DS1552)
n Input / output logic levels: 5 V or levels up to 40 V (depending on VDrive), selectable
n All channels fully configurable as frequency or PWM inputs/outputs
n PWM frequency 0.0003 Hz ... 150 KHz, duty cycle 0 ... 100%, up to 21-bit resolution
n Motion sensing with 3-axis accelerometer. Pressure sensing for altitude indication.
n Signal conditioning for automotive signal levels, no power driver included
n Overvoltage protection; overcurrent and short circuit protection
n ZIF connector for I/O signals, mechanically secured, Sub-D connector for power supply
n LEMO connectors for 2 ECU interfaces, Ethernet I/O interface, USB interface, and Ethernet host interface
n Ethernet host interface for notebook/PC connection (for program load, experiment configuration, signal monitoring and
flight recorder read-out)
n Integrated Ethernet switch
IP module slot. Can also be used for other IP modules such as an ARINC interface module (via dSPACE Engineering Services, p. 580).
User-programmable via RTI FPGA Programming Blockset. Using the RTI FPGA Programming Blockset requires additional software.
3)
1)
2)
2015
Engineering
Bit I/O
523
Digital
I/O

Output current
General
Hardware
Sampling
Software
n 4 CAN channels
networking supported)
Programmable FPGA
Analog Resolution
input
Application Fields
n Clock/calendar function for time-stamping flight recorder data
Boot time
Inter
Host interface
faces
Parameter
Specification
MicroAutoBox II
1401/1511
1401/1513
1401/1511/1512
1401/1512/1513
Physical Enclosure material n Cast aluminum box

charac Enclosure size
teristics
Temperature
n Operating (case) temperature: -40 ... +85 C (-40 ... +185 F)
n Storage temperature: -55 ... +125 C (-67 ... +257 F)
Power supply
n 6 ... 40 V input power supply, protected against overvoltage and reverse polarity
Power
consumption
n Max. 25 W
Variants with DS1513 I/O Board with more CAN

Channels and more Analog I/O
MicroAutoBox II now has even more CAN channels and also
more analog inputs and outputs. The DS1513 I/O Board
increases the number of CAN channels to 6, making the
MicroAutoBox II ideal for automotive function prototyping
for electric/hybrid drives and for commercial vehicles. Its
high number of analog inputs and outputs (32 x ADC, 8 x
DAC) provides additional flexibility for connecting sensors
and actuators in areas such as combustion engines and
524
n Max. 50 W
vehicle dynamics controllers. The CAN interfaces are easy

to configure in Simulink via the dSPACE blocksets RTI CAN
and RTI CAN MultiMessage (RTI = Real-Time Interface), allowing quick, efficient configuration of the CAN network
topology. The hardware of the new CAN interfaces supports partial networking. This means that energy can be
saved by switching some CAN nodes off selectively while
others are still active.
2015
Introduction
Technical Details (Variants 1401/1501, 1401/1504, 1401/1505/1507, 1401/1507)

Parameter
Specification
MicroAutoBox II
1401/15011)
Processor
n IBM PPC 750GL, 900 MHz (incl. 1 MB level 2 cache)
Memory
n 16 MB main memory
1401/15041)
1401/1505/15071)
1401/1507
n 6 MB memory exclusively for communication between MicroAutoBox and PC/notebook
Application Fields
n 16 MB nonvolatile flash memory containing code section and flight recorder data
n Clock/calendar function for time-stamping flight recorder data
n Depending on flash application size. Measurement examples:
Boot time
1 MB application: 160 ms; 3 MB application: 340 ms

Host interface
n 100/1000 Mbit/s Ethernet connection (TCP/IP). Fully compatible with standard network infrastructure. LEMO connector.
n Optional XCP on Ethernet interface to support third-party calibration and measurement tools
Ethernet real-time
I/O interface
n 100/1000 Mbit/s Ethernet connection UDP/IP (TCP/IP on request). RTI Ethernet (UDP) Blockset (optional) for read/write
USB interface
n USB 2.0 interface for long-term data acquisition with USB mass storage devices. LEMO connector.
CAN interface
n 2 CAN channels
Serial interface
(based on CAN
processor)
n 1 x serial interface usable as K/L line or LIN interface
n 2 x serial interface usable as K/L line or LIN interface
ECU interface
n 3 x dual-port memory
access. LEMO connector.

n 4 CAN channels
interface
IP module slot for

FlexRay and CAN FD
Analog Resolution
input
Sampling
interface
interfaces
Software
Inter
faces
interface
n 2 slots2) for FlexRay modules (i.e., 4 FlexRay channels) or
(NEW) CAN FD modules (p. 533). Combination possible.

n 4 to 1 multiplexed
n Simultaneous sample & hold
n 8 12-bit channels
n 0 ... 4.5 V
Output current
n 5 mA max. sink/source current
General
n Digital I/O on 68336 slave processor, 20 MHz, with time processor unit (TPU)
n I/O software support for different applications
n 16 discrete inputs
Bit I/O
n 10 discrete outputs, 5 mA output current

n 16 shared discrete inputs/outputs, bit-selectable
n 16 TPU channels
PWM generation/
measurement
n 8 12-bit channels
Hardware
Digital
I/O
n 0 ... 5 V
n Additional digital I/O
channels available via I/O

extension on IP module slot
(5 inputs and 2 outputs,
or 2 inputs and 5 outputs,
software-selectable, 5 V
output level, 24 mA output
current)
n 4 shared inputs for frequency or PWM
Engineering
Input voltage range

Analog Resolution
output Output voltage range
n 4 PWM outputs, PWM frequency 2.5 Hz ... 100 kHz, duty cycle 0 ... 100%
n Up to 16-bit resolution
On-board sensors
n Motion sensing with 3-axis accelerometer. Pressure sensing for altitude indication.
Signal conditioning
n Signal conditioning for automotive signal levels, no power driver included
n Overvoltage protection; overcurrent and short circuit protection

n ZIF connector for I/O signals and power supply,
mechanically secured
n ZIF connector for I/O
signals and power supply,

mechanically secured
n Sub-D connectors for bus
interfaces and power supply
n Sub-D connectors for bus
interfaces and power supply
n LEMO connectors for 2 ECU interfaces, Ethernet I/O interface, USB interface, and Ethernet host interface
n Connection to a notebook/PC for program load, experiment configuration, signal monitoring and flight recorder read-out
n Additional 78-pin Sub-D connector with MicroAutoBox variants 1401/1505/1507 and 1401/1507
n Host interface: 100/1000 Mbit/s Ethernet connection (TCP/IP), see "Interfaces"
n Integrated Ethernet switch
The MicroAutoBox II hardware variants 1401/1501, 1401/1504 and 1401/1505/1507 will be available only until the end of
2015. New releases of dSPACE software are guaranteed to continue supporting these MicroAutoBox II hardware variants until
at least the end of 2018. We recommend that you use the successor variants when starting new projects.
2)
IP module slot.
1)
2015
525
Parameter
Specification
MicroAutoBox II
1401/1501
1401/1504
Physical Enclosure material n Cast aluminum box

charac Enclosure size
n Approx. 200 x 225 x 50 mm
teristics
(7.9 x 8.9 x 2.0 in)
1401/1505/1507
1401/1507
(7.9 x 8.9 x 3.8 in)
Temperature
n Operating (case) temperature: -40 ... +85 C (-40 ... +185 F)

n Storage temperature: -55 ... +125 C (-67 ... +257 F)
Power supply
n 6 ... 40 V input power supply, protected against overvoltage and reverse polarity
Power
consumption
n Max. 25 W
(7.9 x 8.9 x 2.0 in)
Order Information
Products
Order Number
MicroAutoBox II 1401/1513
n MABX_II_1513
MicroAutoBox II 1401/1512/1513
n MABX_II_1512/13
n MABX_II_1511
n MABX_II_1511/12
n MABX_II_0507
n MABX_II_1507
n MABX_II_1501
n MABX_II_1504

Software
Order Number
n Data retrieval utility for flight recorder read-out
Included
n Comprehensive C libraries (e.g., digital I/O support)
Required
n RTI
n Microtec PowerPC C Compiler
n CCPPPC
n ControlDesk
Optional
n Real-Time Interface (RTI)
Next Generation (p. 106)
See p. 108
n RTICAN_BS
n RTICANMM_BS
n RTILINMM_BS
n FCP
n RTIBYPASS_BS
n NEW: RTI AUTOSAR Blockset (p. 82)
n See p. 85
n RTI Ethernet (UDP) Blockset (p. 88)
n RTI_ETH/UDP_BS
n RTI USB Flight Recorder Blockset
n RTI_USB_FR_BS
n AutomationDesk
(p. 156)
n RTI FPGA Programming Blockset1)2)
n AUD
(p. 86)
n See p. 871)2)
n RTI DS1552 I/O Extension Blockset (p. 533)
n RTI1552_I/O_EXT_ BS
n MABXII Cylinder Pressure Indication Solution (p. 533)
n MABXII_CPI_CPU
n MicroAutoBox II AC Motor Control Solution Blockset
n MABXII_ACMC_BS
n RTI Watchdog Blockset (p. 529)
n RTI_WATCHDOG_BS
n XSG AC Motor Control Library including XSG Utils Library
n FPGA_XSG_ACMC
and XSG AC Motor Control Interface Library (p. 96)

n XSG Utils Library2) (p. 94)
526
n FPGA_XSG_UTILS
Using the RTI FPGA Programming Blockset requires additional software i.a. Xilinx products, please see the relevant product information.
1)
2)
2015
Introduction
Order Number
Included
One Ethernet Interface Cable (ETH_CAB1) is already included

with each purchased MicroAutoBox II.
Optional
n DS4340 FlexRay Interface Module (p. 538)
n DS4340
n NEW: DS4342 CAN FD Interface Module (p. 539)
n DS4342
n FlexRay interface cable
n FR_CAB1
n FlexRay interface cable for MicroAutoBox II
n FR_CAB3
Application Fields
Hardware
1401/1511/1512 and 1401/1512/1513

n Ethernet interface cable (LEMO to RJ45 connector), 5 m
n ETH_CAB1
n Electrically isolated Ethernet interface cable (300 Vrms,
n ETH_CAB2
LEMO to RJ45 connector)

n Ethernet cable to connect MicroAutoBox II and DCI-GSI2
n ETH_CAB3
n Ethernet interface cable (LEMO to RJ45 connector), 10 m
n ETH_CAB4
n USB interface cable (LEMO to USB connector) for connection n USB_CAB13
to mass storage devices ("flight recorder")

n LVDS link cable to connect MicroAutoBox and DCI-GSI1 or
n LVDS_CAB1
n LVDS_CAB15
n MicroAutoBox Break-Out Box (p. 540)
n DS1541
n DS1552 Multi I/O Module (p. 533)
n DS1552
n DS1553 ACMC Module (p. 534)
n MABXII_ACMC
n MicroAutoBox Embedded PC (p. 530)
n See p. 530
n Digital I/O extension for MABX II 1401/1507
n MABXII_1507_DIO_SOL
n MicroAutoBox II RapidPro Joining Plate1) (p. 529)
n RAPIDPRO_MABX_KIT
Shock and vibration ratings depend on the stack size. Please contact dSPACE for more information.
1)
2015
527
Engineering
Hardware
n LVDS link cable LEMO-1S to LEMO-1S, 5 m, 85 C
Software
DPMEM PODs (LEMO-1S to ZIF crimp contacts)
Block Diagram
IBM PPC
750 GL
6 MB
communic.
memory
16 MB
flash
(non-volatile)
16 MB
local RAM
Clock/
calendar
64-Bit Global Bus
Watchdog
USB
Connector
(LEMO)
ECU
interface
Connector
(LEMO)
ECU
interface
Connector
(LEMO)
Ethernet
I/O
interface
Connector
(LEMO)
Signal Generation/
Measurement
Signal
Conditioning
CAN/LIN/serial
module
Physical
CAN/serial
CAN/LIN/serial
module
Physical
CAN/serial
CAN/LIN/serial
module
Physical
CAN/serial
Digital I/O
(FPGA-based)
Signal
conditioning
& protection
32-channel
16-bit ADC
Signal
conditioning
& protection
8-channel
16-bit DAC
Signal driver
& protection
Signal Generation/
Measurement
Signal
Conditioning
I/O Connector
Local Bus/Intermodule Bus
Performance
timer
Connector
(LEMO)
Ethernet
host
interface
IP module slot
(e.g., for FlexRay)
Programmable
FPGA
528
2015
FPGA
extension slot
Optional signal
conditioning on DS1552
or ACMC Solution
Add-On Modules1)
1)
I/O Connector
IP module slot
(e.g., for FlexRay)
The modules are optional, see pp. 532-535.
Introduction
Multistage Watchdog Mechanism for More Safety

immediately and in a defined manner. This gives you an
added layer of safety when experimenting with prototype
vehicles in road and fleet tests.
Key Benefits
n Activating a predefined system behavior (e.g., system
reboot) in critical states
n Easy configuration directly in the Simulink model increases
efficiency. Same user experience as with any other RTI
blockset.
n Two-stage watchdog concept (FPGA-based hardware
watchdog and configurable software watchdogs on the
CPU) for setting up task-specific monitoring
n Configurable watchdog timeout functionality helps monitor and analyze root causes
n All MicroAutoBox II variants supported
The run-time watchdog can

easily be programmed and
integrated into controller
models via the RTI Watchdog Blockset. Configuration and execution blocks
for watchdog functionality
can be added to a model by
simply dragging them from
the blockset library into a
Simulink diagram.
Software
Application Fields
Overview
MicroAutoBox II has a multistage watchdog mechanism that
performs run-time monitoring with configurable timeout
behavior. When critical states occur, the system responds
RTI Watchdog Blockset

Order Information
Product
Order Information
RTI Watchdog Blockset
Hardware
RTI_WATCHDOG_BS
Combining MicroAutoBox and RapidPro
Compact System Setup with MicroAutoBox-RapidPro

Joining Plate1)
The joining plate enables you to combine a MicroAutoBox II
and RapidPro hardware in a one-stack-system. Such a compact system is beneficial if the mounting space is limited.
MicroAutoBox II and RapidPro units joined by the joining plate.
Order Information
Product
Order Information
MicroAutoBox II RapidPro Joining Plate
1)
RAPIDPRO_MABX_KIT
Shock and vibration ratings depend on the stack size. Please contact dSPACE for more information.
2015
529
Engineering
Flexible Signal Conditioning and Power Stages

with RapidPro
To extend the MicroAutoBox signal conditioning options,
many customers use the comprehensive signal conditioning
and power stage options of the RapidPro hardware.
MicroAutoBox Embedded PC
All Integrated
MicroAutoBox II with MicroAutoBox Embedded PC is a compact, shock- and vibration-proof system for in-vehicle use
that combines two powerful hardware units. While the actual
control functions are being computed on the real-time prototyping unit of the MicroAutoBox, additional applications such
as telematics, digital road maps and camera-based object
detection can run on the integrated MicroAutoBox Embedded
PC. With all these possibilities, the system provides immense
potential for developing advanced driver assistance, info-
tainment, telematics and image processing applications.

The integrated Ethernet switch lets the host PC access both
units via the same Ethernet connection. Different startup
and shutdown options are provided: for example, you can
remote-control both units either synchronously via the ignition switch or completely independently of each other.
The MicroAutoBox Embedded PC is an extension for the
MicroAutoBox II. There are two hardware options (see
below).
Embedded PC with Intel Atom N270
Embedded PC with Intel Core i7-3517UE
Intel Atom N270/1.6 GHz (passive cooling without fan)

2 GB RAM,
n 64 GB 2.5'' SATA SSD
n 4 x USB 2.0
n
n
Intel Core i7 dualcore processor, 2 x 1.7/2.8 GHz, 4 MB cache

(temperaturecontrolled fan)
n 8 GB DDR3 RAM
n 128 GB flash memory (64 GB integrated plus 64 GB userexchangeable
via CFAST card)
n 2x USB 2.0, 2x USB 3.0
3 x Gigabit Ethernet, and DVI video interface at front panel

Internal PCIe Mini Card slot, e.g., for optional WLAN communication
n Rearside ExpressCard slot, e.g., to support FireWire or customerspecific hardware
n Temperature range: 0 ... +60 C (+32 ... +140 F)
n Windows 7 or Ubuntu/Linux operating system
n
n
In
FPGA
DS1401
Processor
Processor
Board
Ethernet Host
Ethernet I/O
COM Express
processor
module,
Intel Core
i7 dual-core,
2 x 1.7/2.8 GHz,
8 GB DDR3
RAM
Embedded PC
Gbit Ethernet
Switch
PCIe
Mini Card
128 GB
flash memory
(64 GB
integrated
plus 64 GB
exchangeable via
CFAST card)
Express
Card
CFAST
I/O connector
Out
3 x Ethernet, 2 x USB 3.0, 2 x

USB 2.0, DVI-I, Power connectors
DS1511
I/O Board
Embedded PC
Example:
MicroAutoBox II 1401/1511 and
MicroAutoBox Embedded PC with
Intel Core i73517UE.
Order Information
Product
Order Number
MicroAutoBox Embedded PC with Intel Atom N270
MABXII_EMB_PC, Option: IA16_S64
MicroAutoBox Embedded PC with Intel Core i73517UE
MABXII_EMB_PC, Option: I7_S64C64
WLAN PCIe Mini Module for 802.11 b/g/n
EMB_PC_WLAN
530
2015
Introduction
MicroAutoBox II 1401/1512/1513 and

Embedded PC with Intel Core i73517UE
16-bit
ADC
CAN
Optional unit for

FPGA and IP modules
16-bit
DAC
DIO
PCIe Mini Card
Power supply unit
Power supply unit

Remote control
IBM PowerPC,
900 MHz,
1 MB cache
128 GB flash memory

(64 GB integrated plus 64 GB
exchangeable via
CFAST card)
IP module 1
FPGA
IP module 2
(e.g., FlexRay)
USB data
storage
LVDS
interface
Ethernet
I/O
Ethernet
host
Gbit Ethernet
ExpressCard
CFAST
COM Express
processor module,
Intel Core i7 dual-core

processor,
2 x 1.7/2.8 GHz,
8 GB DDR3 RAM
2 x USB 3.0,
2 x USB 2.0
DVI-I
Embedded PC unit
Embedded controller unit

Gbit Ethernet switch
Engineering
Hardware
3 x Gbit Ethernet
2015
531
RS232,
LIN
Remote control inputs
Software
UBat = 7 32 V
Application Fields
Block Diagram
I/O Extensions for the SimulinkProgrammable FPGA1)2)3)

Flexible Extension
The FPGA technology integrated in MicroAutoBox II
addresses new use scenarios with varying I/O requirements.
For greater flexibility, the I/O converters are sourced out to
separate add-on modules, which can easily be integrated into
the MicroAutoBox II 1401/1511/1512 and 1401/1512/1513
(only one module at a time). It is easy to change the modules later on.
Two I/O Modules Available

n The DS1552 Multi I/O Module (p. 532) is a universal
I/O module which offers many powerful I/O converters
and several interfaces. For example, it can be used for
FPGA-based cylinder pressure indication.
n The DS1553 ACMC Module (p. 534) is an I/O
module with I/O optimized for the control of various
electric drives.
I/O connector
FPGA I/O Extension Module

Out
In
FPGA
(programmable)
DS1512
FPGA Board
DS1401
Processor Board
I/O connector
Processor
FPGA
DS1511 or
DS1513
I/O Board
In
Out
DS1552 Multi I/O

Module
DS1553 ACMC
Module
and 1401/1512/1513
The FPGA I/O extension modules are easy

to integrate into the MicroAutoBox II
1401/1511/1512 and 1401/1512/1513.
Programming Options
DS1552 Multi I/O Module

Dedicated RTI blockset
Xilinx tools plus RTI FPGA Programming Blockset
1)2)3)
VHDL
1)
2)
3)
532
2015
4)
DS1553 ACMC Module
Customer-Specific Solution
via dSPACE Engineering
Services
4)
optional
optional
optional
For programming via Simulink, the RTI FPGA Programming Blockset is needed.
Using the RTI FPGA Programming Blockset requires additional software, i.a. Xilinx products, please see the relevant
product information.
Please note that due to the introduction of the Vivado software, Xilinx will no longer support the Xilinx System
Generator for DSP in combination with the ISE Design Suite after MathWorks MATLAB and Simulink Release R2013b.
XSG AC Motor Control Library (p. 96) required for the I/O framework.
Introduction
Use Case 2:
Additional I/O Channels for the Standard I/O
You can supplement the standard I/O interfaces of the
MicroAutoBox II with additional I/O channels (configurable
with RTI DS1552 I/O Extension Blockset). The FPGA is not
user-programmable, and Xilinx tools are not needed in this
use case as it is used in a predefined configuration together
with the RTI DS1552 I/O Extension Blockset.
FPGA model components created with the Xilinx System

Generator2) blockset in an XSG model with RTI blocks.
RTI DS1552 I/O Extension Blockset
Hardware
Software
Use Case 1:
User-Specific FPGA Programming
The DS1552 provides I/O interfaces for the user-programmable FPGA in the MicroAutoBox II. The FPGA is
programmed by model-based design with the RTI FPGA
Programming Blockset1)2) (p. 86) plus Xilinx software, in
VDHL or via dSPACE Engineering Services (p. 580).
Application Fields
Universal I/O Module

The DS1552 Multi I/O Module is a universal I/O piggyback
module with a large number of fast, powerful I/O converters and different serial interfaces. It is easy to install in the
MicroAutoBox II 1401/1511/1512 and 1401/1512/1513.
There are different use cases:
2)
3)
Using the RTI FPGA Programming Blockset requires additional software, i.a. Xilinx products, please see the relevant product
information.
Please note that due to the introduction of the Vivado software, Xilinx will no longer support the Xilinx System Generator
for DSP in combination with the ISE Design Suite after MathWorks MATLAB and Simulink Release R2013b.
As of December 2014, the option to add custom algorithms is still under development. For more information on availability,
please contact dSPACE.
2015
533
1)
Engineering
Use Case 3:
FPGA-Based Cylinder Pressure Indication
With the cylinder pressure indication blockset, the
MicroAutoBox II can now be used for FPGA-based cylinder
pressure measurement and indication (MABXII Cylinder
Pressure Indication Solution). The solution supports anglesynchronous pressure measurement with 0.1 max. resolution. The evaluation of the pressure values can be controlled
by several algorithms, e.g., released heat, combustion mass
center, indicated mean effective pressure. In the future you
will also be able to add your own algorithms using the RTI
FPGA Programming Blockset3).
I/O Resources of the DS1552

Specification
Parameter
Accessible via the RTI FPGA Programming Blockset1) Accessible via the RTI DS1552 I/O Extension Blockset
Analog input
n 8 parallel, 16-bit, 1 Msps analog input channels (0 ... 5 V input range)

n 16 multiplexed, 16-bit, 200 Ksps analog input channels (10 V input range)
n Sensor supply, 2...20 V configurable
Analog output
n 4 16-bit analog output channels (0 ... 5 V output range)
Digital I/O
n 16 input channels
n 16 output channels, 5 mA output current

n 8 bidirectional channels, logic level selectable (3.3 V or 5 V),
45 mA output current
Order Information
Product
Order Number
n DS1552
RTI FPGA Programming Blockset1)2)
n RTI_FPGA_BS1)2)
RTI DS1552 I/O Extension Blockset
n RTI1552_I/O_EXT_BS
Cylinder Pressure Indication Solution (RTI blockset). Open XSG library planned3) .
Please inquire
DS1553 ACMC Module

Electric Drives Control
The DS1553 ACMC Module is an I/O piggyback module with
I/O that is optimized for controlling various electric drives.
It can be installed in MicroAutoBox II 1401/1511/1512 and
1401/1512/1513. There are two different use cases:
Using the RTI FPGA Programming Blockset requires additional software, i.a. Xilinx products, please see the relevant
product information.
2)
Please note that due to the introduction of the Vivado software, Xilinx will no longer support the Xilinx System
Generator for DSP in combination with the ISE Design Suite after MathWorks MATLAB and Simulink Release R2013b.
3)
As of December 2014, the option to add custom algorithms is still under development. For more information on
availability, please contact dSPACE.
1)
534
2015
Use Case 2:
The MicroAutoBox II AC Motor Control Solution uses the
DS1553 module in conjunction with a dedicated FPGA firmware and provides a comprehensive and easy-to- use RTI
blockset for controlling various electric drives. All modeling
is performed on the processor via MATLAB Simulink no
FPGA programming by the user required.
Use Case 1: XSG AC Motor Control Library
Use Case 2: MicroAutoBox II AC Motor Control Solution Blockset

Hardware
Software
Use Case 1:
User-Specific FPGA Programming
The DS1553 provides I/O interfaces for the user-programmable FPGA of MicroAutoBox II. The FPGA is programmed by
model-based design with the RTI FPGA Programming Blockset1)2) (p. 86) plus Xilinx software or via dSPACE Engineering
Services (p. 580). The required I/O framework is provided in
a bundle with the XSG AC Motor Control Library (p. 96).
Application Fields
Introduction
I/O Resources of the DS1553

Parameter
Specification
Digital input
Digital output
8 channels, 0 ... 5 V, differential or singleended, softwareconfigurable
Analog input
16 channels, 0 ... 5 V, singleended to generate gate driver signals, PWM synchronization signals, bit out
8 additional channels by modifying IPmodule pins
n 8 channels, softwareconfigurable input voltage range (5 V, 15 V, 30 V), differential, 10 Msps
Analog output
2 channels, 10 ... 10 V (singleended) or 20 ... 20 V (differential, reference to GND)
Resolver interface
Max. position resolution 16 bits (depending on motor velocity). Generation of excitation signal (3,7,10 Vrms;
excitation frequency from 2 ... 20 kHz in 250 Hz steps (softwareconfigurable)
RS422/RS485
4 RS485 transceivers for connecting 2 serial angle meters (e.g., EnDat or SSI interface)
12 V: max. 50 mA
5 V: max. 50 mA (use the MicroAutoBox II VSENSPIN for currents up to 250 mA)
Engineering
Product
Order Number
DS1553 ACMC Module
MABXII_ACMC
MicroAutoBox II AC Motor Control Solution Blockset
MABXII_ACMC_BS
RTI_FPGA_BS
XSG AC Motor Control Library including XSG Utils Library and XSG AC Motor
Control Interface Library
FPGA_XSG_ACMC
1)2)
1)
2)
Using the RTI FPGA Programming Blockset requires additional software, i.a. Xilinx products, please see the relevant product information.
2015
535
Order Information
Certifications
Standards
Like all dSPACE hardware products, MicroAutoBox meets
the requirements of the European Committee for Electro
technical Standardization (CENELEC) and is therefore
CE-compliant.
n EN 61326-1 Table 2: Immunity standard for industrial
environments
n CISPR11, EN 55011 Group 1, Class A: Emission standard
for industrial environments
Robustness Tests
To verify their reliability under realistic operating conditions,
all the standard MicroAutoBox variants were exposed to
extreme shock and vibration tests according to ISO 167503:2007. During the test, MicroAutoBox continuously
executed a program without any failures. It is also shockand vibration-tested up to 50G.
Vibration
Shock
Applied Standard
Description
ISO 16750-3:2007
/ 4.1.2.4 Test IV
DO160F Section 8
Test Curve B1
Broad band noise, 2h per axis, RMS

acceleration 27.8 m/s2
EN 60068-2-6
Test conditions: swept sine, 1 octave

per minute, 3-axis test
Operating: 5 ... 2000 Hz, up to 5 g,
2 sweeps per axis
Linear shock (1/2 sine pulse), 6-axis
Operating: 500 m/s, 6 ms, 10 pulses
per axis
ISO 16750-3:2007
/ 4.2.2
Broad band noise, 2h per axis, RMS

acceleration 31.3 m/s
Frequency range: 10 2000 Hz
Other Prototyping Systems
Use Case (Example)
Differences to Other Prototyping Systems
Bypass-Based Prototyping2)
In bypass-based prototyping, existing ECU software is optimized or partially revised. In this example, an automotive
ECU is connected to the MicroAutoBox via an ECU interface. The original ECU executes all the functions that will
remain unchanged, while the new algorithms are calculated in the MicroAutoBox. The necessary input data and
results are exchanged between the MicroAutoBox and the
original ECU. If your existing ECU already features the I/O
data required by the new control strategy, you only need
an appropriate ECU interface and the MicroAutoBox for
controller prototyping. If your algorithm requires additional
data, you can use the I/O interfaces of the MicroAutoBox2)
or RapidPro, to directly connect new sensors or actuators
to the vehicle bus.
Processor
AutoBox System
MicroAutoBox ECU
Scalable, floatingpoint, high

processing power
Floating-point, Fixed-point or
high processing floating-point,
power
target type,
low processing
power
Memory
Large, scalable
Large
Limited
I/O
Flexible, modular,
scalable
Fixed1)
Applicationspecific, fixed
Signal
conditioning
External, flexible,
e.g. via RapidPro
hardware
Built-in,
Built-in, fixed,
additional
applicationflexible signal
specific
conditioning
e.g. via RapidPro
hardware
Size
19.5 x 20 x 48 cm
(7.7 x 7.9 x 18.9 in)
Small
(pp. 523-526)
Small
Operation
Stand-alone
or PC
Stand-alone
or PC
Stand-alone
Programming
Graphical,
convenient,
automatic
implementation
Graphical,
Difficult,
convenient,
manual
automatic
implementation
Existing ECU
Additional I/O
1)
536
2015
2)
I/O
I/O extensions for the Simulink-Programmable FPGA available. Custom-specific I/O modifications possible via dSPACE
Engineering Services (p. 580).
The MicroAutoBox II 1401/1507 does not offer standard I/O or signal conditioning, but rather concentrates on the bus
and interface features (p. 525).
Introduction
MicroAutoBox II Software Support

It provides a blockset that implements the functionality
and I/O capabilities of MicroAutoBox II in your Simulink
controller models.
Application Fields
Real-Time Interface
The Real-Time Interface (RTI) library provides the link between
dSPACE MicroAutoBox II and the development software
MATLAB/Simulink/Stateflow from MathWorks.
Hardware
Software
MicroAutoBox II RTI Blockset

The latest MicroAutoBox II Blockset covers the additional I/O functionalities of the variants 1401/1513 and
1401/1512/1513, and also includes all the features from
the previous MicroAutoBox variants. Its clear structure makes
it very easy to find the individual I/O blocks' functions.
Wellstructured and ready for use with new and previous

MicroAutoBox variants: the MicroAutoBox II RTI Blockset.
All I/O is easy to access via a well

organized, intuitive structure.
2015
537
Engineering
RTI Blocks for Variants 1401/1513 and

1401/1512/1513
The RTI blockset includes the I/O functions available
with MicroAutoBox II. All I/O is intuitively organized and
structured so that you can easily find the I/O you require.
Engineering Services
I/O Specifications
dSPACE offers engineering services (p. 580) to adapt the I/O
and signal conditioning of MicroAutoBox to your specifications. For I/O, dSPACE offers predeveloped, verified designs
that can easily be integrated in MicroAutoBox. In general,
these modules do not have to be modified to suit your
application, which saves development time and reduces
engineering costs. The same I/O modules can of course be
integrated several times. dSPACE will also include the I/O
circuit designs you provide, such as company-specific CAN
controllers, ASIC, or plug-on devices, and will also design
new circuits according to your specifications. For the MicroAutoBox II 1401/1511/1512 and 1401/1512/1513, dSPACE
offers engineering services for hardware/software interface
integration via FPGA programming.
Custom-Specific Signal Conditioning

The signal conditioning portion of MicroAutoBox can also
be adapted to your requirements: for example, if filter
circuits or amplifiers have to be integrated. And if you want
to include your own signal conditioning concepts, dSPACE
will integrate your designs in the board layout. You can even
completely design the segment yourself.
MicroAutoBox with ARINC Interface for Aerospace
Applications (Example of Add-On I/O solutions)
An ARINC interface can be integrated (by dSPACE
Engineering Services) on the IP module slots offered by Micro
AutoBox II 1401/1505/1507, 1401/1511/1512, 1401/1507,
and 1401/1512/1513.
DS4340 FlexRay Interface Module

FlexRay Interface Module
The FlexRay Interface Module can be used with
MicroAutoBox II 1401/1505/1507, 1401/1511/1512,
1401/1507, and 1401/1512/1513. The module supports
FlexRay protocol specification 2.1 and is downward-compatible with previous standards. It provides a hardwareconfigurable, switchable termination circuit.
Parameter
Specification
General
n Supports the FlexRay protocol specification 2.1

n For use with MicroAutoBox II 1401/1505/1507, 1401/1507, 1401/1511/1512, and 1401/1512/1513
n Communication via Industry Package (IP) mechanism (for variants 1401/1505/1507 and 1401/1507) or via fast COM mode
(for variants 1401/1511/1512 and 1401/1512/1513)

n Molex connectors for direct access to FlexRay bus lines
n Switchable termination circuit (hardware-configurable)
n Feed-through possibility for FlexRay bus lines in passive-linear-bus topology
n Two FlexRay channels
Hardware details
n Freescale MFR43xx Communication Controller Family

n Dual PHY Interface with TJA1080
n For wake-up, hardware modification of the MicroAutoBox and the DS4340 is required.
Order Information
538
Product
Order Number
n DS4340 FlexRay Interface Module
n DS4340
2015
Introduction
NEW: DS4342 CAN FD Interface Module
Parameter
Specification
General
n
n
n
n
n
Hardware details
n
n
2 CAN FD channels
For use with MicroAutoBox II 1401/1505/1507, 1401/1507, 1401/1511/1512, and 1401/1512/1513
Automatic detection of Industry Package (IP) for MicroAutoBox 1507 or fast COM mode for MicroAutoBox 1512
Supported by RTI CAN MultiMessage Blockset
Suited for ISO 118985 network management
Suited for handling ISO 118982 CAN or CAN FD on every channel
NXP TJA1145T CAN Transceiver
Requires one additional slot
Software
Application Fields
Module for Interfacing CAN FD buses

The dSPACE DS4342 CAN FD Interface Module
(FD=Flexible Data Rate) can be used with MicroAutoBox II
1401/1505/1507, 1401/1511/1512, 1401/1507, and
1401/1512/1513. The DS4342 provides two independent
CAN channels, each of which can be used for CAN FD or
for CAN. Network management functions such as wake-up
and sleep are also included.
Order Information
Product
DS4342
Engineering
Hardware
DS4342 CAN FD Interface Module
2015
539
Order Number
MicroAutoBox Hardware / MicroAutoBox BreakOut Box
MicroAutoBox BreakOut Box1)

Universal desktop connection panel for MicroAutoBox
Highlights
n Fast and flexible signal connection
n Checking and reconnecting signals without changing
an existing cabling harness
n For use with all MicroAutoBox variants
Key Benefits
The MicroAutoBox Break-Out Box provides easy access
to all signals on the I/O connectors of the MicroAutoBox
(p. 522). You can observe signals and/or reconnect them
without changing an existing cable harness.
Terminal points
Connector to
MicroAutoBox
1)
540
2015
The Break-Out Box can be used with all MicroAutoBox

variants.
Knife disconnectors
Connector to
sensors and
actuators
Devices connected to the MicroAutoBox Break-Out Box can feed in high currents and high voltages which can be dangerous for
the user. Under all circumstances, you must observe all the safety precautions described in the documentation of the MicroAutoBox
Break-Out Box and of the devices connected.
Introduction
MicroAutoBox Hardware / MicroAutoBox Break-Out Box
Technical Details
Parameter
Specification
General
n I/O connectors: a) for connection to MicroAutoBox II and b) for connection to
an existing cable harness

Physical size
n 341 x 224 x 61 mm (13.4 x 8.8 x 2.4 in.)
Ambient temperature
n 0 ... +70 C (+32 ... +158 F)
Application Fields
n Knife disconnectors to interrupt the signal path
Order Information
Product
Order Number
MicroAutoBox Break-Out Box
n DS1541
Hardware
Software
Relevant Hardware
Order Number
One connection cable to MicroAutoBox is already included
with each purchased MicroAutoBox Break-Out Box.
Required
n MicroAutoBox II
n See p. 526
2015
541
Engineering
Hardware
Included
RapidPro Hardware / Introduction
RapidPro Hardware
Flexible hardware for rapid control prototyping
Highlights
n Scalable, modular, and configurable system architecture
n Compact and robust enclosure
n For in-vehicle, laboratory, and test bench use
n Comprehensive software support
n Application-specific configurations for common
application areas (p. 546)
n Advances for engine control: Any-crank/cam technologies and start/stop development support
542
Signal Conditioning and Power Stages

The wide variety of sensors and actuators used in the
automotive field, especially during the prototyping phase,
means that each sensor or actuator often requires its own
signal conditioning and power stage circuits. The flexibility
and intelligent assistance provided by RapidPro will help you
achieve challenging tasks for signal conditioning and power
stages with high efficiency.
For details, see Use Scenario A (p. 544)
Intelligent I/O Subsystems

The functions being developed and integrated into cars are
growing in complexity and volume. The acquisition and generation of I/O signals is also growing in complexity, for example,
in engine management applications. Moreover, sophisticated
algorithms usually need to be processed in a minimum of time.
All these demanding tasks need to be performed within a
standard prototyping environment with intelligent tools for
assistance. With RapidPro you can build an intelligent I/O
subsystem based on an MPC565 microcontroller.
For details, see Use Scenario B (p. 545)
Key Benefits
The RapidPro hardware works as an extension to dSPACE
prototyping systems. Its enclosure is designed so that you can
use the RapidPro units separately or connect several of them
to build a stack to use as one physical unit. Off-the-shelf
hardware- and software-configurable signal conditioning
(SC) and power stage (PS) modules (p. 559) can be installed
in the units to set up individual systems that optimally fit
the needs of a particular application. The modular
concept, using modules that are hardware- and softwareconfigurable, means that all components can be reused,
reconfigured, or extended with a minimum of effort, for
example in later projects or if requirements change.
Application Areas
The RapidPro hardware can be used for various applications.
To get you started working easily, dSPACE offers off-theshelf, predefined configurations for common application
areas such as:
n Engine control
n Body control
n Chassis control
n Transmission control
n Electric motor control
2015
RapidPro modules (p. 559) can be easily installed in

and removed from the units.
Software
Several RapidPro units can be connected for use as

one physical unit.
Application Fields
Introduction
Hardware
Engineering Services for RapidPro

To assist you with your function prototyping activities,
dSPACE offers specific engineering services (see also p. 580)
for RapidPro hardware:
2015
543
Engineering
n System design and configuration

n Mapping of actuators and sensors to signal conditioning
(SC) and power stage (PS) modules
n Specification and assembly of wiring harnesses
n Development of customer-specific SC and PS modules
n Template Simulink/Real-Time Interface (RTI) models
n Commissioning and system introduction onsite
Use Scenario A
Signal Conditioning and Power Stages for dSPACE
Prototyping Systems
The RapidPro SC Unit and the RapidPro Power Unit (equipped
with the relevant SC and PS modules, p. 559) can be used
as separate units in conjunction with prototyping systems
(MicroAutoBox, MicroLabBox, Modular Hardware including DS1005 and DS1007 plus I/O boards, Single-Board
Hardware). The RapidPro SC Unit supports your prototyping system wherever demanding signal conditioning
tasks such as signal protection, amplification, attenuation, filtering, and electrical isolation have to be performed. In turn, actuators like drives, valves, injectors,
lamps, and relays require high current and/or high voltage

output drivers. The RapidPro Power Unit provides your
prototyping system with the necessary power stages.
Automotive protection and extensive diagnostic capabilities are
especially important for power stages, for example, in safetycritical applications. Using dSPACEs ConfigurationDesk
software (p. 48) you can easily configure the unit and carry
out diagnostics. In this use scenario, the RapidPro hardware
can be used for developing control applications in fields such
as engine, transmission, chassis, body, and drives control.
dSPACE Prototyping Systems
Analog and
digital signals + SPI
USB
RapidPro
SC Unit
RapidPro
Power Unit
Hardware configuration
Sensors
Actuators
In this scenario, automotive sensors and actuators are adapted to a dSPACE

prototyping system with the help of the RapidPro SC Unit and the RapidPro
Power Unit.
544
2015
Introduction
Use Scenario B
Application Fields
An integrated Unit Connection Bus (UCB) allows you to

connect several RapidPro SC or Power Units directly to
the Control Unit without external wiring. Communication
between the RapidPro Control Unit and the prototyping
system is performed via a high-speed link. A RapidPro Control Unit Blockset (p. 549) for MicroAutoBox and modular
DS1005- or DS1007-based systems is available as an I/O
Real-Time Interface (RTI) for Simulink. dSPACEs ConfigurationDesk (p. 48) provides intuitive configuration of the unit
and diagnostics handling. In this use scenario, the RapidPro
hardware can be used for developing control applications
in fields such as engine, transmissions, chassis, body, and
drives control.
Software
Intelligent I/O Subsystems for dSPACE Prototyping

Systems
Applications such as engine management need to acquire complex I/O signals, for example, for crankshaft
and camshaft positions, and to generate complex signals for ignition and injection independently of the RCP
systems main processor and the models simulation step
size. Offloading specific, time-critical tasks like these to
a dedicated microcontroller decisively reduces the main
processors load. The RapidPro Control Unit variant with
MPC565 is used in this scenario as a slave microcontroller
to extend existing prototyping systems with additional
I/O functionality. The RapidPro Control Unit variant can
be used together with the MicroAutoBox or a modular
DS1005- or a DS1007-based system (with DS4121 ECU
Interface Board) or can additionally be combined with other
RapidPro units.
Hardware
LVDS link
RapidPro
Power Unit
USB
RapidPro
Control Unit
with MPC565
Sensors
In this scenario, two RapidPro units form a stack including signal conditioning
and power stages, so that complex I/O signals can be acquired and generated
independently of the main CPU of the prototyping system.
2015
545
Actuators
Engineering
Hardware configuration
Application-Specific Configurations
RapidPros predefined configurations cover a wide range of
typical signal conditioning and power stage tasks in various application areas. For example, the configurations for
engine control prototyping let you run engines with up to
6 cylinders and all modern sensors and actuators, and the
configuration for electric motor control serves as a flexible inverter stage during the prototyping phase of diverse
AC electric motors. Each configuration consists of selected
RapidPro power and signal conditioning modules (p. 529)
installed in the corresponding number of RapidPro units.
A RapidPro Control Unit is used whenever complex I/O signals need to be captured or generated, or a large number
of I/O signals are involved.
dSPACE also provides dedicated Simulink startup models for the configurations. These include all the available
I/O signals which are already configured in corresponding
tasks (e.g. angle-synchronous tasks for engine control). This
enables a fast startup and lets you concentrate fully on
your primary task of developing control algorithms for your
application. If your specific I/O requirements differ from the
setups, this is no problem at all. You can adapt one of the
ready-made configurations or build a new RapidPro system
from scratch. Either way, RapidPro will help you solve your
specific signal conditioning and power stage task.
For further information, please contact dSPACE.
Overview of RapidPro Configurations

Application
Engine control
Basic configuration
(based on Use Scenario B)
n 10 analog inputs
RapidPro SC Unit
RapidPro Power Unit
n 6 high-side outputs
n 2 lambda inputs
n 12 low-side outputs
n 6 crank/camshaft inputs
n 2 DC motor outputs
n 8 digital inputs
(opt. 2 direct injection outputs)
n 7 digital outputs
Engine control
Advanced configuration for
6 cylinders
n 2 lambda inputs
n 30 analog inputs
n 6 direct injection outputs
n 4 knock sensor inputs
n 6 crank/camshaft inputs
n 4 sensor supply outputs
n 8 digital inputs
n 2 DC motor outputs
(2 RapidPro Power Units needed)

Body control
Basic configuration
(based on Use Scenario A)
Body control
Advanced configuration
n 24 digital inputs
n 10 analog inputs
n 8 digital outputs
n 2 full-bridge outputs
n 32 digital inputs
n 28 digital inputs
(opt. 4 sensor supply outputs)
n 10 analog inputs
Chassis control
Basic configuration
(based on Use Scenario A)
n 14 analog inputs
n 16 digital inputs
n 8 digital outputs
Chassis control
Advanced configuration
Transmission control
n 20 analog sensors
n 2 full-brige outputs
n 24 digital inputs
n 16 digital inputs
Electric motor control
n 6 digital motor control inputs

n 2 digital brake chopper inputs
n 3 motor phase half-brigde outputs
n 1 brake chopper half-bridge output
n 3 analog outputs for motor current
measurement
546
2015
Introduction
Basic Configuration for Chassis Control
14 analog sensors
12 low-side drivers
Proportional valves
Valves for hydraulic control
4 x sensor supply
2 full bridge driver
Sensors
Parts
Devices
DC motor
Stepper motor
16 digital inputs
Level sensors
Various switches
Wheel speed sensors
Power Unit
SC Unit
Application Fields
Temperature
Pressure
Acceleration
Level sensors
8 digital outputs
PWM outputs
Relay driver
Flexible controls
Software
The basic configuration for chassis control is based on Use Scenario A (p.514) and offers all the sensors and actuators needed for chassis
control development.
Advanced Configuration for Engine Control
Speed and position of

camshaft and crankshaft
6 solenoid valve drivers

Solenoid injection valves
Hardware
6 inputs for camshaft

and crankshaft
2x 7A DC motor drivers
Throttle motor
EGR motor
2 lambda inputs
Up to 18 low-side drivers
BOSCH lambda sensors

Full coverage (LSU 4.2, 4.9, ADV)
Relays
Valves
Power Unit
Power Unit
SC Unit
Control Unit
4 knock sensor inputs
Engineering
Temperature
Pressure
Throttle position
Air mass flow
...
6 high-side drivers
Relays
Valves
16 digital inputs
Switches
Brake and clutch pedal
Neutral gear
Cruise control
4 x sensor supply
16 digital outputs
Sensors
Parts
Devices
PWM outputs
Relay drives
Flexible controls
The advanced configuration for engine control is based on Use Scenario B (p. 515) and is suitable for engine control development for up
to 6cylinders.
2015
547
Up to 30 analog sensors
Application Areas for RapidPro Modules

To cover todays variety of sensors and actuators, the
RapidPro hardware consists of ready-made and easy-to-insert
hardware- and software-configurable interface modules for
the highest degree of flexibility. Changes in the sensor and
actuator setup are no longer a risk for your development
Available Signal Conditioning

and Power Stage Modules
SC-SENS 4/1 Sensor supply
SC-AI 4/1 Analog inputs
SC-AI 10/1 Analog inputs
SC-DI 8/1 Digital inputs
SC-CCDI 6/1 Crankshaft/camshaft sensors
SC-DO 8/1 Digital outputs
SC-DO 8/2 Digital outputs push-pull
SC-EGOS 2/1 Bosch exhaust gas oxygen sensors
SC-UHEGO 2/1 DENSO exhaust gas oxygen sensors
SC-KNOCK 4/1 Knock sensors
SC-TC 8/1 Thermocouple sensors
PS-FBD 2/1 Full-bridge driver
PS-LSD 6/1 Low-side driver
PS-HSD 6/1 High-side driver
Application Fields
Engine Control
PS-HCFBD 1/1 High-current full-bridge driver

PS-HCHBD 2/1 High-current half-bridge driver
PS-HCFBD 1/2 High-current full-bridge driver (24 V)

PS-HCHBD 2/2 High-current half-bridge driver (24 V)
PS-DINJ 2/1 Direct injection driver
548
project, and home-made solutions are no longer necessary.

The RapidPro signal conditioning and power stage modules
(p. 529) can be easily combined to cover a wide range of
application fields.
Transmission
Chassis
Body Control
Drives
2015
Introduction
RTI RapidPro Control Unit Blockset
The RTI RapidPro

Control Unit Blockset
for MicroAutoBox and
DS1005 or DS1007.
Hardware
n Crankshaft signal measurement

n Engine speed and status
n Camshaft signal measurement
n Injection and ignition pulse generation
n Angle-synchronized task triggers
n Reading diagnostic data of modules
n Checking the status of a carrier board
n Any-crank/cam technologies with fully configurable,
map-based setup of crank/cam wheel geometry
n Support of crank sensors with rotation detection
for HEV and start/stop system development
n Fast, ECU-like engine synchronization
Application Fields
Functionalities can be combined with each other in realtime

applications, e.g., drives and engine functionalities. When
combining the MPC565-based RapidPro Control Unit and
MicroAutoBox or the modular DS1005 or DS1007-based
system, you gain additional functionalities for engine control
compared to using the MicroAutoBox on its own:
Software
In conjunction with the MPC565-based RapidPro Control Unit

(Use Scenario B, p. 545), a generic Real-Time Interface (RTI)
Blockset for Simulink is available for MicroAutoBox and modular DS1005- or DS1007-based systems. The blockset provides
extensive standard I/O functionalities (PWM, bit I/O, A/D)
including incremental encoder interface and stepper motor
control, as well as diagnostic functionalities and special functionalities for engine, chassis and drives control. Examples:
MicroAutoBox plus RapidPro Control Unit

Topic
Examples of extended functionality
Crankshaft control
n Crankshaft signals with up to 3600 pulses per wheel with or without gaps
Camshaft control
n Support of virtually every type of camshaft wheel

n Phase measurement of camshaft position
n Up to 4 camshaft wheels at a time
Engineering
n Generation of peak-and-hold pulse patterns (up to three phases)

n Up to 15 injection pulses for one injection cycle
Common
n Up to 12 channels for injection plus 12 channels for ignition simultaneously

n High engine angle resolution of 0.1
n 4 periodical and 16 absolute angle-based interrupts per engine cycle
2015
549
Injection control
RapidPro Hardware / Hardware Overview
Hardware Overview
Component
Description
Further
Information
Use
Scenario
A (p. 544)
Use
Scenario
B (p. 545)
RapidPro SC Unit
n Signal conditioning unit
p. 551
p. 553
p. 556
n Slots for up to 8 signal conditioning modules

n USB interface for hardware configuration via ConfigurationDesk
RapidPro Power Unit
n Power stage unit

n Slots for up to 6 power stage modules

with MPC565
n Intelligent I/O subunit for adding additional I/O functionality
SC Modules
n 4-channel sensor supply module
p. 560
n 4-channel differential analog input module
p. 560
n 10-channel analog input module
p. 560
n 8-channel digital input module
p. 560
n 8-channel digital output module
p. 560
n Crankshaft/camshaft sensor input module
p. 560
n 2-channel exhaust gas oxygen sensor module for Bosch LSU
p. 560
4.2, 4.9, and LSU ADV broadband lambda probes

n 4-channel knock sensor module
p. 560
n 8-channel thermocouple sensor input module
p. 560
n 2-channel exhaust gas oxygen sensor module for DENSO
p. 561
p. 561
n 2-channel full-bridge driver module
p. 561
n 6-channel low side driver module
p. 561
n 6-channel high side driver module
p. 562
n 1-channel, high-current, full-bridge driver module
p. 562
to the dSPACE prototyping system

n MPC565 microcontroller module
n Up to 6 signal conditioning modules
n Up to 2 communication modules
n LVDS interface for high-speed slave communication with
MicroAutoBox or DS1005 (via DS4121)
broadband lambda probes

n 8-channel digital out module with push-pull functionality
n Further modules are under development
PS modules
n 2-channel, high-current, half-bridge driver module
p. 562
n 2-channel direct-injection driver module1)
p. 562
n 1-channel, high-current, full-bridge driver module for
p. 563
p. 563
12 V and 24 V applications
n 2-channel, high-current, half-bridge driver module for
12 V and 24 V applications
n Further modules are under development
If the DS1664 2-channel direct injection driver module is used with RapidPro, electrically safe host PC interface cables (up to 300 V DC/ACRMS
and 600 V peak) are mandatory for all connected systems such as RapidPro, MicroAutoBox, and DS1005. You must perform all the safety
precautions described in the documentation.
1)
550
2015
RapidPro Hardware / RapidPro SC Unit
Introduction
RapidPro SC Unit
Flexible signal conditioning unit
Application Fields
Highlights
Hardware
Key Benefits
The RapidPro SC Unit is highly modular, flexible, intelligent, and especially designed for rapid control prototyping
in automotive applications. It comes with a robust, compact enclosure and an advanced mechanical concept. It
is not only suited to in-vehicle use, but also to the laboratory and the test bench. All inputs and outputs are automotive-protected. A RapidPro SC Unit can be equipped
with single- and/or multi-channel SC modules mounted
on the carrier board. The whole RapidPro SC Unit can be
switched on or off from a dSPACE prototyping system
via a remote control input, or all outputs deactivated via
an enable/disable input. A USB interface is available for
communicating with the host PC. dSPACEs ConfigurationDesk (p. 48) provides easy configuration of the unit and
diagnostics handling.
Engineering
Application Areas
The RapidPro SC Unit in conjunction with the standard SC
modules (p. 560) or customer-specific modules lets you
adapt almost any type of sensor (for example, temperature,
pressure, and crankshaft and camshaft sensors) to specific
prototyping systems.
Software
n Signal conditioning for dSPACE prototyping systems

n Easily adaptable to different sensor types via
configurable modules
n Slots for up to 8 signal conditioning modules
n Wide supply range
(6 V to 60 V), reverse and overvoltage-protected
Technical Details
Parameter
Specification
General
n 8 slots for configurable, analog or digital signal conditioning modules (SC modules, p. 560)
n Up to 64 channels per unit (for example, 40 analog plus 24 digital I/O or 40 digital plus 24 analog I/O)
n Unit Connection Bus for use with RapidPro Control Unit (p. 526)
n Onboard A/D converter to display I/O signals of the installed SC modules
n Internal temperature and voltage monitoring
n Remote control input to switch the unit on or off
n Enable/disable input to switch all outputs of a unit on or off
2015
551
n Support of modules with different form factors
RapidPro Hardware / RapidPro SC Unit
Technical Details
Parameter
Specification
Software support
Configuration
n Configuration of the SC modules from a host PC via ConfigurationDesk (p. 48)
Diagnostics
n Diagnostics handling via ConfigurationDesk
Electrical
characteristics
Power supply
n +6 +60 V DC
Mechanical
characteristics
Enclosure
n Load dump protection up to +100 V

n Reverse voltage protection up to -100 V
n Aluminum enclosure with cooling fins (no fan)
n Advanced mechanical concept with special coulter clips for easy installation and module locking
n Enclosure designed for flexible assembly (stack or single unit)
Environmental
characteristics
Physical size
(with cover and base plate)
n 200 x 225 x 35 mm (7.87 x 8.86 x 1. 38 in)
Physical size
(without cover and base plate)
n 172 x 225 x 25 mm (6.77 x 8.86 x 0.98 in)
Ambient temperature
n -40 +85 C (-40 +185 F)
Resistance to
vibration
EN 60068-2-6
n Mechanical test of resistance to vibration; test conditions: sinusoidal vibration, 3-axis test,
Resistance to
shock
EN 60068-2-27
n Mechanical test of shock resistance; test conditions: shock, 3-axis test, 11 ms at 15 g,
5 ... 2000 Hz, up to 5 g, 30 minutes per axis

5 ms at 100 g
Order Information
Product
Order Number
RapidPro SC Unit
n RAPIDPRO_1621 (please inquire)

Software
Required
Order Number
Hardware
Required
Optional
552
n CFD-C
Order Number
SC Modules
See p. 559
If the DS1664 2-channel direct injection driver module is used with

RapidPro (Power Unit), electrically safe host PC interface cables (up to
300 V DC/ACRMS and 600 V peak) are mandatory for all connected
systems such as RapidPro, MicroAutoBox, and DS1005. You must
perform all the safety precautions described in the documentation.
n USB_CAB12 (USB PC to LEMO cable with galvanic
RapidPro Power Unit (p. 553)
RapidPro Control Unit with MPC565 (p. 556)
Front connectors for RapidPro SC Unit
n RPS_F1F2
Rear connectors for RapidPro SC Unit
n RPS_R1R2
Crimping tool for RapidPro systems
n RAPIDPRO_CRIMP
RapidPro Break-Out Box for SC Unit (p. 564); 2 x connection cable

RapidPro SC Unit (F1/F2) and BOB (F1/F2), 0.5 m
n DS1687
USB PC to LEMO cable, 3 m
n USB_CAB6
isolation, 4.5 m)
n Further cables: please inquire.
2015
RapidPro Hardware / RapidPro Power Unit
Introduction
RapidPro Power Unit

Flexible power stage unit
Application Fields
Highlights
Hardware
Key Benefits
The RapidPro Power Unit is based on the same advanced
architecture as the RapidPro SC Unit (p. 551). The main
difference is that the power unit is designed to support
high current signals for driving actuators. The carrier board
offers space for up to six power stage modules (p. 559),
with or without current feedback. Each RapidPro Power
Unit can have up to 48 power driver channels. The whole
RapidPro Power Unit can be switched on or off from dSPACE
prototyping systems via a remote control input, or all outputs
can be deactivated via an enable/disable input. dSPACEs
ConfigurationDesk (p. 48) provides easy configuration of
the unit and extensive diagnostics handling.
2015
553
Engineering
Application Areas
The RapidPro Power Unit, in conjunction with the standard
PS modules (p. 559) or customer-specific modules, lets you
adapt many different types of actuators (for example, drives,
injectors, valves, relays, ohmic loads) to specific prototyping
systems.
Software
n Power stages for dSPACE prototyping systems

n Easily adaptable to different actuators via
configurable modules
n Slots for up to 6 power stage modules
n Wide supply range (6 V to 60 V),
reverse and overvoltage-protected

Technical Details
Parameter
Specification
General
n 6 slots for configurable power stage modules (PS modules) (p. 559)
n Up to 48 power stage channels per power unit
n Unit Connection Bus for use with RapidPro Control Unit (p. 556)
n USB interface for communication with host PC
n SPI interface for diagnostics with MicroAutoBox
n Enable/disable input to switch all outputs of a unit on or off
n Defined powered-off state during initialization and booting
Software support
Configuration
n Configuration of the PS modules from a host PC via ConfigurationDesk (p. 48)
Diagnostics

n Interactive diagnostics feedback to the model via RTI blockset (p. 549)
Electrical
characteristics
Power supply
Mechanical
characteristics
Enclosure
n +6 +60 V DC
Environmental
characteristics
Physical size
n 200 x 225 x 35 mm (7.87 x 8.86 x 1.38 in)
Physical size
n 172 x 225 x 25 mm (6.77 x 8.86 x 0.98 in)
Ambient temperature
n -40 +85 C (-40 +185 F)
Resistance to
vibration
EN 60068-2-6
Resistance to
shock
EN 60068-2-27

5 ms at 100 g
Order Information
554
Product
Order Number
RapidPro Power Unit
2015
Introduction

Order Number
Required
n CFD-C
Optional
n RTI
PS Modules
See p. 559
If the DS1664 2-channel direct injection driver module

is used with RapidPro, electrically safe host PC interface
cables (up to 300 V DC/ACRMS and 600 V peak) are
mandatory for all connected systems such as RapidPro,
MicroAutoBox, and DS1005. You must perform all the
safety precautions described in the documentation.
isolation, 4.5 m)

Front connectors for RapidPro Power Unit
n RPP_F1F2
Rear connectors for RapidPro Power Unit
n RPP_R1R2
n RAPIDPRO_CRIMP
RapidPro Break-Out Box for Power Unit (p. 564);

2 x connection cable RapidPro Power Unit (F1/F2)
and BOB (F1/F2), 0.5 m
n DS1688
n USB_CAB6
Engineering
Hardware
RapidPro SC Unit (p. 551)

RapidPro Control Unit, MPC565-based (p. 556)
2015
555
Optional
Order Number
Software
Hardware
Required
Application Fields
Software
RapidPro Hardware / RapidPro Control Unit with MPC565
RapidPro Control Unit with MPC565

Intelligent I/O subsystem for dSPACE prototyping systems
Highlights
n MPC565 microcontroller module
n Complex I/O signal generation and acquisition
n Up to 6 signal conditioning modules
n USB configuration interface
n LVDS slave communication interface
n NEW: Powerful FPGA
556
Application Areas
The MPC565-based RapidPro Control Unit can be used
as an intelligent I/O subunit to provide existing prototyping systems such as MicroAutoBox or AutoBox (including the DS1005 PPC Board or the DS1007 PPP Processor Board and the DS4121 ECU Interface Board)
with additional I/O functionality. For example, in
applications such as engine or vehicle dynamics control,

complex I/O tasks can be shifted from the prototyping
system to the RapidPro Control Unit. The RapidPro Control
Unit also provides space for signal conditioning modules,
so that different sensors can be adapted to a specific
prototyping system.
Key Benefits
The MPC565-based RapidPro Control Unit is based on
the same architecture as the RapidPro SC Unit (p. 551).
Additionally, the RapidPro Control Unit is equipped with
a powerful microcontroller module, including an MPC565
microcontroller, which is dedicated to handling complex I/O
tasks. The carrier board provides space for up to six signal
conditioning modules (SC modules, p. 559) and two communication (COM) modules. The signal conditioning modules
are the same modules as for the SC Unit. The USB configuration interface module is used for communication with the
host PC. The LVDS slave interface module enables highspeed communication with dSPACE prototyping systems
(MicroAutoBox or DS1005 or DS1007 via DS4121). The RapidPro
Control Unit can be used separately or in combination with

the other units to build an intelligent I/O subsystem tailored
to a particular application. An integrated Unit Connection
Bus allows you to connect several RapidPro SC or Power
Units directly to the Control Unit without external wiring.
Efficient configuration of a single control unit or a stack
and diagnostics handling are provided by ConfigurationDesk
(p. 48) via the USB configuration interface connected to
the host PC. Interactive diagnostics with feedback to the
model can be performed with the RTI RapidPro Control Unit
Blockset (p. 549). This blockset also provides extensive standard I/O functionalities such as PWM, bit I/O, A/D and special
functionalities for engine, chassis and drives control.
2015
Introduction
Technical Details
Parameter
Specification
General
n 6 slots for configurable, analog or digital signal conditioning modules (SC modules) (p. 559)
Application Fields
n 2 slots for communication interface modules (USB configuration interface module,
LVDS slave interface module)

n Unit Connection Bus to expand RapidPro Control Unit with several RapidPro Power
and/or SC Units
n Power management, sleep, and wake-up via prototyping system
n Support of table-based algorithm for wider coverage of crank/cam wheel architectures, e.g.,
asynchronous crank wheels for 3-cylinder engines

n Support of crank speed sensors with rotation detection for start/stop development
Microcontroller module
n MPC565, 56 MHz
n 4 MB external SRAM, 16 MB external flash
n Onboard FPGA for additional functionality
Software
n 48-channel time processing unit (TPU)

n 40-channel bit I/O
n 22-channel multi I/O timer (MIOS)
n 2 queued A/D converters with internal sample/hold
n 40 A/D converter channels (10-bit resolution, 4 s conversion time per channel)
Software support
Configuration
n Configuration of connected units and modules from a host PC via ConfigurationDesk (p. 48)
Diagnostics

n Interactive diagnostics feedback to the model via RTI RapidPro Control Unit Blockset (p. 549)
Electrical characteristics
I/O Real-Time Interface
n RTI RapidPro Control Unit Blockset (p. 549)
Power supply
n +6 ... +60 V DC
Hardware

n Voltage reverse protection up to -100 V
Mechanical characteristics
Enclosure

Physical size
n 200 x 225 x 35 mm (7.87 x 8.86 x 1.38 in.)
Ambient temperature
n -40 ... +85 C (-40 ... +185 F)
Resistance
to vibration
EN 600682-6
Resistance
to shock
EN 600682-27

5 ms at 100 g
2015
557
Environmental
characteristics
Engineering
n 172 x 225 x 25 mm (6.77 x 8.86 x 0.98 in.)

Physical size
Order Information
Products
Order Number

with MPC565
Stack:
with MPC565 plus RapidPro Power Unit
n RAPIDPRO_1601/1651
Stack:
with MPC565 plus RapidPro SC Unit plus RapidPro Power Unit
n RAPIDPRO_1601/1621/1651

Software
Required
Order Number
n CFD-C
n RTI
RTI RapidPro Control Unit Blockset (p. 519)
n RTIRAPIDPRO_BS
SC Modules
See p. 559
If the DS1664 2-channel direct injection driver module

is used with RapidPro, electrically safe host PC interface
cables (up to 300 V DC/ACRMS and 600 V peak) are
mandatory for all connected systems such as RapidPro,
MicroAutoBox, and DS1005. You must perform all the
safety precautions described in the documentation.
Hardware
Required
Optional
Order Number
isolation, 4.5 m)
RapidPro SC Unit (p. 551)
RapidPro Power Unit (p. 553)
Front connector1 for RapidPro Control Unit
n RPC_F1
Front connector2 for RapidPro Control Unit
n RPC_F2
n RAPIDPRO_CRIMP
RapidPro Break-Out Box for Control Unit (p. 564);

1 x connection cable between RapidPro Control Unit (F1)
and BOB (F1), 0.5 m;
1 x connection cable between RapidPro Control Unit (F2)
and BOB (F2); 0.5 m
n DS1689
n USB_CAB6
LVDS-Link cable LEMO-1S to ZIF crimp contacts, 5 m, 60 C n LVDS_CAB1

LVDS-Link cable LEMO-1S to LEMO-1S, 5 m, 60 C
n LVDS_CAB2
n LVDS_CAB15
n LVDS_CAB3
LVDS-Link cable LEMO-1S to ZIF crimp contacts, 1 m, 60 C n LVDS_CAB9
558
2015
RapidPro Hardware / RapidPro SC/PS Modules
Introduction
RapidPro SC/PS Modules

Mountable signal conditioning and power stage modules for RapidPro units
Application Fields
Highlights
Standard Modules and Custom Modules

Besides the standard modules described in the following
tables (p. 560 p. 563), dSPACE also offers you engineering services to develop individual signal conditioning and
power stage modules for your specific application scenario.
Hardware
Application Areas
The RapidPro signal conditioning (SC) and power stage
(PS) modules bring vital signal conditioning and power
stage functionality to the RapidPro units. The SC modules
can be installed in the RapidPro SC Unit and the RapidPro
Control Unit. The PS modules are installed in the RapidPro
Power Unit.
Software
n Hardware- and software-configurable standard modules

n Easy to mount on RapidPro units
n Safe locking of modules on RapidPro units
n Signal conditioning and power stage functionality

2015
Engineering
units are automotive-protected and can be locked safely

on the carrier boards with coulter clips. This makes them
suitable for in-vehicle applications. Modules are not limited
in size. If complex electronic circuits require more space or
pins than a single slot module offers, modules with other
form factors can be used.
559
Key Benefits
A wide choice of hardware- and software-configurable
modules is available that provide standard solutions in many
different applications. Installing and removing the modules
is easy, so the RapidPro units can be reused efficiently in
different projects. Customer-specific modules will also be
available on request. All the modules used with the RapidPro
Signal Conditioning (SC) Modules

Signal Conditioning
Module (SC Module)
Description
Order Number
SC-SENS 4/1
n 4-channel sensor supply module
n DS1626
n Requires 1 slot in a RapidPro unit

n Software-adjustable voltage range: 2 V ... 20 V, adjustable in steps of 5.5 mV
n Output power: 1.2 W per channel
n Fully isolated outputs
n Thermal overcurrent protection
n Accuracy 1%
SC-AI 4/1
n 4-channel differential analog input module
n DS1631

n Software-adjustable input range: 100 mV ... 50 V
n Output range: 0 ... 5 V, 5 V, 0 ...10 V, 10 V, software-adjustable globally for all four channels
n Four software-selectable 1st order low-pass filters (per channel). Cutoff frequencies: 10 Hz, 50 Hz, 100 Hz, 1 kHz
n Input circuit: up to 4 hardware-configurable devices per channel, for example, pull-up, pull-down
SC-AI 10/1
n 10-channel analog input module
n DS1633
n Requires 2 slots in a RapidPro unit

n Double size module (requires two slots)
n Onboard sensor supply: 5 V, 1 W
n External supply input
n Input circuit: up to 9 hardware configurable devices per channel, for example, pull-up, pull-down, 1st order
low pass filter

SC-DI 8/1
n 8-channel digital input module
n DS1642

n Software-adjustable comparator threshold and hysteresis voltage, software-adjustable in a range of 39.5 V
n Input voltage range: up to 55 V continuous
n Input circuit: up to 3 hardware-configurable devices per channel, for example, pull-up, pull-down
SC-DO 8/1
n 8-channel digital output module
n DS1646

n Open collector output
n Output current: each channel 1 A, total permissible current for all channels: 1 A
n Output voltage: 40 V
n Fully isolated outputs of one module (one common ground)
n Overcurrent protection
SC-CCDI 6/1
n Crankshaft/camshaft sensor input module
n DS1637

n Connection of rotational speed sensors with open load voltage up to 200 V (60 V DC)
n 4 inputs for cam sensors with common ground
SC-EGOS 2/1
n 2-channel, exhaust gas oxygen sensor module for connecting Bosch LSU4.2, LSU4.9 or LSU ADV broadband n DS1634
lambda probes
n Based on Bosch ASIC CJ125
n Lambda measurement range: 0.65 ... and 0.75 ... (software-configurable)
n Pump reference current: 0 ... 150 A (software-configurable in 10 A steps)
SC-KNOCK 4/1
n 4-channel knock sensor module
n DS1635

n Based on Bosch ASIC CC196 (with on-board DSP)
SC-TC 8/1
n 8-channel thermocouple sensor input module
n DS1638

n Suitable for type J and K thermocouples
n One 24-bit A/D converter per channel, sampling rate for each converter (software-configurable) 0.1 Hz ... 50 Hz
n Splitter cable (available as J or K variant) plus memory identifying the connected thermocable and thermocouples
n High-precision cold junction compensation
560
2015
Introduction
Signal Conditioning
Module (SC Module)
Description
Order Number
SC-UHEGO 2/1
n 2-channel exhaust gas oxygen sensor module
n DS1639
n For integrating DENSO broadband lambda probes (PLUS2.1, PLUS3.x) into a function prototyping set-up
Application Fields

n Based on DENSO ASIC technology
n Air-fuel ratio measurement range: software-configurable, wide range: AFR 10 , stoichiometric range:
AFR 12 25
SC-DO 8/2
n 8-channel digital out module with push-pull functionality
n DS1647

n Configurable output stage: push-pull, low-side driver, high-side driver
n Enables fast control of digital circuitry (e.g. dashboard applications, external power stages for electrical drives)
n Tri-state capability during shutdown and idle state of the real-time application
n Low-side driver mode for driving loads (e.g. relays)
n Parallel channel operation for increased current capability
Software
n Routing compatible with SC-DO 8/1 (DS1646)
Power Stage (PS) Modules

Power Stage Module
(PS Module)
Description
Order Number
PS-FBD 2/1
n 2-channel full-bridge driver module
n DS1661

n Each driver 5 A continuous, 7 A peak (depends on the Power Unit the module is mounted in)
Hardware
n Maximum supply voltage: 40 V continuous, 45 V peak (0.5 sec)

n Usable as: full-bridge, half-bridge, low or high side driver
n Software adjustable current limitation and switch-off time
n High-side rise time: 1.8 s typ., 3.5 s max.,
2015
Engineering
n DS1662
561
PS-LSD 6/1
high-side fall time: 0.2 s typ., 0.8 s max.,

low-side rise time: 6.5 s typ., 11 s max.,
low-side fall-time: 4.3 s typ., 6.5 s max.
n Detailed load failure diagnosis
n Current measurement with software adjustable filters (2nd order) on both channels
n Overload protection, overtemperature protection, short-circuit protection to ground, UBAT and across the load
n Integrated on carrier board: load dump protection up to +100 V, reverse voltage protection up to -100 V
n 6-channel low-side driver module
n 4 output channels with up to 5 A (hardware-configurable)
n 2 output channels with up to 1 A
n Max. supply voltage: 37 V continuous
n Clamping voltage: 45 V or 70 V (depending on hardware configuration)
n Switching time: <10 s
n Current measurement with hardware-adjustable low-pass filter (1st order) on channel 1 and 2
n Overload protection, overtemperature protection, short-circuit protection to ground, active output clamping
n Integrated on carrier board: load dump protection up to +100 V (only valid for internal voltage supply of
the module), reverse voltage protection up to -100 V
Power Stage Module

(PS Module)
Description
Order Number
PS-HSD 6/1
n 6-channel high-side driver module
n DS1663

n 4 output channels with up to 5 A, clamping voltage 48 V
n 2 output channels with up to 1 A, clamping voltage 63 V
n Max. supply voltage: 36 V continuous, 40 V peak
n Switching time: <30 s
n Load failure diagnosis
n Current measurement with hardware-adjustable low-pass filter (1st order) on channel 1 and 2
n Overload protection, overtemperature protection, short-circuit protection to ground, VBAT and across the load,
active output clamping
n Integrated on carrier board: load dump protection up to +100 V (only valid for internal voltage supply of
the module), reverse voltage protection up to -100 V

PS-HCFBD 1/1
n 1-channel high-current full bridge driver module
n DS1667

n Up to 60 A DC peak current (1 s), 42 A rms continuous (Tambient= 25 C, filter frequency 1 kHz, corresponding
duty cycle)
n Up to 60 A DC peak current (1 s), 29 A rms continuous (depends on ambient temperature)

n Max. supply voltage: <20 V continuous
n Current measurement with hardware-adjustable low-pass filter (1st order)
n Internal free-wheeling diodes
n Protection against: short circuit, overtemperature, and overvoltage
n Load failure diagnostics
PS-HCHBD 2/1
n 2-channel, high-current, half-bridge driver module
n DS1668

n Each channel up to 30 A peak current (1 s), 25 A rms continuous (depends on ambient temperature)
n Parallel mode possible (30 A DC peak per channel, 19 A rms continuous per channel)
n Usable as half-bridge or low-side or high-side driver output
n Max. supply voltage: <20 V continuous
n Current measurement with hardware-adjustable low-pass filter (1st order) for each channel
n Internal free-wheeling diodes
n Protection against short circuit, overtemperature, and overvoltage
n Load failure diagnostics
PS-DINJ 2/11)
n 2-channel direct-injection driver module
n DS1664

n Single or double injector operation mode (two injectors of the same bank cannot be driven at the same time)
n Booster voltage U max: 100 V1)
n I max: 30 A peak, 15 A continuous
n Control of start injection
n Software-adjustable booster voltage
n Software-adjustable injection duration (peak and hold times)
n Software-adjustable peak current (upper and lower values), subpulse A and B available for Use Scenario B
n Software-adjustable hold current (upper and lower values)
If the DS1664 2-channel direct injection driver module is used with RapidPro, electrically safe host PC interface cables (up to 300 V DC/ACRMS
and 600 V peak) are mandatory for all connected systems such as RapidPro, MicroAutoBox, and DS1005. You must perform all the safety
precautions described in the documentation.
1)
562
2015
Introduction
Power Stage Module

(PS Module)
Description
Order Number
PS-HCFBD 1/2
n 1-channel high-current full-bridge driver module for 12 V and 24 V applications
n DS1767
Application Fields
n Suitable for Use Scenarios A and B (p. 514, p. 515)

n Support of DC motors and stepper motors
n Up to 60 A DC peak current (1 s), 42 A rms continuous (depends on ambient temperature)
n Max. supply voltage: 30 V
n Current measurement with software-configurable low-pass filter (1st order/2nd order)
PS-HCHBD 2/2
n 2-channel, high-current, half-bridge driver module for 12 V and 24 V applications
n DS1768

n Suitable for Use Scenarios A and B (p. 514, p. 515)
n Each channel up to 60A peak current (1 s), 42 A rms continuous per channel (depends on ambient
temperature, electric drive mode)

n Electrical drive mode: Control of three-phase electrical motors (BLDC motors and synchronous motors).
Software
Requires two PS-HCHBD 2/2 modules in the same Power Unit and includes a brake chopper for conversion
of breaking energy into heat
n General purpose mode for controlling high current actuators (e.g. valves, resistive loads) (up to 30 A peak
current. 19 A rms current)
n Each channel up to 30 A peak current per channel (1 s), 19 A rms continuous per channel (depends on
ambient temperature)
n Output stages in the general purpose mode configurable as half-bridge, low-side or high-side driver
n Max. supply voltage: 30 V
n Current measurement with software-configurable low-pass filter (1st order/2nd order)
n Optional: RP-HC-CAB1 cable for connecting external loads such as three-phase electric motors
2015
563
Engineering
Hardware
For more detailed information, please contact dSPACE. Further signal conditioning modules are under development. Please let us know about
your requirements for future modules.
RapidPro Hardware / RapidPro BreakOut Boxes
RapidPro BreakOut Boxes1)

Desktop connection panels for RapidPro systems
Highlights
n Fast and flexible sensor and actuator connection
n Checking and reconnecting signals without changing
an existing cable harness
Key Benefits
With the RapidPro Break-Out Boxes, you can connect
sensors and actuators to RapidPro units flexibly and see
at a glance which signals are connected, including their
statuses. You can also reconnect signals without changing
an existing cable harness. This makes the RapidPro BreakOut Boxes an important accessory in setting up signal
conditioning, power stages and intelligent I/O subsystems

with RapidPro units in combination with dSPACE prototyping
systems. Each RapidPro Break-Out Box provides a number
of multicolor LEDs, one LED per signal. The LEDs indicate
different voltage ranges and the signals by different colors.
Labeled terminals
Multicolor LEDs
Rotary switch:
voltage level adaption
Female I/O
connectors
to RapidPro
units
Male I/O
connectors
to sensors/
actuators
Terminal points
1)
564
Knife disconnectors
Slide switch to
turn LEDs on/off
Devices connected to RapidPro Break-Out Boxes can feed in high currents and high voltages which can be dangerous for the user. Under all
circumstances, you must observe all the safety precautions described in the documentation of the RapidPro Break-Out Boxes and of the devices
connected!
2015
Introduction
RapidPro Hardware / RapidPro Break-Out Boxes
Technical Details
Parameter
Specification
General
n Three variants for different RapidPro units:
DS1687 for SC Unit, DS1688 for Power Unit, DS1689 for Control Unit
n I/O connectors a) for connection to RapidPro units and b) for connection to an existing
cable harness
n Each Break-Out Box provides the same number of terminals as the connected unit: up to
Application Fields
6 terminal points for each signal. There are knife disconnectors to interrupt the signal path.
n LEDs to indicate signal status (one multicolor LED for each signal path). Indication adjustable
to different voltages. Slide switch to turn all LEDs on/off.

Electrical characteristics
Power supply
n +6 +60 V DC
n MINI Fuse (blade type automotive fuse):
Physical size
Environmental
characteristics
Ambient temperature
n 0 +70 C (+32 +158 F)
Software
Mechanical characteristics
1x 10 A (Break-Out Box for SC Unit),

2x 30 A (Break-Out Box for Power Unit),
1x 5 A or 1x 10 A (Break-Out Box for Control Unit)
n 356 x 224 x 50 mm (14 x 8.8 x 1.95 in)
Order Information
Products
Order Number
RapidPro Break-Out Box for SC Unit; 2 x connection cable RapidPro SC Unit (F1/F2) and BOB
(F1/F2), 0.5 m
RapidPro Break-Out Box for Power Unit, 2 x connection cable RapidPro Power Unit (F1/F2)
and BOB (F1/F2), 0.5 m
RapidPro Break-Out Box for Control Unit, 1 x connection cable between RapidPro Control Unit
(F1) and BOB (F1), 0.5 m; 1 x connection cable between RapidPro Control Unit (F2) and BOB
(F2), 0.5 m
n DS1687
Hardware
n DS1688
n DS1689
Hardware
Required
n CFD-C
Engineering
Required
Order Number
Order Number
RapidPro unit with corresponding SC/PS modules
See p. 529
2015
565
Software
ECU Interface Hardware / USB to CAN Converter DCICAN1
USB to CAN Converter DCICAN1

Robust and compact USBtoCAN gateway
Highlights
Robust design for in-vehicle use
n Plug & Play via USB
n Integrated optoisolation and high-speed transceiver
n API for easy integration in custom applications
n
Application Areas
n Measurement of ECU internal variables, ECU
calibration, diagnostics and ECU flash programming
via CCP1), XCP2) on CAN, KWP20003) or UDS4) on CAN,
for example.
n Measurement of physical quantities like temperature,
pressure and voltages via CAN-based I/O modules
n Monitoring the data stream on the CAN bus in
n Transmitting messages via the CAN bus
Key Benefits
The Controller Area Network (CAN) is an established standard in the automotive industry to exchange data between
electronic control units. The DCI-CAN1 provides a robust,
compact interface to the CAN bus via a Plug & Play USB
connection, and features integrated optoisolation and a
high-speed transceiver. The DCI-CAN1 is powered directly
via USB, so no additional components are necessary to connect to the CAN bus.
Host PC
ECU with CCP
or XCP on CAN
Connection scenario using a DCICAN1.
1)
566
2)
3)
2015
4)
CAN Calibration Protocol

Universal Measurement and Calibration Protocol
Keyword Protocol 2000
Unified Diagnostic Services
Introduction
ECU Interface Hardware / USB to CAN Converter DCI-CAN1
Technical Details
Parameter
Specification
General
n
NXP CAN controller SJA1000 (clock rate: 16 MHz)
n
High-speed CAN transceiver 82C251
n
Baud rates up to 1 Mbit/s
n
Supports CAN specification 2.0A and 2.0B (11- and 29-bit identifiers)
n
Time-stamping all measured or monitored data is sent to ControlDesk Next Generation
Application Fields
with time stamps (resolution 50s)

n
Complies with European directives 73/23/ECC (Low Voltage Directive) and 89/336/ECC
(Electromagnetic Compatibility Directive)

Host interface
n
USB
Software configuration
n
Configuration of the DCI-CAN1 from host PC with ControlDesk Next Generation or with dSPACE CAN API
Physical
characteristics
Enclosure
n
Robust aluminum box
Connectors
n
9-pin, male Sub-D connector for connection to CAN (according to CiA-DS 102-1)
n
A-type USB connector with 1.5 m (5 ft) cable for connection to the host PC
Status LED
n
Off: CAN inactive/not connected
n
On: CAN active
n
16 x 55 x 84 mm (0.63 x 2.16 x 3.30 in)
Approx. weight
n
150 g (0.33 lb.)
Temperature range
n
-40 ... 85 C (-40 ... 185 F) ambient temperature
Software
n
Flashing: bus traffic
Physical size
n
-65 ... 125 C (-85 ... 257 F) storage temperature
n
IP 54
Power supply
n
Power consumption max. 600 mW supplied by USB
n
Galvanic isolation up to 50 V (connector maximum) via optoisolation
Power consumption
n
< 600 mW supplied by USB
Galvanic isolation
n
Up to 50 V (connector maximum) via optoisolation
Hardware
Electrical
characteristics
IP protection class
Order Information
Product
Order Number
USB to CAN Converter DCI-CAN1
n
DCI_CAN1
Application Areas
Key Features
The API allows custom applications to be built in Python (API

available as a Python module) or Microsoft Visual C++ 6.0
(API available as a functional WIN32 DLL). For supported
operating systems (API, driver) see
n
Supports multiapplication: several applications can connect to the same CAN channel
Engineering
dSPACE CAN API and CAN Driver
n
Supports multiclient: the same application can connect to one or more CAN channels
n
2 virtual CAN channels for testing your application without using the hardware
n
Up to 16 CAN channels accessible
2015
567
n
Provided along with the DCI-CAN1 and dSPACE Release
ECU Interface Hardware / USB to KLine Interface DCIKLine1
USB to KLine Interface DCIKLine1

Robust and compact USB to KLine interface
Highlights
Robust design for in-vehicle use
n Plug & Play via USB
n Integrated optoisolation
n Supports 12 V and 24 V power supply networks
in the vehicle
n
Application Areas
The DCI-KLine1 is used with ControlDesk Next Generation
to access electronic control units via KWP2000 on K-Line
(ISO14230). ECUs providing single-wire K-Line communication and a fast initialization wake-up pattern (WuP) are
supported. ECU diagnostics and ECU flash programming
can both be done via the DCI-KLine1.
USB
Key Benefits
The DCI-KLine1 comes in the same reliable, robust and
compact casing as the DCI-CAN1. Plug & play capabilities
via USB provide a quick connection to the host PC. The
DCI-KLine1 can be used for ECU diagnostics in passenger
cars and commercial vehicles with 12 V and 24 V power
supply networks. The integrated optoisolation of the DCIKLine1 avoids ground loops.
K-Line
DCI-KLine1
ECU with
KWP2000 on K-Line
Connection scenario using the DCIKLine1 for ECU diagnostics and ECU flash programming.
568
2015
Introduction
ECU Interface Hardware / USB to K-Line Interface DCI-KLine1
Technical Details
Parameter
Specification
General
n
Support of fast initialization on KLine via hardwaregenerated wakeup pattern (WuP)
n
Baud rate range: 183 Bd 115,2 kBd1) for communication
n
Support of standard PC baud rates according to ISO 14230 (9.6 kBd, 19.2kBd, 38.4kBd, 57.6kBd,
115.2kBd) and other specific baud rates

n
FT232BM USB-to-serial converter
Application Fields
n
Complies with European directives 73/23/ECC (Low-Voltage Directive) and 89/336/ECC (Electro
magnetic Compability Directive)

Host Interface
n
USB
Software configuration
n
Configuration of the DCI-KLine1 from host PC with ControlDesk Next Generation
Physical
characteristics
Enclosure
n
Robust aluminum box
Connectors
n
4 mm female connectors for connection to the ECU and power supply: red (VBAT), black (GND),
green (K-Line)
n
A-type USB connector with 1.5 m (5 ft) cable for connection to the host PC
n
Off: USB not powered/not connected
Status LED
n
On (yellow): USB not initialized, VBAT on
n
On (red): USB initialized, VBAT off
n
On (green): USB initialized, VBAT on
n
16 x 55 x 84mm (0.63x 2.16x 3.30in)
Approx. weight
n
150g (0.33lb.)
Temperature range
n
-40+85C (-40+185F) ambient temperature
Software
n
Flashing (green): K-Line traffic
Physical size
n
-65+125C (-85+257F) storage temperature
Electrical
characteristics
Power supply
n
Voltage range: 4 40V
Power consumption
n
<100mA (from USB)
n
Overvoltage protection: 60V, including all possible wrong wirings of K-Line, GND, and VBAT
n
40mA max. (from VBAT)
n
Approx. 2mA (from VBAT, in standby mode)
Hardware
n
Up to 60VDC (connector maximum) via optoisolation
Galvanic isolation
The lower limit is determined by the USB-to-serial converter. The upper limit is determined by the driver circuit and capacitance of K-Line.
1)
Order Number
DCI-KLine1
n DCI_KLINE1
Relevant Software
Software
Required
Order Number
n
n
See p. 108
2015
569
Product
Engineering
Order Information
ECU Interface Hardware / Generic Serial Interfaces
Generic Serial Interfaces

Function bypassing, measurement, ECU calibration and flash programming
Highlights
n Very small communication latencies with bypassing
n Various on-chip debug interfaces and connectors
supported off-the-shelf
n High measurement data throughput via USB or XCP
on Ethernet
n Measurement and bypassing without ECU code
changes
Application Areas
The current trend for modern automotive microcontrollers
is towards higher levels of system integration, faster clock
rates, increased on-chip RAM and flash memory, and more
comprehensive I/O functionality. In this context, on-chip
debug interfaces are becoming much more important for
ECU software development.
dSPACE provides the generic serial interfaces DCI-GSI1 and
DCI-GSI2, which can be used for function bypassing, measurement, ECU calibration and flash programming. The
broad range of available connector adapters lets you adapt
the DCI-GSIs to individual electronic control units.
Differences Between the DCI-GSIs

Although both the DCI-GSI1 and the DCI-GSI2 are basically tailored for similar use cases, they differ in several
details: For example, the DCI-GSI2 provides an open and
standardized XCP on Ethernet interface for third-party tools
to connect to. In addition, the DCI-GSI2 features bypassing
without requiring any ECU source or HEX code changes,
and enables very high measurement data throughputs and
extremely fast measurement rasters via GBit Ethernet.
For a detailed comparison of the DCI-GSI1 and DCI-GSI2,
see the table on p.571.
ECU
ControlDesk
Next Generation
DCI-GSI2
Ethernet
XCP on Ethernet
Vbat
MicroAutoBox II with
integrated Ethernet switch
Example wiring scenario with DCIGSI2 for ECU calibration and measurement in parallel to bypass communication.
570
2015
Introduction
Application Fields
dSPACE AutoBox
for bypassing
Ethernet
LVDS
(Low-Voltage
Differential Signaling)
ECU
JTAG/Nexus,
AUD or
NBD, ...
DCI-GSI1
Installation inside or outside
the ECU enclosure
Example wiring scenario with DCIGSI1 for ECU

calibration and measurement (blue connection)
plus function bypassing (green connections)
in parallel.
Software
USB
Comparison of DCI-GSI2 and DCI-GSI1

Parameter
DCI-GSI2
DCI-GSI1
Harness complexity
n
Two connections in total (Ethernet, power supply)
n
Three connections in total (LVDS, USB, power
Size of enclosure
n
102.5 x 71 x 26.5 mm (4.04 x 2.80 x 1.04 inch)
n
102.5 x 71 x 21.4 mm (4.04 x 2.80 x 0.84 inch)
Temperature range
n
40 +85 C (40 +185 F) operating
n
40 +85 C (40 +185 F) operating
supply)
temperature)
XCP on Ethernet (UDP/IP, TCP/IP), 1 GBit/s

Host interface for measurement and calibration n
n
USB 2.0, proprietary protocol
Interface to prototyping system for function

bypassing
n
XCP on Ethernet (UDP/IP, TCP/IP), 1 GBit/s
n
LVDS, proprietary protocol
Automatic detection of target microcontroller
Hardware
temperature (extended temperature range on request)
n
No
n
Yes
Maximum measurement data throughput
n
> 50 Mbit/s1)
n
< 6 Mbit/s (via USB interface)
CPU load on ECU for rastersynchronous

measurement
n
Very low (no changes to ECU code required)
n
Low (ECU service typically required)
Fastest measurement raster
n
100 kHz (measurement rasters 10 s possible)
n
10 kHz (for measurement rasters 100 s)
Support of address remapping and memory

management units (MMUs)
n
Unlimited
n
Limited
Data tracing of ECU memory
n
Unlimited (trace mirror size up to 400 kB)
n
Limited
Bypassing without hooks in ECU software
n
Yes (via data trace interface)
n
No
ECU calibration including working/reference

page concept
n
Yes
n
Yes
Flash programming of braindead ECU
n
Yes
n
Yes
Depending on the debug interface type.
2015
571
1)
Engineering
n
Yes
Parallel calibration, measurement and bypassing n

Yes
Technical Details of DCI-GSI2

Parameter
Specification
Host Interface
n
XCP on Ethernet (100 Mbit/s, 1 GBit/s)
ECU Interface
n
JTAG/OCDS and DAP/DAP2: Infineons TriCore families
n
DAP: Infineon XC2000
n
JTAG/Nexus: Freescales MPC55xx, MPC56xx and MPC57xx families
n
JTAG/Nexus: ST Microelectronics SPC56xx and SPC57xx families
n
JTAG/Nexus: Renesas V850E2 and RH850 family
For further interfaces, please contact dSPACE.

n
Connector to on-chip debug bus:
Connectors
n Various connector adapters are available from dSPACE. Some adapters also have a tool connector
for connecting an additional tool such as a debugger.

n
Ethernet connector:
n 8pin connector for connection to the host PC and/or the bypass system
n
Power connectors (only one power connector can be used at the same time):
n 2pin LEMO power connector on the DCI-GSI2 enclosure for connection to an external power supply
n Internal power connector in the DCI-GSI2 for connection to the vehicle power supply in the ECU
via the internal power supply cable

Physical
characteristics
Enclosure
n
Aluminum box (to be ordered separately)
Size
n
DCI-GSI2 with aluminium box: 102.5 x 71 x 26.5 mm (4.04 x 2.8 x 1.04 in)
n
DCI-GSI2 without aluminium box: 70.05 x 62.4 x 10.5 mm (2.76 x 2.46 x 0.41 in)
Weight
(without connector adapter)
n
DCI-GSI2 with aluminium box: approx. 220 g (0.49 lb.)
Temperature range
n
-40 ... +85 C (-40 ... +185 F) operating temperature
n
DCI-GSI2 without aluminium box: approx. 28 g (0.06 lb.)
n
-40 ... +105 C (-40 ... +221 F) operating temperature on request
n
-65 ... +125 C (-85 ... +257 F) storage temperature
Electrical
characteristics
n
4.3 ... 30 V (38 V transient), extended range with power supply cable PWR_CAB9
Power supply
Protection
Power consumption
n
Protected against reverse battery up to -32 V
1)
n
4 W typ. at room temperature, 12 V, and 1 GBit/s Ethernet. Using 100 Mbit/s Ethernet instead of
1 GBit/s saves about 0.7 W

n
30 mW typ. in standby mode
If JTAG/Nexus with MPC5xxx microcontroller is used.
1)
572
2015
Introduction
Product
Order Number
Generic Serial Interface DCI-GSI2
n
DCI_GSI2
Application Fields
Order Information
Relevant Hardware
Hardware
Order Number
n
Enclosure for in-vehicle use
n
DCI_GSI2_ENC1
n
Enclosure for laboratory use
n
DCI_GSI2_ENC2
n
Microcontroller-specific connector adapters
n
Please inquire
n
ETH_CAB1
the host PC)
n
Ethernet Connection Cable (for example, to connect a DCI-GSI2 to a MicroAutoBox II) n
ETH_CAB3
n
Ethernet Connection Cable (for example, to connect the MicroAutoBox II to the
n
ETH_CAB4
host PC); length 10 m
n
PWR_CAB9
n
Power Supply Cable for DCI-GSI1/GSI2 with galvanic Isolation
Engineering
Hardware
Software
n
Ethernet Connection Cable (for example, to connect the DCI-GSI2 to
2015
573
Optional
Technical Details of DCI-GSI1

Parameter
Specification
General
n
64 MB RAM for buffering measurement data
n
USB host interface for measurement and calibration
n
Low-voltage differential signaling (LVDS) bypass interface for connection to dSPACE prototyping hardware
n
Interface for connecting an additional tool to the ECU via its on-chip debug port
n
Offline check and display of allocation status of overlay RAM in ControlDesk Next Generation
n
Quick-start measurement
n
ECU flash programming via dSPACE ECU Flash Programming Tool (p. 235)
n
Support of memory address relocation, for example, in connections with microcontrollers featuring
memory management units (MMUs)

ECU interface
n
READI/Nexus: Freescales MPC56x family1)
n
AUD/AUD2: Renesas SH2 and SH2A family
n
NBD: Renesas V85x, Renesas M32R family and Toshiba TMP1984FDF
n
JTAG/OCDS: Infineons TriCore family
n
JTAG/H-UDI: Renesas SH2A and SH4A family
n
JTAG/SDI: Renesas M32R family
n
JTAG/Nexus: Freescales MPC55xx and MPC56xx family
Target/tool connector
n
SAMTEC FOLC-125-01-S-Q-LC to interface individual connector adapters
n
Various connector adapters available from dSPACE. Certain adapters feature an extra connector
allowing third-party tools such as a debugger to be connected in parallel.

Physical
characteristics
Enclosure
n
Aluminum box (to be ordered separately)
n
Protection classes IP 54 and IP66 on request
Size
n
DCI-GSI1 with aluminum box: 102.5 x 71 x 21.4 mm (4.04 x 2.80 x 0.84 in)
n
DCI-GSI1 without aluminum box: 62.4 x 56 x 10.5 mm ( 2.46 x 2.21 x 0.41 in)
Weight
n
DCI-GSI1 with aluminum box: approx. 214 g (0.47 lb.)
n
DCI-GSI1 without aluminum box: approx. 29 g (0.06 lb.)
Temperature range
n
-40 ... +85 C (-40 ... +185 F) operating temperature
n
-65 ... +125 C (-85 ... +257 F) storage temperature
Electrical
characteristics
Power supply
n
6 V ... 48 V
Protection
n
Protected against overvoltage
n
Load dump protection up to 60 V
n
Protected against reverse battery up to -60 V
Power consumption2)
n
2.3 W max., at room temperature and 12 V
n
12 mW typ. in standby mode
The DCI-GSI1 uses chip-internal overlay units of the MPC56x. There is an error in some versions of MPC56x chips with regard to using these
overlay units; Freescale has confirmed this (published as CDR_AR_1073). Ensure that your application or chip version is not affected by this
error. You can also contact dSPACE to exclude problems in connection with this error.
2)
If JTAG/Nexus with MPC5xxx microcontroller is used.
1)
574
2015
Introduction
Product
Order Number
Generic Serial Interface DCI-GSI1
n
DCI_GSI1
Application Fields
Order Information
Relevant Hardware
Order Number
n
DCI_GSI1_ENC
n
Microcontroller-specific connector adapters
n
Please inquire
n
Accessory kit for DCI_GSI1
n
DCI_GSI1_C
n
Interface cable with optoisolation
n
USB_CAB4
n
PC connection cable
n
USB_CAB5
n
Power supply cable for DCI-GSI1 with galvanic isolation
n
PWR_CAB7
n
LVDS Link Cable (to connect MicroAutoBox and DCI-GSI1 or DPMEM PODs)
n
LVDS_CAB1
n
LVDS Link Cable (to connect DS4121 and DCI-GSI1 or DPMEM PODs)
n
LVDS_CAB2
2015
575
Engineering
Hardware
n
Enclosure for DCI-GSI1
Software
Hardware
Optional
ECU Interface Hardware / Additional Bypass Interface Solutions
Additional Bypass Interface Solutions

Customerspecific DPMEM PODs and onchip debugging interfaces
Highlights
n Dedicated interfaces tailored for customer-specific
use cases
n Solutions for a wide range of microcontrollers
already available
n Reliable systems proven in several thousand
installations world-wide
Application Areas
When the external bypass method is used for rapid control
prototyping, there are often several possible ways of diverting the flow of data from the ECU to the prototyping system
and back. In cases where a dSPACE standard bypass interface
is not applicable, a customer-specific plug-on device (POD)
may be a suitable solution. dSPACE offers a wide range of
options for such PODs, meeting the needs of numerous
microcontroller types and individual applications. We recommend you consult us on bypassing issues at an early project
stage, to gain maximum benefit from one of dSPACEs
standard solutions and significantly reduce engineering
costs.
Key Benefits
From many years of experience with bypass interface
development, dSPACE has a long list of well proven solutions
to offer. You can also order a custom bypass interface,
precisely tailored to the microcontroller of your production
ECU and your application.
Bypass Interfaces Supported by dSPACE Including CustomerSpecific Solutions

Strategy
Bypass Interface Solution
Bypassing via DPMEM POD
Parallel interface
n
Standard product, e.g., DS541 DPMEM POD for MPC55xx microcontrollers
n
Customized DPMEM POD
Bypassing via OnChipDebugging Serial interface

Interface
n
Standard products: DCIGSI1 and DCIGSI2 (p. 570) for microcontrollers specified
Bypassing via XCP on CAN
n
Standard product: One CAN channel on ECU is used
CAN interface
Bypassing via CCP using CAN
576
n
Customerspecific PODs or specific adaptations of the DCIGSI1 and DCIGSI2
n
Standard product: One CAN channel on ECU is used
Bypassing via XCP on Ethernet

(UDP/IP and TCP/IP)
Ethernet interface
Bypassing via XCP on FlexRay
FlexRay interface
n
Standard product: LVDSEthernet Link Cable (LVDS_CAB13/14), DS1007 (p. 362)
with integrated Ethernet interface, MicroAutoBox II Ethernet I/O interface (p. 522)
n
Standard product: One FlexRay channel on ECU is used
2015
Introduction
ECU Interface Hardware / Additional Bypass Interface Solutions
CPU
Bypass Interface
Freescale 68HC11
n
Customer-specific: DPMEM POD
Freescale 68HC12
n
Freescale 68HC16
n
Freescale MPC563
n
Freescale MPC555
n
Freescale MPC56x
n
Standard product: DCI-GSI1 (p. 570)
Freescale MPC55xx and MPC56xx
n
Standard product: DPMEM POD DS541 and DS543 for VertiCal connector
Application Fields
Partial List of CPUs and Bypass Interfaces
n
Standard products: DCI-GSI1, DCI-GSI2 (p. 570)
n
Standard products: DCI-GSI2 (p. 570)
Freescale MPC57xx
n
Standard product: DPMEM POD DS543 for VertiCal connector
n
Infineon Aurix TC27xx
n
Standard product: DCI-GSI2
Infineon C167
n
Infineon TriCore TC1775
n
Infineon TriCore TC1766 , TC1796
n
Infineon TriCore TC1736, TC1767, TC1797
n
Standard products: DCI-GSI1, DCI-GSI2
Infineon TriCore TC1791, TC1793, TC1798
n
Infineon XC2000
n
Renesas M32R
n
Customer-specific: RTD IF POD
Software
Freescale DSP56F807
n
Renesas RH850
n
Renesas SH2/SH2A
n
Customer-specific: NBD IF POD
n
Standard products: DCI-GSI1
Renesas V850
n
n
Standard product: DCI-GSI1, DCI-GSI2
n
Standard products: DPMEM POD DS543 for VertiCal connector
ST-Microelectronics ST10-F280
n
Toshiba R3900
n
Freescale HCS12
n
Texas Instruments TMS470
n
Hardware
ST-Microelectronics SPC564A80
Control algorithm
DPMEM
Processor Board
(DS1005 or DS1006)
DPMEM
DS4121
CustomerSpecific POD
Engineering
I/O
and/or
standard
ECU
functions
Data,
Interrupts, etc.
Electronic Control
Unit (ECU)
Control algorithm
DPMEM
or
Processor Board
(DS1007)
DPMEM
MicroAutoBox II
CustomerSpecific POD
I/O
and/or
standard
ECU
functions
Electronic Control
Unit (ECU)
The DS1007 (p. 362) and the MicroAutoBox II (p. 522) offer standard Ethernet interfaces.
2015
577
Bypassing via DPMEM POD: a customer-specific POD combined with the DS4121 ECU Interface Board (p. 412) provides a fast and safe
communication between your ECU and your prototyping system.
Engineering
dSPACE Engineering Services ____________ 580
Engineering / dSPACE Engineering Services
dSPACE Engineering Services

Dedicated assistance for all development phases
Highlights
n Globally available engineering and consulting services
complementing dSPACE's product range
n Custom hardware and software adaptations
n Fast response
n Experienced team of engineers
n Local and global projects, from small projects to
complete turnkey solutions
Key Benefits
dSPACE systems are easy to get up and running however,
if a project is more complex, if individual solutions are needed
or if there is high time pressure, you can trust dSPACE's
fast, competent and reliable engineering and consulting
services. Experienced engineers support you with smallscale project aid as well as with complete turn-key solutions. And dSPACE engineers can also help you on-site
even as residents. dSPACE's engineering services enable you
to quickly work independently with our tools and to acquire
the necessary product know-how from dSPACE's specialists.
For global projects, dSPACE's internationally networked
team of specialists as well as our central project coordination guarantee smooth and rapid project progress towards
successful project completion. dSPACE engineering services
are provided worldwide thanks to the dSPACE headquarters and three project centers in Germany, the three dSPACE
locations in Japan, and the dSPACE locations in France, the
U.K., the USA, and China. dSPACE engineering and consulting services are available for every phase of development, so
that you can concentrate fully on your actual tasks. Moreover, dSPACE specialists provide standard training courses as
well as customer-specific courses, also on site if requested.
Typical Services (Examples)
Description
Tool introduction
n dSPACE Engineering Services help you collect all the information needed for making your decision so
as to ensure the long-term viability of your system. For example, dSPACE offers feasibility studies, the
development of application scenarios, benchmarking, pilot projects, and specific training and coaching.
Process consulting
n dSPACE supports you in optimizing your development processes and in combining dSPACE tools and
Turn-key solutions
n dSPACE Engineering Services offer complete ready-to-use solutions even for complex application scenarios.
third-party tools efficiently in one single tool chain.

If required, you can receive assistance throughout the entire dSPACE tool chain, including requirements
analysis, specification to implementation, system delivery, and on-site commissioning and more.
Maintenance services and life cycle support
n To ensure that your system works properly even if requirements change, dSPACE services go far beyond
system delivery. Services include, for example, software adaptations, interface extensions, hardware
modification and expansion, and model adaptation.
580
2015
Introduction
Overview of Engineering Services

System Architecture
Details (Examples)
Integrating SystemDesk (p. 40) into

customer-specific development processes
n Custom integration with basic software configuration tools
Application Fields
Service (Examples)
n Custom integration with TargetLink (p. 180) and other behavior modeling tools
n Adapting SystemDesk to customer-specific data management solutions
Migrating customer-specific architectures
n Importing legacy system and software information from non-AUTOSAR formats

n Integrating non-AUTOSAR code
AUTOSAR support
n Support for introducing the AUTOSAR-compliant development of software architectures
Model analysis and advice
n Help in analyzing the efficiency, safety, and reusability of your models and modeling style
n Assistance in creating and optimizing company-specific guidelines and in applying industry-proven standards
Tool automation
n Developing custom scripts (e.g., mapping of architecture elements based on naming conventions, connection
of software components based on customer rules)
Software
Rapid Control Prototyping

Service (Examples)
Details (Examples)
Custom solutions
n Custom I/O interfaces (e.g. FPGA-based I/O modules for DS5202/DS5203 FPGA boards or MicroAutoBox II)
n Custom RTI blocksets
n Modifying and designing signal conditioning and power stage modules for RapidPro hardware (p. 542)
n Integrating third-party hardware and software (e.g., for developing driver assistance systems)
Turn-key prototyping systems

(from selective services to complete
turn-key systems)
n Concept design
n System configuration
n Signal list / wiring harness specification
Hardware
n Wiring harness assembly

n I/O model and system tests
n On-site commissioning
n Hands-on training
Bypassing
n ECU-specific configuration of dSPACE bypass services and integration into ECU source code
n Development of ECU-specific plug-on devices and connector adapters for the dSPACE bypass interfaces DCI-
GSI1 and DCI-GSI2 (p. 570)

n Development and customer-specific adaptation of ECU flash programming tools
n Support for setting up HEX-code-based external and internal bypassing projects with the ECU Interface
Engineering
Manager (p. 226)
ECU Autocoding
Service (Examples)
Details (Examples)
Tool introduction
n Hands-on support during introduction of TargetLink (p. 180)

n Custom TargetLink training
n Defining interfaces to other tools used in the project
n Defining project configurations (project template / TargetLink Data Dictionary)
n Connecting to existing data bases, import/export of variable files (e.g., XLS, .m)
n Linking the model and TargetLink Data Dictionary
n Creating customer-specific utilities and scripts
n Adapting documention generation or A2L file generation
n Custom block libraries and/or I/O blocksets
n Intregrating with SYNECT for central management of TargetLink models, model interfaces, and parameter sets
n Integrating with SYNECT Test Management
2015
581
Integrating TargetLink into the

customers development processes
ECU Autocoding
Service (Examples)
Details (Examples)
Model analysis and advice
n Help
in analyzing your models and modeling style with regard to efficiency, safety, and reusability
in creating and optimizing company-specific guidelines and in applying industry-proven
standards
n Assistance
AUTOSAR integration
n Support for developing and integrating AUTOSAR-compliant software components
ECU integration
n Support for integrating the generated code in the ECUs software environment
Tool chain development and maintenance
n Specification and development of complete tool chains around TargetLink

n Maintaining tool chains
n Migration to new versions
Process consulting
n Consultation
on issues such as model, code and data exchange between ECU suppliers and OEM,
and between function and software developers; developing safety-relevant applications; software
development according to ISO 26262. Advice on responsibilities, intellectual property, etc.
HIL Testing
Service (Examples)
Details (Examples)
Turn-key HIL systems

(from selective services to complete turn-key
systems)
n Concept design, hardware planning, project management

n Signal list / wiring harness specification
n Developing custom hardware (e.g. lambda probe simulation, ECU mount, gearbox mount, valve signal
detection unit, 1-D and 3-D motion platforms, steering test benches, FPGA-based solutions, hardware
for load simulation)
n Developing custom software (e.g., Simulink and ConfigurationDesk models)
n Open- and closed-loop HIL system tests
n HIL systems for applications such as testing complete hybrid powertrains, battery management, etc.
n Implementing sensor and actuator models and protocols
n Custom tools to manage the HIL system, e.g., for variant handling
n Custom FPGA applications (e.g., e-drive models, special I/O functions) based on XSG library
n On-site commissioning
n Hands-on training
n Resident engineers (see also "Test Management and Automation", p. 584)
Simulation models
n See table "Modeling" (p. 583)
Test management and automation
n See table "Test Management and Automation" (p. 584)
Process consulting
n Integrating HIL testing in the ECU development process and tool environment
n Optimizing HIL testing activities by means of variant and workflow management
n Partitioning between components, subsystems, and full-vehicle HIL simulators
n Exchanging models and data between OEM and supplier
n Consulting on HIL configuration management
582
2015
Introduction
Modeling
Service (Examples)
Details (Examples)
Model parameterization/calibration and

validation
n Parameterizing and validating Automotive Simulation Models (ASMs) (p. 236)

n Parameterizing third-party models
Application Fields
n Adapting models and model parameters for closed-loop HIL tests

n Validating models against measurement data
Model integration
n Integrating ASMs, customer models, and third-party models into a HIL, MIL, or SIL environment
n Integrating special maneuvers, roads, vehicles, etc. in the ASM Vehicle Dynamics and ASM Traffic
simulation environment
n Combining the above models, for example, to create an entire virtual vehicle
n Handling variants of models in a superset model
Model development and adaptation
n Developing and adapting model components, e.g. for ASM Engine (CNG engine, special injection
systems, truck components, ...), ASM Vehicle Dynamics (air suspension, parking assistant systems, special
differentials, ...), or drivetrain applications (electric vehicles, hybrid-electric drivetrains)
n Developing custom import and export filters for parameterizations, road descriptions, etc.
n Developing and adapting model components for customer models
n Closed-loop HIL, MIL, and SIL tests
Software
n Integrating ASMs into your development process

n On-site support and resident engineers for modeling tasks
n Developing custom pre- and postprocessing tools
Engineering
Hardware
n Special training classes for ASM users
2015
583
Further support
Test Management and Automation

Service (Examples)
Details (Examples)
AutomationDesk (p. 156) jump start
n Creating concepts for test scenarios and test cases

n Implementing examples
n Hands-on training
AutomationDesk customization and test

automation engineering
n Integrating AutomationDesk into your development and test process

n Tool connections, e.g., Microsoft Excel, Vector CANoe, Vector CANstress, and other third-party tools
n Developing test automation frameworks according to your requirements (e.g., project and library
structure, test development process)

n Developing import routines for third-party test formats
n Implementing tests and test examples
n Extending AutomationDesk with custom test steps and test libraries
n Adapting automatic reports to your requirements
n On-site services for tool support; resident engineers covering the whole test process
Test management and process support
n Setting up test processes from test specification to test results

n Setting up an environment for the central management of all test data
n Integrating requirements management, test management and test automation
n Test system maintenance
n Project-specific training for your engineers
n Consulting on test modeling in AutomationDesk for efficient use in SYNECT Test Management (p. 272)
584
2015
Introduction
Virtual Validation
Service (Examples)
Details (Examples)
Tool introduction (VEOS , p. 100)
n Customer-specific training, consulting and support

n Configuring and building virtual electronic control units based on Simulink models or C-code
Application Fields
Integration of virtual validation into customerspecific development processes
n Connecting several virtual electronic control units to form complex simulation systems
n Designing, implementing and maintaining tool chain
Customer-specific tool chains and integration
n Developing customer-specific scripts (e.g., data exchange between several tools, creating and testing
simulation systems and virtual control units)

n Tool connections, e.g., VEOS (p. 100), TargetLink (p. 180), SystemDesk (p. 40), ConfigurationDesk
(p. 48), ControlDesk Next Generation (p. 106), or Simulink, or other third-party tools
n Integrating V-ECUs into real-time simulations
n Process support
V-ECU on HIL systems
Service (Examples)
Software
Data Management
Details (Examples)
Tool introduction (SYNECT , p. 270)
n Customer-specific training, consulting and support

Process consulting and tool chain integration
n Integrating requirements management, test management and test execution

n Optimizing testing activities through efficient variant handling
n Integrating signals and parameter management from simulation to calibration
n Optimizing signal and parameter management through efficient variant handling
n Customizing SYNECT to match customer data
n Integrating SYNECT data management with in-house tools
Hardware
n Consulting on test modeling in AutomationDesk for efficient use in SYNECT Test Management (p. 272)
n Consulting on model life cycle management and the use of SYNECT Model Management (p. 280)
n Customizing model import and export
Engineering
Custom Training Courses

Our specialists will provide a wealth of knowledge and
experience to get your project moving: in our regular,
standard training courses, in special courses tailor-made
for you, and if you want, on site. The instructors are experienced dSPACE engineers.
n Support and Maintenance (p. 588)

n www.dspace.com/go/trainings
2015
585
Support: An Integral Part of the Product

dSPACE offers high-quality technical support. When you
call us or use the support e-mail address or the form on our
website, your request is immediately forwarded to the right
support, application, or development engineer.
Support: An Integral Part of the Product ____ 588
Software Maintenance Service (SMS) ______ 588

Support: An Integral Part of the Product
We regularly receive feedback from customers saying they
are very satisfied with the quality and response time of our
support services. dSPACE offers high-quality technical support for any technical problem. When you call us or use
our support mail address, your request is immediately

forwarded to the right support, application or development
engineer. We regard support as an integral part of our
products.
If You Encounter a Problem

If you encounter a problem using dSPACE products,
please contact your local office:
n dSPACE Offices: www.dspace.com/go/locations
n Distributors: www.dspace.com/go/distributors
For countries not listed, please contact our
headquarters in Paderborn, Germany.
n www.dspace.com/go/support
n Tel.: +49 5251 1638-941
n support@dspace.de
If possible, please provide your execution key number
together with your support request. The number indicates
the type of support applicable, i.e., standard support or
Premium Support (see below).
Software Maintenance Service (SMS)

The dSPACE Software Maintenance Service (SMS) maximizes the value of your investment in dSPACE systems by
giving you access to regular software upgrades and
Premium Support. The service is available for an annual fee.
For software products with SMS, you will automatically
receive all upgrades and enhancements released during the
maintenance period. These include the latest feature
innovations as well as compatibility with new MATLAB
releases. The dSPACE Software Maintenance Service includes
Premium Support, which gives you, for example, telephone
588
support, online support via WebExTM, and consultation with

senior staff from the dSPACE development departments
when appropriate.
For detailed information on the entire SMS offer and on the
effective fees, please contact your local dSPACE office or
your local distributor for dSPACE products:
n www.dspace.com/go/locations
n www.dspace.com/go/distributors
(For countries not listed, please contact our headquarters
in Paderborn, Germany.)
2015
Introduction
Safe Use of dSPACE Products / Third-Party Brands and Product Names
Warning!
Electrical Safety
Using dSPACE products can be dangerous. You must carefully read and follow the instructions below and in the user manuals. dSPACE products
enable you, the user, to influence or control electronic and mechatronic systems. The user actions involved may cause hazards which result in
property damage, personal injury, or death.
Software
Application Fields
Application Environment Noncontractual Use

dSPACE products must be used for development, research, and test purposes only. Using the dSPACE products for purposes other than these is deemed to be improper and
noncontractual use. This especially applies to any use in production machinery and in vehicles intended for sale to end users. Note that in the context of these restrictions,
the term dSPACE products includes dSPACEs production code generator TargetLink, but not the actual code generated by TargetLink.
Safety measures
n Work on dSPACE hardware systems and the connected electrical equipment must be carried out only by a skilled electrician (or by instructed persons under the supervision
and guidance of a skilled electrician) and in accordance with electrical engineering rules and regulations. To avoid property damage, personal injury, or death, the user must
under all circumstances take all the steps to protect against system failures that a reasonable user would take, including but not limited to back-up or shutdown mechanisms.
n Any in-vehicle use of dSPACE products throughout development, research or test purposes requires the use of enclosed test tracks that are specially safety-secured for
the specific purpose. Specially safety-secured in this regard means with appropriately restricted access and further appropriate safety measures. If the user intends to use
dSPACE products outside enclosed tracks, he/she has to check with the local authorities under which circumstances this is possible. The user and the local authorities
involved bear full responsibility for such use.
The user might want to perform safety-critical interventions that affect vehicle behavior, such as the stimulation of a bus system, or the calibration or bypassing of in-vehicle
electronic control units (ECUs). If this is the case and where dSPACE products are deployed in conjunction with ECUs which would be a hazard if they malfunctioned, the
user must take appropriate measures to ensure that the overall system enters a safe state if a dangerous situation occurs. Appropriate measures in this regard might be,
for example, implementing emergency shutdown or a limp-home mode.
n Any data or code acquired through the use of dSPACE products must be verified for reliability, quality, and accuracy prior to use or distribution. This applies especially to
calibration data, to measurements that are used as a basis for calibration work, and to code produced by dSPACEs production code generator TargetLink.
Liability
It is your responsibility to adhere to instructions and warnings. Any unskilled operation or other improper use of dSPACE products in violation of the respective safety
instructions, warnings or other instructions contained in applicable user manuals constitutes contributory negligence, which may lead to a limitation of liability by dSPACE
GmbH, its representatives, agents and local dSPACE companies, to the point of total exclusion, as the case may be. Any exclusion or limitation of liability according to other
applicable regulations remains unaffected.
Important Information on Third-Party Brand Names and Product Names

The text within this document mentions several third-party brand names and/or product names. With regard to any third-party brand names and/or product name the
following applies:
n Brand
names and product names are trademarks or registered trademarks of their respective companies or organizations.
explicitly stated otherwise, mentioning third-party products does not imply any endorsement or recommendation of these products. The absence of a company
name or product name does not imply any evaluation.
n Mentioning third-party names aims solely to illustrate certain capabilities of dSPACE products, and is not, or not necessarily, a statement of compatibility in each individual
use case or of suitability for a specific use case. Please always check with dSPACE and with the vendor of the third-party product under which circumstances products and
product versions are compatible with each other, and which are suitable use scenarios.
n To purchase or get technical support for third-party products, please contact the third-party product vendor directly.
n Where links to the websites of other providers have been provided to supplement the dSPACE GmbH contents, said links are intended solely to facilitate access to generally
available information sources. The linked sites were inspected for illegal contents, but are subject to changes that are beyond our control. Should illegal contents on any
such websites become known to you, please inform us of this fact by e-mail to webmaster@dspace.de.
n No offers, obligations, or binding statements from dSPACE GmbH, including but not necessarily on the availability of products or services, can be inferred from the information in the Catalog. For information on these, please send your inquiry to info@dspace.de.
n AutomationDesk, CalDesk, ConfigurationDesk, ControlDesk, dSPACE, Embedded Success dSPACE, Green Success, MicroAutoBox, ProMINT, SCALEXIO,
SYNECT, SystemDesk, TargetLink, and VEOS are trademarks or registered trademarks of dSPACE GmbH in the United States of America or in other countries or both.
n This document mentions brand names and products of the following third-party companies or organizations: AIM (AMC-FDX-2), Airbus (AFDX), AMD (Quad-Core AMD
Opteron), Apache Subversion, ASAM, AUTOSAR, Avionics Interface Technologies (AIT, PMC modules), Axiom Manufacturing (Axiom CMD-05651, Axiom CME-0555,
Axiom MPC5554DEMO), Beckhoff (FB1111-0140), Berner & Mattner (CTE), Bosch (CC196, CC770, CJ125, E-Ray controller, LSU4.2, LSU4.9, LSU ADV), BTC Embedded
Systems (BTC EmbeddedSpecifier, BTC EmbeddedTester, BTC EmbeddedValidator), Cosmic Software (Cosmic compilers), Delta Elektronika (SM15/100, SM35/45, P183),
DENSO (PLUS2.1, PLUS3.x), Eberspcher (FlexCard Cyclone II, FlexCard Cyclone II SE, FlexCard USB), Elektrobit (EB) (EB 61x0, EB Assist ADTF, tresos, tresos Studio), EmergeEngineering (MEDKit), ETAS (INCA), Freescale (56F83xx, 68HC11, 68HC12, 68HC16, CodeWarrior (Metrowerks), DSP56F807, HCS12, MPC5xx, MPC55xx, MC56F83xx,
M68EVB912DP256, MPC5561EVB, MPC5604BEVB, MPC8240, MPC565, MPC563, MPC555, MPC56x, MPC56xx, S12X), Future Technology Devices (FT232BM), GE Intelligent Platforms (Bus Tools/ARINC 2.61, IP-429HD-88P module, IP-717-HBP), Glenair (Glenair), Green Hills Software (Green Hills compilers), Hewlett-Packard (HP) (Quality
Center), Hilscher (Hilscher modules, SyCon), Hypertac (Hypertac), IBM (PowerPC 405CR, PowerPC 603e, PPC 750GL, PPC750GX, Rational DOORS), I+ME ACTIA (i+ME
eCAN C167 CR), Infineon (C16x, C167, SK-EB XC2287, TriBoard TC1766, TC1767, TC1791, TC1793, TC1796, TC1798, TLE6259, TriCore, XC2000), Intel (Atom N270/1.6
GHz COM Express processor module, Core i5, Core i7, Pentium, XEON), JSOL Corporation (JMAG-RT), Kontron (Kontron ETX module), Kvaser (LAPcan, LAPcan II,
Leaf Professional, Leaf Professional LIN (USB), Memorator Professional, USBcan II, USBcan Professional), Laminar Research (X-Plane), LTi (ServoOne TWINsync interface),
Maxim Integrated Products (MAX3057), Microsoft (DirectShow, Excel, Source-Code Control Interface, SQL Server, Visual C++, Visual Studio, Windows, Windows
XP, Windows Vista, Word), MISRA (MISRA, MISRA AC-TL), Model Engineering Solutions (Model Examiner (MXAM), MTest, M-XRAY, Quality Commander), MOST
Cooperation (MOST), Motorola (Motorola 68336), NEC (V850FX3 CAN-IT), Nokia (HERE), NXP (82C251, SJA1000, TJA1054), Oracle (Orade), ParallelGraphics (Internet Scene
Assembler), PikeTec (TPT), PTC (Integrity), PushOk Software (SCC API plug-in), QNX Software Systems (QNX Realtime Operating System), RA Consulting (DiagRA), Reactive
Systems (Reactis), Renesas (CDK7058, M32R, M3A2154, SDK72513, SH-2, SH2A, SH4A, V85x), SAMTEC (FOLC-125-01-S-Q-LC), Schaeffler Engineering (StyleChecker), SICK
(Hiperface), SIMPACK (SIMPACK), Softing (Diagnostic Tool Set DTS, DTS7, EDICcard-based diagnostic interface VAS5163, EDIABAS), Spectrum Digital (VC33 DSP), SQLite
(SQLite), ST-Microelectronics (SPC564A80, ST10-F280), Tasking (Tasking compilers), TDK-Lambda (Genesys), Testwell (CTC++), TEWS Technologies (TIP150-41), Texas Instruments (C31, C3X/4X Code Composer, TMS320F240 DSP, TMS320P14 DSP, TMS320 Optimizing C Compiler, TMS320VC33, TMS470, SN75176), MathWorks (MathWorks,
MATLAB, Real-Time Workshop, Simulink, Simulink Coder, Stateflow, Stateflow Coder), Toshiba (R3900, TMP1984FDF), TV SD (TV SD), Vector (CANalyzer,
CANape, CANcard, CANcase, CANscope, CANstress, CANoe, VN16xx series, VN7600, VN89xx series, vTESTstudio), VIRES Simulationstechnologie (OpenDRIVE), WebEx
Communications (WebEx), Wind River (Wind River compilers), Xilinx (ISE Foundation, Kintex-7, System Generator, Spartan-3 XC3S4000, Spartan 6, Virtex, Vivado).
Errors and omissions excepted.
2015
589
Engineering
Hardware
n Unless
Index
3-D maps (ControlDesk) 113

3-D online animation (MotionDesk) 140
3-D road preview (Road Generator, ModelDesk) 146,
263
3-D scene building (MotionDesk) 141
A
A/D board 366, 372, 382, 386
ACC, adaptive cruise control 24, 258
Accessories 480, 484, 488, 492, 494, 505, 540, 564
ACE Kits 34
AC Motor Control Solution 460, 534
Actuators 542, 553
Adaptive cruise control (ACC) 24, 258
Additional Bypass Interface Solutions 576
Additional I/O solutions (Modular hardware) 474
ADAS, see driver assistance systems
ADASIS 24, 92
ADASIS v2 Horizon Reconstructor Blockset 92
ADTF Blockset (dSPACE) 24
Aerospace applications 26
AFDX, SCALEXIO Interface Solution for 329
Agricultural applications 28
Alternator model 247
Analog I/O 298, 332, 350, 516, 522, 542
controller boards 334, 340
MicroAutoBox II 522
MicroLabBox 516
Analog input modules (RapidPro) 559
Angular processing unit 305, 382, 386, 392, 439, 456,
464
Animation 140, 258
ANSI C (TargetLink) 180
Application fields 21
APU, see Angular processing unit
ARINC 429 327, 448
ARINC 717 450
ASAM 25
ASM (Automotive Simulation Models) 236
application examples 29, 31
battery 246-248
brake hydraulics model 256
diesel exhaust system model 245
engine models 241-245
electric components model 246-249
graphical user interface for 261
ModelDesk 261
pneumatics 256
satellite (ASM Satellite) 26
traffic simulation 257-260
trailer model 254
truck with tractor and trailer simulation 253
turbocharger model 244
vehicle dynamics simulation 250
XSG electric components model 249
AUD
interface 63, 107, 130, 571, 574
product: AutomationDesk 156
AutoBox 488
Autocoding (TargetLink) 180
Automatic production code generation (TargetLink) 180
Automatic scaling 197-198
AutomationDesk 156
Automation Server 169
Automation Module, MCD3 (ControlDesk) 138
Automation, real-time, python-based 170
Automotive applications 22-25
Automotive Simulation Models, see ASM
AUTOSAR 25
migration 206, 209, 582
590
Migration Tool (TargetLink) 209

module (TargetLink) 206
Blockset (RTI) 82
RTE Generation Module (SystemDesk) 41
Runtime Environment (RTE) 11, 40, 83, 208
system modeling 43
Autoscaling, worst-case 198
Avionics instruments (ControlDesk) 115
B
Basic software 41, 83, 84, 101, 581
Batch mode (ModelDesk) 267
Battery cell voltage emulation 514
Battery cell voltage measurement and balancing 478
Battery model 246-248
Battery simulation controller (SCALEXIO) 326
Blocksets 54-97, 150, 549
Boards 296, 332, 348
Brake hydraulics model (ASM) 256
Break-Out Box
for dSPACE Simulator 506
for MicroAutoBox II 540
for RapidPro 564
Bus board (SCALEXIO) 324
Bus Navigator Module (ControlDesk) 134
Bypassing (Rapid control prototyping)
dialog-based configuration 62
dSPACE Calibration and Bypassing Service 230
dSPACE Internal Bypassing Service 231
ECU interface board (DS4121) 412
ECU Interface Manager 226
ECU Interface Module (ControlDesk) 130
engineering services 581
hooks 65-67, 226, 230, 231
interfaces 62, 226, 230, 231, 232, 362, 412, 522,
570, 576
internal 65, 226, 231, 581
MicroAutoBox II 522
RTI Bypass Blockset 62
virtual 103
C
Calibration 63, 83, 106, 163, 205, 230, 232, 233, 235,
279
software 196
Camera-based systems 24, 119, 144, 530
Camera interface and video instrument (ControlDesk)
119
CAN
blocksets 68, 70
Bus Navigator Module (ControlDesk) 134
bypassing 63
FD (CAN FD) 70, 109, 424, 427, 522, 539
USB to CAN converter 566
CAN Navigator, see Bus Navigator Module
Car2x systems 145
CCP
RTI Bypass Blockset 62
Certification for IEC 61508 and ISO 26262
(AutomationDesk, TargetLink) 156, 158,
180, 218
Certified code (TargetLink) 219
Code, certified (TargetLink) 219
Code coverage analysis 47, 101, 199
Code optimization (TargetLink) 202
Collaboration software (SYNECT) 270
COLLADA (MotionDesk) 140
COM/DCOM interface 107, 121, 132, 138, 157, 168, 169
Combustion engine simulation, models for 240

Combustion torque modulation 241, 242
Commercial & off-highway vehicles 28
Company information, see www.dspace.com
Compilers 98
ConfigurationDesk 48
Connector panels 346, 480
Consulting (dSPACE Engineering Services) 580
ControlDesk Next Generation 106
avionics instruments 115
Basic version 110
Bus Navigator Module 134
ECU Diagnostics Module 131
ECU Interface Module 130
Failure Simulation Module 137
MCD3 Automation Module 138
Multiprocessor Module 126
Operator version 124
PC-based simulation with VEOS 123
SCALEXIO Multicore Module 128
SCALEXIO Multiprocessor Module 129
SCALEXIO Platform Module 127
Signal Editor Module 133
Standard Platforms Module 125
Controller board 304, 334, 340, 352, 356, 362
Control unit blockset (RTI, RapidPro) 549
Control Unit with MPC565 (RapidPro) 556
Coverage analysis 47, 199, 221
Crankshaft/camshaft sensor input module 560
Crossing traffic simulation 257, 260
Customer-specific development (Engineering) 580
Customer examples 22-37
Custom models 237, 266, 268
Customer-specific RapidPro modules 559
Customer support 585
Customized circuits
integrating (DS4201) 416
C code 44, 54, 98, 100, 180
C compilers 98
Cylinder pressure indication, FPGA-based
(MicroAutoBox II) 533
Cylinder pressure simulation (ASM) 243
D
D/A board 375, 382, 386, 392
Data dictionary (TargetLink) 213
Data management software (SYNECT) 270
DBC files 41, 44, 68, 70, 73
DCI-CAN1 566
DCI-GSI1 570
DCI-GSI2 570
DCI-KLine1 568
Demo equipment (for single-board hardware) 347
Development process 10-13
Diagnostics 52, 106, 131, 138, 163, 496
Diesel engine simulation 242, 243, 244, 245
Diesel exhaust system model 245
Diesel oxidation catalyst (DOC) 242, 245
Diesel particulate filter (DPF) 242, 245
Digital I/O 309, 312, 314, 316, 334, 340, 392, 404, 409,
410, 428, 432, 438, 516, 522, 551
Digital input module (RapidPro) 560
Digital output module (RapidPro) 560, 561
Digital output module with push-pull functionality
(RapidPro) 561
Digital position signals
capturing 400, 560
generating 456
Digital waveform capture board 428
Direct-injection driver module (RapidPro) 562
2015
Application Fields
Full-Size 500
Mid-Size 496
implementation software 54
programmable power supplies 506
real-time models (ASM) 236
Real-Time Testing 170
SCALEXIO 296
signal conditioning 314, 316, 382, 386, 410
test automation software 156
workflow management 290
dSPACE Simulator Full-Size 500
dSPACE Simulator Mid-Size 496
dSPACE XCP Service 232
dual-core processor 362, 516
2015
Hardware
Software
E
ECU
autocoding 180
bypassing, see Bypassing (Rapid control prototyping)
calibration 63, 83, 106, 163, 205, 230, 232, 233,
235, 279
code generation 180
connection 412, 570, 576
development 10-13
engineering services for ECU development 580
Diagnostics Module (ControlDesk) 131
flash programming 132, 235, 570, 581
hardware-in-the-loop simulation, see dSPACE
Simulator
integration 582
interface board 412
Interface Manager 226
Interface Module (ControlDesk) 130
rapid control prototyping, see dSPACE Prototyping
Systems
system architecture design 40
testing 296, 496
Education, research (application field) 34
Electric components simulation, models for 247, 249
Electric drives 30
Electrical drives simulation 247
Electrical safety (Safe use of dSPACE products) 589
Electrical system model 247
Electric motor 30, 31, 247, 249, 303, 362, 452, 454,
456, 464, 496, 500, 510, 511, 513, 516, 521,
522, 542
Electric Motor Control Blockset (RTI, MicroLabBox) 519
Electronic load modules 303, 510, 511, 513
Embedded PC (MicroAutoBox II) 530
Embedded software development 10
EMH Solution 464
Encoder 94, 96, 249, 328, 334, 340, 400, 430, 436,
452, 456, 460, 465, 517, 521, 549
EnDat 460, 465, 517, 535
Engineering services 580
Engine simulation models 240
Environment simulation (ASM Traffic) 258
EtherCAT slave interface 470
Ethernet blocksets (RTI) 88
Ethernet Interface 88, 362, 472, 475, 516, 522
EV1077 (Battery cell voltage emulation) 248, 514
EV1099 (Resolver SC Module for DS5203) 441
Evaluation boards (TargetLink) 185
Exhaust gas oxygen sensor modules (RapidPro) 560, 561
Expansion boxes for modular hardware 484
Experiment software (ControlDesk Next Generation)
106
Engineering
DS4302 418
DS4330 421
DS4340 426, 538
DS4342 427, 539
DS4505 424
DS5001 428
DS5101 432
DS5202 (FPGA Base Board) 452
DS5203 (FPGA Board) 438
DS5203M1 (Multi-I/O Module) 441
DS5380 510
DS5381 511
DS541 576-577
DS6101 314
DS6201 316
DS802 493
DS814 492
DS815 492
DS817 492
DS819 492
DS821 492
DS830 494
DS910 355
DS911 361
DS921 89, 475
dSPACE ADTF Blockset 24
dSPACE
company, see www.dspace.com
systems 10
dSPACE ECU Flash Programming Tool 235
dSPACE Engineering Services 580
dSPACE FlexRay Configuration Package 76
dSPACE products (overview) 14
AUTOSAR 82
bypassing, see Bypassing (Rapid control prototyping)
bus interfaces (RTI) 54-76, 88
embedded PC (MicroAutoBox II) 530
experiment software 106
FPGA programming 86, 438, 516, 522
generic serial interfaces 570
implementation software 48
intelligent I/O subsystems (RapidPro) 542, 556
MicroAutoBox II 522
MicroLabBox 516
modular hardware 348
on-target prototyping 24, 65, 231
power stages 542, 553
RapidPro 542
Real-Time Interface (RTI) 54
signal conditioning 522, 542, 551, 556
single-board hardware 332
dSPACE tool chain 10-13
dSPACE Simulator
automation 156, 170
3-D online animation 140
break-out boxes 506
bus interfaces (RTI) 68-76, 88
CAN gateway 507
data management software 270
extensions 505
failure insertion units 50, 137, 178, 300, 322, 499,
503, 504, 508, 509
FlexRay, testing FlexRay ECUs 76, 324
591
Discontinuous conduction mode (DCM) inverter 247

DO-178B/C 27, 219
Dolly trailer simulation (ASM Truck) 253
Driver assistance systems (ADAS)
ADASIS v2 Horizon Reconstructor Blockset 92
application examples 24
ASM Traffic 257, 258
MicroAutoBox II 522, 530
ModelDesk 261, 263, 264, 265
MotionDesk 140, 144, 146
TargetLink, matrix support 191
virtual test drive (VEOS) 103
Drives, electric 30
DS1005 352
DS1006 356
DS1007 362
DS1006 Advanced Support Package 475
DS1103 334
DS1104 340
DS1450 508
DS1513 524
DS1552 533
DS1553 534
DS1626 560
DS1631 560
DS1633 560
DS1634 560
DS1635 560
DS1637 560
DS1638 560
DS1639 561
DS1642 560
DS1646 560
DS1647 561
DS1661 561
DS1662 561
DS1663 562
DS1664 562
DS1667 562
DS1668 562
DS1767 563
DS1768 563
DS2002 366
DS2003 366
DS2004 372
DS2101 375
DS2102 375
DS2103 375
DS2202 382
DS2211 386
DS2302 392
DS2401 398
DS2502 305
DS2601 318
DS2621 320
DS2642 322
DS2655 311
DS2655 M1 312
DS2671 324
DS2680 306
DS2690 309
DS2907 326
DS3001 400
DS3002 400
DS4002 404
DS4003 409
DS4004 410
DS4121 412
DS4201 416
DS4201-S 417
Introduction
Index
Index
F
Failure simulation 50, 81, 137, 178, 300, 322, 449, 458,
467, 499, 504, 508, 509
Failure Simulation API Package 178
Failure Simulation Module (ControlDesk) 137
Fellow vehicle simulation (ASM Traffic) 258, 260, 265
FIBEX 41, 44, 70, 73, 76
Field Bus Solution (SCALEXIO) 330
FlexRay
bus FIU board (DS1450) 508
interface (RTI) 76
interface module 426, 538
MicroAutoBox II 522
SCALEXIO Bus Board (DS2671) 324
Flight recorder 353, 363, 517, 523, 525
blockset (MicroLabBox, MicroAutoBox II) 519, 526
FMI 25
FMU 48, 51, 100, 280, 283, 302
Force feedback support (ControlDesk) 115
FPGA
Base Board (DS5202) 452
Base Board (DS2655, SCALEXIO) 311
Board (DS5203) 438
control design (XSG AC Motor Control Library) 96
function blocks for faster implementation of FPGA
models 94
I/O extension modules for MicroAutoBox II 532
MicroAutoBox II 522
Programming Blockset (RTI) 86
RapidPro Control Unit with MPC565 556
simulations, FPGA-based 249
cylinder pressure indication (MicroAutoBox II) 501
Full-bridge driver module (RapidPro) 561, 562, 563
Fullpassing, see dSPACE Prototyping Systems
Full-Size (dSPACE Simulator) 500
Function development, see dSPACE Prototyping Systems
Function prototyping, see dSPACE Prototyping Systems
Further applications (Other Fields) 36
G
Gateway 63, 69, 71, 472, 507, 566
Generic serial interface (DCI-GSI1, DCI-GSI2) 570
Gigalink module 355, 361
GNU C compiler 98
Graphical scene design (MotionDesk) 140, 147
GSI (DCI-GSI1, DCI-GSI2) 570
Guidelines 219, 268, 581, 582
H
Hardware-in-the-loop simulation, see dSPACE Simulator
and SCALEXIO
High-current full bridge driver module (RapidPro)
562, 563
High-current half-bridge driver module (RapidPro)
562, 563
HighFlex I/O boards (SCALEXIO) 298
High-side driver module (RapidPro) 561, 562
HIL API standard 101, 104, 107, 133, 156, 165, 176
HIL hardware 296, 348, 496, 500, 505
HIL I/O 298, 350, 505
HIL simulation, see dSPACE Simulator and SCALEXIO
HIL testing, see dSPACE Simulator and SCALEXIO
H-UDI 63, 574
Hybrid drive 23, 29, 246, 500, 511, 522, 524
I
I/O subsystems (RapidPro) 542, 556
IEC 61508 12, 156, 158, 180, 218
592
IGBT pulse measurement 454, 464

Implementation software 48, 54
In-vehicle experiments
expansion box (AutoBox) 488
experiment software (ControlDesk) 106
power stages (RapidPro) 542
prototyping unit (MicroAutoBox II) 522
signal conditioning (RapidPro) 542
Incremental code generation (TargetLink) 200
Incremental encoder interface 336, 342, 400, 549
Industrial automation 30, 36, 516
Instrumentation (ControlDesk) 106, 112
Integrating third-party products
TargetLink Partner Program 220
third-party brand names and product names 589
Integration and test facility (ITF) 26, 27
Internal bypassing 62, 65, 103, 231, 581
Intersection and junction simulation (ASM) 257, 258
Inverter models 247, 249
IOCNET (SCALEXIO) 299
ISA bus 155, 337, 348
ISO 26262 25
ITF (integration and test facility) 26, 27
J
JMAG-RT/ASM tool coupling 249
Joining plate (MicroAutoBox II, RapidPro) 529
JTAG/H-UDI 574
JTAG/Nexus 63, 107, 571, 572, 574
JTAG/OCDS 63, 107, 572, 574
JTAG/SDI 63, 107, 574
Junction and intersection simulation (ASM) 257, 258
K
K-line 107, 131, 139, 163, 308, 324, 325, 568
K/L line 522
Knock sensor module (RapidPro) 560
KWP2000 131, 139, 566, 568
L
Laboratory, prototyping unit (MicroLabBox) 516
Lambda probe 314, 498, 502, 507, 560, 561, 582
LDF files 41, 44, 73
LED panels 346, 480
Liability 589, 596
LIN interface 73, 324, 421, 522
Link boards (Modular hardware) 492
Link panel (DS830) 494
Load models 247
Local services 588
Low-side driver module (RapidPro) 561
LSU (Lambda-Sonde universal, universal lambda probe)
507
LVDS 89, 90, 412, 477, 517, 522, 556, 571, 574, 576
M
Maintenance
Software Maintenance Service (SMS) 588
Man-in-the-loop 153, 259
Maneuver editor (ModelDesk) 264
MAT files 71,166, 171, 173, 264
MCD3 Automation Module (ControlDesk) 138
MCD tool 106
Measurement
ControlDesk 106
ECU interface hardware 566, 570
ECU services 221, 230

I/O boards 297, 332, 348, 516
MicroLabBox 516
MicroAutoBox II 522
ModelDesk 261
RapidPro hardware 542
Mechatronics 22-37
Medical applications 32, 516
MicroAutoBox II 522
AC Motor Control Solution 534
Break-Out Box 540
CAN FD module 539
certifications 536
cylinder pressure indication, FPGA-based 533
DS1513 524
embedded PC 530
FPGA I/O extension modules 532
joining plate (MicroAutoBox II/RapidPro) 529
Multi I/O Module DS1552 533
RTI blockset 537
watchdog mechanism 529
WLAN 530
MicroLabBox 516
Mid-Size (dSPACE Simulator) 496
MIL (model-in-the-loop) 186, 238, 261, 272
MIL-STD-1553 interface 328, 446
MISRA AC TL 219
MISRA C 219
MISRA TargetLink guidelines, see MISRA AC-TL
Model-based control design 10
Model Compare 222
ModelDesk 261
Model implementation
RTI 54
Model-in-the-loop (MIL) 186, 238, 261, 272
Modeling guidelines for TargetLink 219
Model management (SYNECT) 280
Model referencing 54, 101, 200
Modular hardware 348
MotionDesk 140
automatic driving maneuvers 152
blockset 150
multitrack mode 148
Multi-PC Interface Kit 154
scene editor 147
Multibody system (MBS) 251-254
Multicore Module, for SCALEXIO (ControlDesk) 128
Multi-channel A/D board 366
MultiCompact (SCALEXIO) 298
Multi I/O Module DS1552 (MicroAutoBox II) 533
MultiLink panel (DS830) 494
Multi-PC Interface Kit (MotionDesk) 154
Multiprocessor Module (ControlDesk) 126
Multiprocessor Module, for SCALEXIO (ControlDesk)
129
Multiprocessor systems 60, 126, 129, 175, 296, 304, 349,
355, 361, 362
Multirate code (TargetLink) 181
Multiswitch instrument (ControlDesk) 113
N
NBD 63, 107, 571, 574, 577
Nexus, see JTAG/Nexus
Nexus/READI 63
O
Off-highway (application field) 28
Offline simulation 41, 82, 87, 100, 101, 123, 141, 143, 237
2015
Q
Quad-Core AMD Opteron 356
S
Safety instructions (dSPACE products) 589
Satellites 26, 27
2015
Hardware
Software
Application Fields
SC-AI 4/1 560

SC-AI 10/1 560
SCALEXIO 296
AFDX, solution for 329
aerospace solutions 327, 328
ARINC 429 interface 327
battery simulation 302, 326
bus board 324
digital I/O board 309, 316
EtherCAT interface 330
Ethernet solution 89
failure simulation 322
Field Bus Solution 330
FPGA base board 311
FIU and power switch board 322
implementation software (ConfigurationDesk) 48
introduction 296
I/O unit 306
MIL-STD-1553 interface 328
Multi-I/O board 314
multicore module (ControlDesk) 128
multiprocessor module (ControlDesk) 129
platform module (ControlDesk) 127
processing unit 304
PROFIBUS interface 330
PSI5 Master/Slave Solution 331
signal generation board 320
signal measurement board 318
SC-CCDI 6/1 560
SC-DI 8/1 560
SC-DO 8/1 560
SC-DO 8/2 561
SC-EGOS 2/1 560
SC-KNOCK 4/1 560
SC-SENS 4/1 560
SC-TC 8/1 560
SC-UHEGO 2/1 561
SCR (Selective catalytic reduction) model 245
SCRAMNet+ Interface 442
Selective catalytic reduction (SCR) model 245
Sensor simulation 396, 397, 398, 432, 456, 464, 477
Sensor supply module (RapidPro) 560
Sequence builder (AutomationDesk) 160
Serial Interface Board (DS4201-S) 417
Service-based bypassing, see Bypassing (Rapid control
prototyping)
Services
dSPACE XCP Service 232
Signal & Parameter Management (SYNECT) 277
Signal conditioning 296, 298, 314, 316, 382, 386, 410,
438, 441, 456, 465, 479, 496, 498, 500, 502,
507, 522, 542, 551, 556, 581
Signal Editor Module (ControlDesk) 133
SIL (software-in-the-loop) 29, 46, 47, 186, 238, 239,
272, 583
Simulation
hardware-in-the-loop, see dSPACE Simulator
model-in-the-loop (MIL) 186, 238, 261, 272
offline 41, 82, 87, 100, 101, 123, 141, 143, 237
software-in-the-loop (SIL) 29, 46, 47, 186, 238, 239,
272, 583
processor-in-the-loop (PIL) 47, 101, 186, 272
Simulation models (ASM) 236
Simulator hardware 296, 496, 500
Simulink
open simulation models (ASM) 236
Engineering
P
Partitioning models 61
Partner Program, TargetLink 220
PCI 327-330, 332, 340, 351, 442, 446, 486, 491, 492,
494
PCIe see PCI Express
PCI Express 304, 332, 340, 351, 486, 491, 492, 494,
530
PCMCIA 136, 351, 486, 491, 492, 494
PC-based simulation (VEOS) 100, 123
PC cards 340
Pedestrian simulation 144, 257
PFD (Primary Flight Display) (ControlDesk) 115
PGI1 (Programmable Generic Interface) 331, 477
PHS bus (Modular Hardware) 328
PHS++ 352, 357, 363, 382, 425, 444, 446, 473
PIL (processor-in-the-loop) 47, 101, 186, 272
Platform API Package 176
Plotter (ControlDesk) 114
Plug-on device (POD) 412, 576
Pneumatics (ASM) 256
POD (Plug-on device), see Plug-on device (POD)
Position Sensor Simulation Solution 456
PowerPC 334, 340, 352, 522
PowerPC compiler 98
Power RealTime Library 97
Power stages (RapidPro) 542, 553
Process integration 580
Processor hardware 304, 334, 340, 352, 356, 362,
516, 522
Processor-in-the-loop (PIL), see PIL (processor-in-the-loop)
Production code for ECUs (TargetLink) 180
Product Overview 14-19
PROFIBUS interface 444
Programmable Generic Interface (PGI1), see PGI1
Prototyping, see dSPACE Prototyping Systems
Prototyping Board (DS4201) 416
PS-DINJ 2/1 562
PS-FBD 2/1 561
PS-HCFBD 1/1 562
PS-HCFBD 1/2 563
PS-HCHBD 2/1 562
PS-HCHBD 2/2 563
PS-HSD 6/1 562
PS-LSD 6/1 561
PSI5 331
PWM
capturing 318, 334, 386, 428
generating 320, 334, 404, 522
PWM Measurement Solution 454
PX10 484
PX20 484
PX4 484
Python 46, 117, 121, 160, 170, 176, 178, 261, 267,
272, 567
Python-based real-time test automation 170
R
R&D controller board (DS1104) 340
Radar sensor model 258
RCP, see dSPACE Prototyping Systems
RapidPro hardware 542
application-specific configurations 546
break-out boxes 564
communication interface modules 556, 557
ConfigurationDesk 48, 52
Control Unit Blockset (RTI) 549
Control Unit with MPC565 559
hardware overview 550
intelligent I/O subsystem 545, 556
power stages 553
Power Unit 553
SC/PS modules 559
SC Unit 551
signal conditioning 551, 556
use scenarios 544, 545
Rapid control prototyping, see dSPACE Prototyping
Systems
READI/Nexus, see Nexus/READI
Real-time animation 140, 258
Real-time code for dSPACE hardware
ConfigurationDesk (for SCALEXIO) 48
RTI 54
Real-time hardware 304, 334, 340, 352, 356, 362,
516, 522
Real-Time Interface (RTI) 54
ADASIS v2 Reconstructor Blockset 92
AUTOSAR Blockset 82
blocksets for 59
Bypass Blockset 62
CAN Blockset 68
CAN MultiMessage Blockset 70
Electric Motor Control Blockset (MicroLabBox) 519
Ethernet blocksets 88
FPGA Programming Blockset 86
FlexRay Configuration Package 76
for multiprocessor systems 60
LIN MultiMessage Blockset 73
MicroAutoBox II blockset 537
RapidPro Control Unit Blockset 549
USB Flight Recorder Blockset 364, 519, 526
Real-time models for HIL simulation 236
Real-time simulation (HIL) 296, 496, 500
Real-Time Testing 170
Remote control 40, 131, 137, 138, 141, 147, 156, 163,
166, 168, 169, 177, 229, 267, 489, 497, 498,
499, 501, 503, 506, 510, 530, 551, 553, 557
Research and education 34
Resistance sensor simulation 398
Resistive sensor simulation 398
Resolver Interface 462, 479, 517, 535
Restbus simulation
dSPACE Simulator 496, 500
Real-time Testing 170
SCALEXIO 296
Road Generator (ModelDesk) 263
Robotics 147, 150, 152, 334, 339, 340, 400, 428, 442,
516, 521
RPCU Blockset (RTI, RapidPro) 549
RTE Generation Module (SystemDesk) 41
RTI see Real-Time Interface
Runnables (AUTOSAR) 43, 46, 66, 84, 191, 206-209
593
OIL files 186, 211, 212, 214, 215

On-chip debug interfaces 64, 230, 412, 570
On-target prototyping 24, 65, 231
OpteronTM (Quad-Core AMD) 356
Optimization module, TOM (TargetLink) 202, 203
OSEK/VDX 211
Oxygen sensor modules (RapidPro) 560, 561
Introduction
Index
Index
Real-Time Interface (RTI) for 54

Single-board hardware 332
Sinusoidal position signals
measuring 400
SMS (Software Maintenance Service) 588
Software components (SWC) 44, 46, 206, 209, 210, 214
Software-in-the-loop (SIL) 29, 46, 47, 186, 238, 239,
272, 583
SPICE 218
Standard Platform Module (ControlDesk) 125
Starter model 241, 242, 247, 251
Start/stop system simulation 241-243
Stateflow
production code generation 180
Real-Time Interface for 54
Stopwatch instrument (ControlDesk) 117
Success stories 22-37
Support and Maintenance 588
SYNECT
Base 271
Introduction 270
Model Management 280
Test Management 272
Signal & Parameter Management 277
Variant Management 284
System architecture software (SystemDesk) 40
SystemDesk 40
SystemDesk Modeling Module 43
SystemDesk RTE Generation Module 41
SystemDesk V-ECU Generation Module 46
Systems Overview 10
T
Tandem-AutoBox 488
Target implementation, see TargetLink
TargetLink 180
AUTOSAR 206
autoscaling 197, 198
Base Suite 182
block library for implementation 189
blockset stand-alone 189
certification for IEC 61508 and ISO 26262 218
certified code 219
code coverage analysis 199
code optimization 202
Data Dictionary 213
DO-178B/C 26, 27, 219
evaluation boards 185
ISO/IEC 15504 218
IEC 61508 218
ISO 26262 218, 582
MISRA AC-TL 219
MISRA C 219
modeling guidelines for 219
model referencing 200
modular development 200
optimization modules (TOM) 184, 202
OSEK/VDX 211
Partner Program 220, 221
Product Support Center 183
scaling variables 197
simulation modes 192
simulation modules (TSM) 182, 184
SYNECT, connection to 216
SystemDesk, interaction with 206, 210
third-party tools 220-221
typical steps in generating production code 186
VEOS, connection to 217
worst-case autoscaling 198
594
XCP on FlexRay 62, 63, 107, 130, 576

Target optimizations 203
XCP Service, dSPACE 232
Technical support 588
X-Plane integration 26
Test automation 156, 170, 176, 178, 272
XSG AC Motor Control Library 96
Test builder library (AutomationDesk) 157
XSG Electric Components 249
Test debugging (AutomationDesk) 161
XSG Utils Library 94
Test development (AutomationDesk) 160
Testing
automation 156, 170, 176, 178, 272
control algorithms, see dSPACE Prototyping Systems
ECUs, see dSPACE Simulator
ECU functions, see dSPACE Prototyping Systems
production code 186
VEOS 100
Test Management (SYNECT) 272
Test report generation (AutomationDesk) 157
Test report generation (SYNECT ) 276
Thermocouple sensor input module (RapidPro) 560
Timing I/O 405, 411, 428, 430, 432
TOM (Target Optimization Modules) 184, 202
TSM (Target Simulation Modules) 182, 184
Tool chain 10-13
Traffic Editor (ModelDesk) 265
Traffic simulation (ASM) 257-259
Trailer simulation (ASM) 254
Training courses, see www.dspace.com/goto?trainings
Trucks 28-29, 253
TTL 96, 249, 325, 336, 341, 342, 398, 399, 400, 401, 402,
403, 405, 409, 410, 432, 433, 456, 459, 465, 468
TV 158, 218
Turbocharger model (ASM) 244
U
USB 119, 135, 136, 362, 475, 517, 519, 522, 530, 544,
545, 551, 554, 556, 566, 568, 570
USB Flight Recorder Blockset 364, 519, 526
USB to CAN Converter (DCI-CAN1) 566
USB to K-Line Interface (DCI-Kline1) 568
V
Variable array (ControlDesk) 113
Variable Editor 233
Variable valve lift (VVL) simulation 243
Variable valve timing (VVT) simulation 243
Variant-Based Workflow Management 290
Variant Management (SYNECT) 284
VCFP demo 347
V-ECU Generation Module (SystemDesk) 46
VEOS 100
Vehicle dynamics simulation
models for 250
Video instrument (ControlDesk) 119
Virtual validation 13, 100
Visualizing simulations 106, 140, 261
VME 442, 476
Voice-coil-driven flexible positioner (VCFP) 347
VRML2 141, 147
W
WLAN (MicroAutoBox II) 530
Workflow management, variant-based 290
worst-case autoscaling (TargetLink) 198
X
X86 304, 356
X86 C compiler 98
XCP on CAN 62, 63, 107, 130, 235, 566, 576
XCP on Ethernet 62, 63, 85, 107, 130, 235, 523, 525,
570, 576
2015
We Are Where You Are
Headquarters
Subsidiaries
Germany:
dSPACE GmbH, Paderborn
Project centers:
Stuttgart, Munich , Wolfsburg
USA:
France:
United Kingdom:
Japan:
China:
Distributors
dSPACE Inc., Detroit

dSPACE SARL, Paris
dSPACE Ltd., Cambridge
dSPACE Japan K.K.,
Tokyo, Nagoya,
Utsunomiya
dSPACE Mechatronic
Control Technology
(Shanghai) Co., Ltd.,
Shanghai
Australia:
Brazil:
Czech Republic
and Slovakia:
India:
Korea:
Netherlands:
Poland:
Sweden:
Sydney
So Paulo
Prague
Bengaluru
Seoul
Rotterdam
Krakow
Stockholm
Copyright 2015 by dSPACE GmbH.

All rights reserved. Written permission is required for reproduction of all or parts of this publication. The source must be stated in any such
reproduction. dSPACE is continually improving its products and reserves the right to alter the specifications of the products at any time without
notice. "AutomationDesk", "CalDesk", "ConfigurationDesk", "ControlDesk", "dSPACE", "Embedded Success dSPACE", "Green Success",
"MicroAutoBox","ProMINT", "SCALEXIO", "SYNECT", "SystemDesk", "TargetLink", and "VEOS" are trademarks or registered trademarks
of dSPACE GmbH in the United States of America or in other countries or both. Other brand names or product names are trademarks or registered trademarks of their respective companies or organizations.
Please note: To ensure that your application scenario is optimally supported by a specific dSPACE product or product combination,
please contact dSPACE for the latest information on product versions, compatibilities, and suitable use scenarios.
www.dspace.com
www.dspace.com
Catalog 2015
Company Headquarters
in Germany
United Kingdom
France
dSPACE GmbH
Rathenaustrae 26
33102 Paderborn
Tel.: +49 5251 1638-0
Fax: +49 5251 16198-0
info@dspace.de
dSPACE Ltd.
Unit B7 . Beech House
Melbourn Science Park
Melbourn
Hertfordshire . SG8 6HB
Tel.: +44 1763 269 020
Fax: +44 1763 269 021
info@dspace.co.uk
dSPACE SARL
7 Parc Burospace
Route de Gisy
91573 Bivres Cedex
Tel.: +33 169 355 060
Fax: +33 169 355 061
info@dspace.fr
China
Japan
USA and Canada
dSPACE Mechatronic Control

Technology (Shanghai) Co., Ltd.
Unit 1101-1105, 11F/L
Middle Xizang Rd. 18
Harbour Ring Plaza
200001 Shanghai
Tel.: +86 21 6391 7666
Fax: +86 21 6391 7445
infochina@dspace.com
dSPACE Japan K.K.

10F Gotenyama Trust Tower
4-7-35 Kitashinagawa
Shinagawa-ku
Tokyo 140-0001
Tel.: +81 3 5798 5460
Fax: +81 3 5798 5464
info@dspace.jp
dSPACE Inc.
50131 Pontiac Trail
Wixom . MI 48393-2020
Tel.: +1 248 295 4700
Fax: +1 248 295 2950
info@dspaceinc.com
01/2015
Catalog 2015

DSPACE Catalog2015 E Web

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DSPACE Catalog2015 E Web

Uploaded by

Copyright:

Available Formats

www.dspace.

USA and Canada

dSPACE Mechatronic Control

dSPACE Japan K.K.

dSPACE GmbH Rathenaustrae 26 33102 Paderborn Germany info@dspace.de www.dspace.com

We Are Where You Are

dSPACE Inc., Detroit

Copyright 2015 by dSPACE GmbH.

dSPACE GmbH Rathenaustrae 26 33102 Paderborn Germany info@dspace.de www.dspace.com

dSPACE Systems ___________________________________________________ 10

Product Overview __________________________________________________ 14

Automotive Industry ________________________________________________ 22

System Architecture Software ________________________________________ 40

Real-Time Interface (RTI) ______________________________________ 54

Real-Time Interface for Multiprocessor Systems (RTI-MP) ___________ 60

Real-Time Interface Bypass Blockset ____________________________ 62

Real-Time Interface CAN Blockset ______________________________ 68

Real-Time Interface CAN MultiMessage Blockset _________________ 70

Real-Time Interface LIN MultiMessage Blockset ___________________ 73

dSPACE FlexRay Configuration Package _________________________ 76

RTI FPGA Programming Blockset _______________________________ 86

Ethernet Blocksets ___________________________________________ 88

ADASIS v2 Horizon Reconstructor Blockset ______________________ 92

XSG Utils Library ____________________________________________ 94

XSG AC Motor Control Library ________________________________ 96

NEW: Power RealTime Library _________________________________ 97

NEW: RTI AUTOSAR Blockset __________________________________ 82

ControlDesk Next Generation _______________________________ 106

Test Automation Software __________________________________________ 156

AutomationDesk ___________________________________________ 156

Real-Time Testing __________________________________________ 170

Platform API Package _______________________________________ 176

Failure Simulation API Package _______________________________ 178

Support and Maintenance

MotionDesk _______________________________________________ 140

TargetLink Data Dictionary ___________________________________ 213

TargetLink Partner Program __________________________________ 220

Model Compare1) ___________________________________________ 222

ECU Interface Software ____________________________________________ 226

ECU Interface Manager______________________________________ 226

dSPACE Calibration and Bypassing Service ______________________ 230

dSPACE Internal Bypassing Service ____________________________ 231

dSPACE XCP Service ________________________________________ 232

Variable Editor _____________________________________________ 233

dSPACE ECU Flash Programming Tool __________________________ 235

Automotive Simulation Models (ASM) ________________________________ 236

Combustion Engine Simulation _______________________________ 240

ASM Gasoline Engine Basic ___________________________ 241

ASM Diesel/Gasoline Engine ___________________________ 242

ASM Diesel/Gasoline Engine In-Cylinder _________________ 243

ASM Turbocharger ___________________________________ 244

ASM Diesel Exhaust System ___________________________ 245

Electric Components Simulation ______________________________ 246

ASM Electric Components ____________________________ 247

XSG Electric Components ____________________________ 249

Vehicle Dynamics Simulation _________________________________ 250

ASM Vehicle Dynamics _______________________________ 251

ASM Truck _________________________________________ 253

ASM Brake Hydraulics ________________________________ 256

Traffic Simulation ___________________________________________ 257

ASM Traffic _________________________________________ 258

ASM Versions and License Concept ___________________________ 269

Data Management Software ________________________________________ 270

SYNECT Test Management ____________________________ 272