DSPACE Catalog2016 E Web

www.dspace.
com
Catalog 2016
dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

We Are Where You Are
dSPACE Locations Distributors

Germany: dSPACE GmbH Paderborn Australia and
Munich New Zealand: Sydney
Stuttgart Brazil: São Paulo
Wolfsburg India: Bengaluru
USA: dSPACE Inc. Detroit Korea: Seoul
France: dSPACE SARL Paris Netherlands: Rotterdam
United Kingdom: dSPACE Ltd. Cambridge Poland: Krakow
Japan: dSPACE Japan K.K. Tokyo Sweden: Stockholm
Nagoya Czech Republic
Utsunomiya and Slovakia: Prague
China: dSPACE Mechatronic Shanghai
Control Technology
(Shanghai) Co., Ltd.

Contents
Introduction
Contents
Introduction 8
dSPACE Systems ___________________________________________________ 10

Product Overview __________________________________________________ 14
Application Fields
Application Fields 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
Software 38
Software
System Architecture Software ________________________________________ 40
SystemDesk® _______________________________________________ 40
Implementation Software ___________________________________________ 48
ConfigurationDesk® __________________________________________ 48
NEW: Bus Manager __________________________________________ 54
Real-Time Interface (RTI) ______________________________________ 56
Real-Time Interface for Multiprocessor Systems (RTI-MP) ___________ 62
Real-Time Interface Bypass Blockset ____________________________ 64
Hardware
Real-Time Interface CAN Blockset ______________________________ 71
Real-Time Interface CAN MultiMessage Blockset _________________ 74
Real-Time Interface LIN MultiMessage Blockset ___________________ 77
dSPACE FlexRay Configuration Package _________________________ 80
RTI AUTOSAR Blockset _______________________________________ 86
RTI FPGA Programming Blockset _______________________________ 90
Ethernet Blocksets ___________________________________________ 92
dSPACE Ethernet Configuration Package ________________________ 96
ADASIS v2 Horizon Reconstructor Blockset ______________________ 98
Engineering
NEW: V2X Solution _________________________________________ 100
XSG Utils Library ___________________________________________ 104
XSG AC Motor Control Library _______________________________ 106
NEW: XSG Advanced Engine Control Library ____________________ 107
NEW: Electrical Power Systems Simulation Package ______________ 108
Compilers _________________________________________________ 111
Simulation Software _______________________________________________ 112
VEOS® ___________________________________________________ 112
Support and Maintenance
Experiment and Visualization Software _______________________________ 120

ControlDesk® Next Generation _______________________________ 120
MotionDesk _______________________________________________ 156
Test Automation Software __________________________________________ 172
AutomationDesk ___________________________________________ 172
Real-Time Testing __________________________________________ 190 3
2016

Contents
Software
Platform API Package _______________________________________ 196

NEW: Failure Simulation Package _____________________________ 198
Production Code Generation Software _______________________________ 202
TargetLink® ________________________________________________ 202
TargetLink Partner Program __________________________________ 240
Third-Party Tools and Services for TargetLink ____________________ 241
Model Compare1) ___________________________________________ 242
ECU Interface Software ____________________________________________ 248
ECU Interface Manager______________________________________ 248
dSPACE Calibration and Bypassing Service ______________________ 252
dSPACE Internal Bypassing Service ____________________________ 253
dSPACE XCP Service ________________________________________ 254
Variable Editor _____________________________________________ 255
dSPACE ECU Flash Programming Tool __________________________ 257
Automotive Simulation Models (ASM) ________________________________ 258
Combustion Engine Simulation _______________________________ 262
ASM Gasoline Engine Basic ___________________________ 263
ASM Diesel/Gasoline Engine ___________________________ 264
ASM Diesel/Gasoline Engine In-Cylinder _________________ 265
ASM Turbocharger ___________________________________ 266
ASM Diesel Exhaust System ___________________________ 267
Electric Components Simulation ______________________________ 268
ASM Electric Components ____________________________ 269
XSG Electric Components ____________________________ 271
Vehicle Dynamics Simulation _________________________________ 272
ASM Vehicle Dynamics _______________________________ 273
ASM Truck _________________________________________ 275
ASM Trailer _________________________________________ 276
ASM Pneumatics ____________________________________ 278
ASM Brake Hydraulics ________________________________ 278
Traffic Simulation ___________________________________________ 279
ASM Traffic _________________________________________ 280
ModelDesk ________________________________________________ 283
ASM Versions and License Concept ___________________________ 291
Data Management Software ________________________________________ 292
SYNECT® _________________________________________________ 292
SYNECT Test Management ____________________________ 294
SYNECT Signal & Parameter Management _______________ 299
SYNECT Model Management __________________________ 302
SYNECT Variant Management _________________________ 306
General SYNECT Functionalities ________________________ 309
Workflow Management _____________________________________ 312
4
2016 Limited availability outside of Europe and Asia, please contact dSPACE.
1)

Contents
Introduction
Hardware 316
SCALEXIO® Hardware ______________________________________________ 318

SCALEXIO Hardware Introduction _____________________________ 318
SCALEXIO Processing Unit ___________________________________ 328
Application Fields
DS2680 I/O Unit ___________________________________________ 330
DS2690 Digital I/O Board ____________________________________ 333
DS2655 FPGA Base Board ___________________________________ 335
DS6101 Multi-I/O Board _____________________________________ 338
DS6201 Digital I/O Board_____________________________________ 340
DS2601 Signal Measurement Board ___________________________ 342
DS2621 Signal Generation Board _____________________________ 344
DS2642 FIU & Power Switch Board ____________________________ 346
DS2671 Bus Board _________________________________________ 348
DS2907 Battery Simulation Controller__________________________ 350
Software
Additional Solutions ________________________________________ 351
Single-Board Hardware ____________________________________________ 356
Single-Board Hardware Introduction ___________________________ 356
DS1103 PPC Controller Board ________________________________ 358
DS1104 R&D Controller Board ________________________________ 364
Connector and LED Panels ___________________________________ 370
Demo Equipment __________________________________________ 371
Modular Hardware ________________________________________________ 372
Modular Hardware Introduction ______________________________ 372
Hardware
I/O Boards Overview ________________________________________ 374
DS1005 PPC Board _________________________________________ 376
DS1006 Processor Board ____________________________________ 380
DS1007 PPC Processor Board _________________________________ 386
DS2002/DS2003 A/D Boards _________________________________ 390
DS2004 High-Speed A/D Board _______________________________ 396
DS2101/DS2102/DS2103 D/A Boards __________________________ 399
DS2202 HIL I/O Board _______________________________________ 406
DS2211 HIL I/O Board _______________________________________ 410
Engineering
DS2302 Direct Digital Synthesis Board _________________________ 416
DS2401 Resistive Sensor Simulation Board ______________________ 422
DS3001/DS3002 Incremental Encoder Interface Board ____________ 424
DS4002 Timing and Digital I/O Board __________________________ 428
DS4003 Digital I/O Board ____________________________________ 433
DS4004 HIL Digital I/O Board _________________________________ 434
DS4121 ECU Interface Board _________________________________ 436
DS4201 Prototyping Board ___________________________________ 440

DS4201-S Serial Interface Board ______________________________ 441
DS4302 CAN Interface Board ________________________________ 442
DS4330 LIN Interface Board __________________________________ 445
DS4505 Interface Board (FlexRay, CAN FD) _____________________ 448
5
2016

Contents
Hardware
DS5001 Digital Waveform Capture Board ______________________ 452

DS5101 Digital Waveform Output Board _______________________ 456
DS5203 FPGA Board ________________________________________ 462
SCRAMNet+ Interface _______________________________________ 466
PROFIBUS Interface _________________________________________ 468
Interface to MIL-STD-1553 ___________________________________ 470
ARINC 429 Interface ________________________________________ 472
ARINC 717 Interface ________________________________________ 474
FPGA Base Board ___________________________________________ 476
PWM Measurement Solution _________________________________ 478
Position Sensor Simulation Solution ___________________________ 480
AC Motor Control Solution __________________________________ 484
EMH Solution ______________________________________________ 488
EtherCAT Slave Interface ____________________________________ 494
100 Mbit/s Ethernet Interface (UDP/IP, TCP/IP) ___________________ 496
Additional I/O Solutions _____________________________________ 498
Accessories ______________________________________________________ 504
Connector and LED Panels ___________________________________ 504
PX4/PX10/PX20 Expansion Boxes for Modular Hardware __________ 508
AutoBox/Tandem-AutoBox ___________________________________ 512
Link Boards ________________________________________________ 516
DS830 MultiLink Panel ______________________________________ 518
Simulator Hardware _______________________________________________ 520
dSPACE Simulator Mid-Size __________________________________ 520
dSPACE Simulator Full-Size ___________________________________ 524
Simulator Extensions ________________________________________ 529
MicroLabBox Hardware ____________________________________________ 540
MicroLabBox ______________________________________________ 540
MicroAutoBox® Hardware __________________________________________ 548
MicroAutoBox II ____________________________________________ 548
MicroAutoBox Break-Out Box ________________________________ 566
RapidPro Hardware ________________________________________________ 568
RapidPro Hardware Introduction ______________________________ 568
RapidPro SC Unit ___________________________________________ 577
RapidPro Power Unit ________________________________________ 579
RapidPro Control Unit with MPC565 __________________________ 582
RapidPro SC/PS Modules ____________________________________ 585
RapidPro Break-Out Boxes ___________________________________ 590
ECU Interface Hardware ___________________________________________ 592
USB to CAN Converter DCI-CAN1 ____________________________ 592
NEW: USB to CAN/CAN FD Converter DCI-CAN2 ________________ 594
USB to K-Line Interface DCI-Kline1 ____________________________ 596
Generic Serial Interfaces _____________________________________ 598
Additional ECU Interface Solutions ____________________________ 604
6
2016

Contents
Introduction

Engineering 606
dSPACE Engineering Services _______________________________________ 608
Support and Maintenance 614
Application Fields
Support: An Integral Part of the Product ______________________________ 616
Software Maintenance Service (SMS) _________________________________ 616
dSPACE Product Lifecycle Model _____________________________________ 617
Safe Use of dSPACE Products 618
Important Information on Third-Party Brand Names

and Product Names 619
Software

Hardware
Engineering
7
2016

Introduction
dSPACE Systems _______________________ 10
Product Overview ______________________ 14

Introduction / dSPACE Systems
dSPACE Systems
Solutions for embedded software development in automotive, aerospace, and industrial control
Highlights
dSPACE products help you manage the complexity

of today’s embedded software engineering
High software quality, accelerated processes, high

productivity
Mature and reliable tools based on leading-edge

technology and 25+ years of experience
Dedicated support and engineering services available

worldwide
Embedded Control Development

with dSPACE Tools
dSPACE offers you a complete and integrated develop- These include, for example:
ment environment for embedded control software and System and software architecture design
systems. Our tools and systems are convenient to use Rapid control prototyping of new, innovative functions
and will save you valuable development time and money, Automatic production code generation optimized for
whether you apply them throughout the entire process many different embedded targets
or just in individual project phases. dSPACE systems sup- Hardware-in-the-loop (HIL) testing of single and net-
port established development processes, particularly for worked embedded control units
embedded control unit development, also with respect Virtual validation of functions and embedded software
to functional safety requirements, and give you ways to with PC-based simulation, and
adapt your process chains to new challenging needs. With Data management for handling the ever increasing
constant innovations, key technologies and standards, number of models, data, tests, variants, dependencies
and dedicated service and support, dSPACE helps you etc., whether in small or large teams and departments.
achieve long-term success and put your visions into ac-
tion. Together with the MATLAB®/Simulink®/Stateflow® The result: dSPACE systems help you create high-quality
products from MathWorks®, a single, highly integrated embedded systems and products, and support you meet-
tool chain for model-based development is available. ing your target dates. Our systems give you the competitive
dSPACE systems let you perform demanding tasks. edge you need to keep pace with strong market demands.
10
2016

Introduction
dSPACE Product Areas
System Architecture
SystemDesk® simplifies and speeds up the planning, implementation,
Application Fields
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. Easy roundtrip engineering with
the production code generator TargetLink® helps get software designs
into production. You can also use SystemDesk to generate virtual ECUs
(VECUs), including components of the application and basic software.
VECUs enable you to test the system’s overall behavior with the
PCbased simulation platform VEOS®, the hardwareintheloop (HIL)
simulator SCALEXIO® or the rapid control prototyping (RCP) platform
MicroAutoBox® II as soon as the implementation with C code is available.
Relevant products:
Software
SystemDesk
(p. 40) TargetLink
(p. 202)
SystemDesk Modeling Module (p. 43) VEOS
(p. 112)
SystemDesk VECU Generation Module (p. 46)
Rapid Control Prototyping
dSPACE prototyping systems are flexible development platforms that

let you develop and optimize your control designs without manual
Hardware
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.
Relevant products and product groups:

Implementation Software (p. 48)
Engineering

SingleBoard Hardware (p. 356)

ControlDesk® Next Generation (p. 120)

Modular Hardware (p. 372)

TargetLink (p. 202)

MicroLabBox (p. 540)

ECU Interface Software (p. 248)

MicroAutoBox (p. 548)

RapidPro Hardware (p. 568)

ECU Interface Hardware (p. 592)

11
2016

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. Moreover, Functional Mock-up Units (FMUs) can be exported
from TargetLink models for simulation on dSPACE or third-party platforms.
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:
TargetLink (p. 202)
VEOS (p. 112)

Third-Party Tools for TargetLink (p. 241)
SYNECT (p. 292)

Model Compare1) (p. 242)

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 (ASM) 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:

SCALEXIO Hardware (p. 318)
Automotive Simulation Models (p. 258)

Simulator Hardware (p. 520)
Implementation Software (p. 48)

Modular Hardware (p. 372)
VEOS (p. 112)

Experiment and Visualization Software (p. 120)
SYNECT (p. 292)

Test Automation Software (p. 172)

1)
Limited availability outside of Europe and Asia.
12
2016

Introduction
Virtual Validation
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
Application Fields
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.
Relevant products:
VEOS (p. 112)
MicroAutoBox II (p. 548)

TargetLink (p. 202)
ControlDesk Next Generation (p. 120)

SystemDesk (p. 40)
AutomationDesk (p. 172)

Software
SCALEXIO Hardware (p. 318)
Automotive Simulation Models (p. 258)

Data Management
The amount of data produced in electronics and software development

is immense. Managing this data is a growing challenge. The solution
is dSPACE SYNECT, a data management software with a special
focus on modelbased development and ECU testing. SYNECT helps
engineers handle models, signals, parameters, tests, test results, etc., their
Hardware
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 with application/product lifecycle
management systems (ALM/PLM), and supports relevant standards.
Relevant product:
SYNECT (p. 292)

Engineering 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 dSPACE’s 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:
dSPACE Engineering Services (p. 608)

13
2016

Product Overview
Product Overview
Offtheshelf components for every development phase
System Architecture Implementation Software Simulation Software

Software
SystemDesk® ConfigurationDesk® RTI AUTOSAR Blockset VEOS®

Modeling system architecture and Configuration and implementation MATLAB®/Simulink®- and AUTOSAR- Platform for PC-based simulation
generating virtual ECUs software for dSPACE SCALEXIO® based co-development, validation and page 112
page 40 hardware prototyping on MicroAutoBox II
page 48 page 86
SystemDesk RTE Generation
Module NEW: Bus Manager RTI FPGA Programming Blockset
page 41 Configuration for LIN, CAN, and CAN Integrating FPGA models in dSPACE
SystemDesk Modeling Module FD bus simulation systems
page 43 page 54 page 90
SystemDesk V-ECU Generation Real-Time Interface (RTI) Ethernet Blocksets
Module Implementation software for running Connection of dSPACE real-time systems
page 46 models on dSPACE hardware to Ethernet networks and devices
page 56 page 92
RTI for Multiprocessor Systems dSPACE Ethernet Configuration

For graphical setup of multiprocessor Package
structures For simulating Ethernet networks in
page 62 real-time systems
page 96
RTI Bypass Blockset
ECU interfacing for rapid control proto- ADASIS v2 Horizon Reconstructor
typing and intrusive testing of existing Blockset
ECU software Developing and testing map-based
page 64 driver assistance systems using the
ADASIS v2 protocol
RTI CAN Blockset page 98
For combining dSPACE systems with
CAN communication networks NEW: V2X Solution
page 71 Developing and testing V2X applications
page 100
RTI CAN MultiMessage Blockset
For combining dSPACE systems with XSG Utils Library
CAN communication networks Ready-to-use function blocks for faster
page 74 implementation of FPGA models
page 104
RTI LIN MultiMessage Blockset
For combining dSPACE systems with XSG AC Motor Control Library
LIN communication networks FPGA-based control design for
page 77 MicroAutoBox II, MicroLabBox, NEW: Electrical Power Systems
SCALEXIO and PHS-based systems Simulation Package
dSPACE FlexRay Configuration page 106 Easy real-time simulation of power
Package
electronics circuits developed with
Configuring dSPACE systems in NEW: XSG Advanced Engine Control SimPowerSystems™
FlexRay networks Library page 108
page 80 FPGA library for cylinder pressure indica-
tion and in-cycle control of combustion Compilers
engines For translating C code into object code
page 107 page 111
14
2016

Product Overview
Introduction
Experiment and Test Automation Production Code ECU Interface Software
Visualization Software Software Generation Software
Application Fields
ControlDesk® Next Generation AutomationDesk TargetLink® ECU Interface Manager
Universal experiment software for elec- Powerful test authoring and automation Automatic production code generator Bypassing without ECU source code
tronic control unit (ECU) development tool (certified for IEC 61508 and ISO (certified for IEC 61508 and ISO 26262) modifications
page 120 26262) page 202 page 248
Software
page 172
MotionDesk Third-Party Tools for TargetLink dSPACE Calibration and
3-D online animation of simulated Real-Time Testing Complementary products for a model- Bypassing Service
mechanical systems in real time Python-based real-time test automation based development process and tool ECU service for measurement, calibra-
page 156 page 190 chain built around TargetLink tion, bypassing, and ECU flash pro-
page 241 gramming
Platform API Package
page 252
Application programming interfaces for Model Compare1)
connecting to dSPACE platforms Comparison of Simulink®, Stateflow®, dSPACE Internal Bypassing Service
page 196 and TargetLink models Using an existing ECU for function
page 242 development
NEW: Failure Simulation Package
page 253
Application programming interfaces for
accessing dSPACE Failure Insertion Units dSPACE XCP Service
page 198 ECU service for measurement, calibra-
Hardware
tion, bypassing, and ECU flash pro-
gramming via XCP
page 254
Variable Editor
Visualize, edit, and create ECU descrip-
tion files
page 255
dSPACE ECU Flash Programming
Tool
ECU flash programming via measure-
ment and calibration interfaces
page 257
Engineering
15
1)
Limited availability outside of Europe and Asia, please contact dSPACE. 2016

Product Overview
Automotive Simulation Data Management SCALEXIO® Hardware

Models Software
Combustion Engine Simulation SYNECT® SCALEXIO Processing Unit Battery Simulation Controller
Real-time models for diesel and gasoline Data management software for model- x86 processor technology Intel XEON E3 Power supply control for battery
engine simulation based development and ECU testing page 328 simulation
ASM – Gasoline Engine Basic page 292 DS2907, page 350
page 263 I/O
ASM – Diesel/Gasoline Engine SYNECT Test Management MultiCompact unit for powertrain ARINC 429
and vehicle dynamics scenarios Interface Solution for ARINC 429
page 264 page 294
ASM – Diesel/Gasoline Engine SYNECT Signal & Parameter DS2680, page 330 page 351
In-Cylinder Management Digital I/O MIL-STD-1553
page 265 page 299 MultiCompact board for vehicle body Interface Solution for MIL-STD-1553
ASM Turbocharger SYNECT Model Management scenarios page 352
page 266 page 302 DS2690, page 333
ASM Diesel Exhaust System SYNECT Variant Management AFDX®1)
page 267 page 306 FPGA Interface Solution for AFDX®
General SYNECT Functionalities HighFlex board with user-programmable page 353
Electric Components Simulation page 309 FPGA
Real-time models for vehicle electrics DS2655, page 335 PROFIBUS and EtherCAT
and traction system simulation Workflow Management Interface Solution for PROFIBUS and
ASM – Electric Components Handling complex workflows including Multi-I/O EtherCAT
page 269 variants I/O hardware with signal conditioning (SCALEXIO Field Bus Solution)
XSG Electric Components page 312 for automotive systems page 354
page 271 DS6101, page 338
PSI5 Master/Slave Solution
Vehicle Dynamics Simulation Digital I/O page 335
Real-time models for ground vehicle SCALEXIO I/O board with 96 bidirec-
simulation tional digital I/O channels
ASM – Vehicle Dynamics DS6201, page 340
page 273
ASM Truck Signal Measurement
page 275 HighFlex board for measuring ECU
ASM Trailer output signals
ASM Pneumatics
Signal Generation
page 278 HighFlex I/O board for simulating ECU
ASM Brake Hydraulics
input signals
Traffic Simulation FIU & Power Switch
Real-time models for traffic and envi- HighFlex board for power-switching
ronment simulation with Failure Insertion Unit
ASM Traffic
DS2642, page 346
page 280
Bus Interfaces
ModelDesk
HighFlex board for interfacing to
Graphical user interface for Automotive
different bus systems
Simulation Models (ASM)
DS2671, page 348
page 283
16 1)
AFDX® is a registered trademark of Airbus
2016

Product Overview
Introduction
Single-Board Hardware Modular Hardware Modular Hardware I/O Boards (1)
Processor Boards
Application Fields
PowerPC and I/O PowerPC Multi-Channel A/D Resistive Sensor Simulation
PPC750GX, 20 x A/D, 8 x D/A, PPC750GX, 1 GHz 32 x 16 bit, MUX, 2 independent ADCs 4 resistance output channels
digital I/O, CAN interface, DS1005, page 376 DS2002, page 390 (10 Ω - 500 kΩ)
and more DS2401, page 422
Software
DS1103, page 358 X86 Processor Technology Multi-Channel A/D
Quad-Core AMD OpteronTM 32 x 16 bit, MUX, 2 independent ADCs Incremental Encoder Interfaces
PowerPC and I/O processor, 2.8 GHz DS2003, page 390 5 or 6 channels,
PowerPC 603e, 8 x A/D, 8 x D/A, DS1006, page 380 digital or sinusoidal signals
digital I/O, and more High-Speed A/D DS3001/2, page 424
DS1104, page 364 Dual-Core Real-Time Processor 16 x 16 bit, 16 independent ADCs,
Freescale QorlQ P5020, dual-core, 2 GHz 800 ns conversion time, Timing and Digital I/O
Panels DS1007, page 386 4 external trigger inputs 8 timing channels, 200 ns resolution,
Connector and LED panels DS2004, page 396 32 dig. I/O
D/A
Demo Equipment 5 x 12 bit Digital I/O
Hardware and software for demon- DS2101, page 399 96 x dig. I/O
strating single-board hardware DS4003, page 433
page 371 High-Resolution D/A
Hardware
6 x 16 bit Digital I/O
DS2102, page 399 96 x dig. I/O with general signal condi-
tioning up to 60 V
Multi-Channel D/A DS4004, page 434
32 x 14 bit
DS2103, page 399 ECU Interface
Interface to electronic control units
HIL I/O DS4121, page 436
16 x 14 bit (A/D), 20 x 12 bit (D/A),
signal conditioning Prototyping Board
DS2202, page 406 Integration of customized circuits
DS4201, page 440
HIL I/O
16 x 14 bit (A/D), 20 x 12 bit (D/A), Serial Interface
4 channels for serial communication
Engineering
sensor signal generation, angle-
synchronous signals, and more DS4201-S, page 441
DS2211, page 410 CAN Interface
Direct Digital Synthesis Interface to CAN bus
6 x VC33 DSP and 16-bit DACs, DS4302, page 442
36 digital I/O
LIN Interface
DS2302, page 416 Interface to LIN bus
DS4330, page 445
FlexRay and CAN FD Interface
Interface to FlexRay or CAN FD
DS4505, page 448
17
2016

Product Overview
Modular Hardware I/O Boards (2) Accessories Simulator Hardware
Digital Waveform Capture Position Sensor Simulation Panels dSPACE Simulator Mid-Size
16 channels, 25 ns resolution Solution Connector and LED panels System for ECU/controller testing
DS5001, page 452 Simulation of position sensors page 504 page 520
page 480
Digital Waveform Output Expansion Boxes dSPACE Simulator Full-Size
16 channels, 25 ns resolution AC Motor Control Solution Space for 3, 9 or 19 dSPACE boards System for ECU/controller testing
DS5101, page 456 Control of diverse AC motors PX4, PX10, PX20 page 524
page 484 page 508
FPGA Board Simulator Extensions
FPGA programmable per EMH Solution AutoBox/Tandem-AutoBox Power switch, CAN gateway, bus FIU,
application Electric motor simulation For in-vehicle experiments, electronic load modules, custom
DS5203, page 462 page 488 space for 3 or 13 dSPACE boards adaptation, break-out boxes
page 512 page 529
SCRAMNet+ Interface EtherCAT Slave Interface
Interface to SCRAMNet+ networks Slave interface to an EtherCAT Link Boards
page 466 communication bus Connecting a host PC with
page 494 dSPACE systems
PROFIBUS Interface page 516
Interface to a PROFIBUS Ethernet Interface (100 Mbit/s)
communication bus Interface to an Ethernet network MultiLink Panel
page 468 page 496 Connection of several systems
to one host PC
MIL-STD-1553 Additional I/O Solutions DS830, page 518
Interface to MIL-STD-1553 networks I/O to your specifications
page 470 page 498
ARINC 429 Interface
Interface to the ARINC 429 avionics
data bus
page 472
ARINC 717 Interface
Interface to the ARINC 717 avionics
data bus
page 474
FPGA Base Board
For high-resolution signal
preprocessing
page 476
PWM Measurement Solution
High-precision digital capturing of
3-phase PWM signals
page 478
18
2016

Product Overview
Introduction
MicroLabBox Hardware MicroAutoBox® Hardware RapidPro Hardware ECU Interface Hardware
Application Fields
MicroLabBox MicroAutoBox II RapidPro SC Unit DCI-CAN1
Compact prototyping unit for the Robust and compact stand-alone Flexible signal Robust and compact USB-to-CAN
laboratory prototyping unit conditioning unit gateway
page 540 page 548 page 577 page 592
Software
MicroAutoBox Break-Out Box RapidPro Power Unit NEW: DCI-CAN2
Desktop connection panel for Flexible power stage unit Robust and compact USB-to-CAN/
MicroAutoBox II page 579 CAN FD gateway
page 566 page 594
RapidPro Control Unit with
MPC565 DCI-KLine1
Intelligent I/O subsystem for dSPACE Robust and compact USB-to-K-Line
prototyping systems interface
page 582 page 596
RapidPro SC/PS Modules Generic Serial Interfaces

Signal conditioning and power stage Function bypassing, measurement, ECU
modules for RapidPro units calibration and flash programming
page 585 page 598
Hardware
RapidPro Break-Out Boxes Additional ECU Interface Solutions
Desktop connection panels for Customer-specific DPMEM PODs and
RapidPro systems on-chip debugging interfaces
page 590 page 604
Engineering
19
2016

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
Well-Proven, Integrated Development Systems

In today’s fast moving, competitive automobile electronics partner, dSPACE has done pioneering work on tools for
world, efficiency, productivity and innovation are key. electronic control unit (ECU) development, and cooperates
Product life cycles are getting shorter. Higher expectations closely with the automotive industry. dSPACE supports all
regarding safety, comfort, and environmental compatibil- the development phases with its products, from architec-
ity are rapidly pushing up the complexity of electronic ture-based system design and block-diagram-based func-
systems. Many automotive manufacturers and suppliers tion prototyping to ECU autocoding, virtual validation, and
have realized that well-proven, integrated development HIL testing, and also offers powerful data management
systems which support industry standards, and a modern software. The advantages for automotive customers: con-
model-based development process can improve hand-off siderable savings in time and cost, greatly enhanced soft-
between the development phases and shorten them. By ware quality, and more efficient cooperation between
this means, enormous manual workloads can be reduced manufacturer and supplier.
and expensive mistakes avoided. As an independent system
A Diversity of Application Fields

dSPACE systems are being used successfully at interna- autonomous driving, comfort electronics, interior systems,
tional automotive customers for developing and testing infotainment, noise cancelation, ECU diagnostics, etc. Our
embedded electronics in fields such as engine control, customers use controllers developed with dSPACE tools in
powertrain control (including hybrid drive technologies and vehicles such as passenger cars, motorbikes, racing cars,
electric drives), vehicle dynamics (e.g., ESP, damping control), and commercial vehicles (p. 28) like trucks, buses, and off-
driver assistance systems (e.g., adaptive cruise control, au- highway vehicles.
tomatic emergency braking, and lane departure warning),
22
2016

Introduction
Application Examples1) (1)
Examples Application Details
Hybrid Drive (I) HIL

simulation for a hybridized High
complexity of networked electronic systems
powertrain dSPACE
Simulators for functionality verification and quality assurance
Automotive Simulation Models (ASM) for simulating the electric

components
Application Fields
Hybrid Drive (II) Rapid
control prototyping and Hybrid
demo vehicle with dSPACE prototyping system
production code generation for a MicroAutoBox®
and RapidPro control hybrid components
hybrid SUV TargetLink® for production code generation

Drivetrain ECUs/ AUTOSAR-compliant

production Engine
ECUs supporting functions for combustion engines, hybrid
AUTOSAR software controllers, and transmission applications
AUTOSAR tool chain using SystemDesk® and Targetlink®

Electric Vehicle Developing

a new electric vehicle Ensuring
the quality of the control software using dSPACE Simulator
for rigorous testing, while cutting the time-to-market
Test automation with AutomationDesk

Battery Testing
Li-ion battery BMS
requirements according to ISO 26262
Software
Management management systems Precise
simulation of Li-Ion battery cells in real-time with dSPACE
System (I) Simulator
Battery Developing
an efficient battery Battery
ECU: focus on electric and thermal protection
Management management system for a hybrid TargetLink
used to generate the ECU software
System (II) vehicle
Active Seat Belts Pre-pretensioner

for seat belts Controllers
use AUTOSAR-compliant software
for optimizing belt impact Seat
belt tightened electrically
SystemDesk and TargetLink used

Steering Systems/ ISO-26262-compliant functional Validating electrically powered steering systems
Hardware

HIL Test Benches validation HIL
test benches based on dSPACE Simulator and Automotive
Simulation Models (ASM)
SYNECT® for bridging the gap between requirements management

and testing
Engineering
1)
Short selection of examples. Numerous application examples from customers, including detailed descriptions and pictures, 23
can be found on www.dspace.com and in the printed issues of dSPACE Magazine (formerly dSPACE NEWS). 2016

Application Examples1) (2)

Video-based Driver Developing

and testing lane MicroAutoBox
II with integrated Embedded PC for image processing
Assistance Systems departure warning systems, using OpenCV (Open Source Computer Vision)
emergency steer and brake Validation of camerabased applications in a virtual traffic

assistants that use video data environment using ASM, ModelDesk, and MotionDesk in connection
and sensor fusion with VEOS® and dSPACE HIL simulators
Smart Adaptive Developing

predictive control ASM
for traffic simulation with MATLAB/Simulink
Cruise Control strategies in a simulation ModelDesk
for creating road networks and traffic scenarios, and
environment for Adaptive Cruise MotionDesk for visualizing driving maneuvers via realtime 3D animation
Control (ACC) Interface to the electronic horizon via ADASIS v2 Horizon

Reconstructor Blockset
AUTOSAR Software Developing AUTOSAR

software TargetLink
for generating the production code for AUTOSAR software
Development by using the dSPACE tool chain components
SystemDesk for generating virtual ECUs

VEOS for validating virtual ECUs

Window Control Developing

new power window Goal: maximum
protection against power window injuries
control algorithms dSPACE
prototyping system and TargetLink used
Lighting Developing
automatic vertical Functional
tests of ECU and stepper motors via HIL simulation with
aim control systems and dSPACE realtime hardware
advanced frontlighting systems
Motorcycle Developing
and testing vehicle Rapid
control prototyping for vehicle dynamics functions on
Development/ dynamics controllers on production ECUs
On-Target motorcycles Ontarget prototyping based on the dSPACE ECU Interface Manager

Prototyping and the RTI Bypass Blockset
Reduced verification effort and a shorter verification phase

24 1)
Short selection of examples. Numerous application examples from customers, including detailed descriptions and pictures,
2016 can be found on www.dspace.com and in the printed issues of dSPACE Magazine (formerly dSPACE NEWS).

Introduction
Standards
Standard dSPACE Products Supporting the Standard
ADASIS www.ertico.com/adasisforum
ADASIS
v2 Horizon Reconstructor Blockset (p. 98)
ASAM www.asam.net
SystemDesk®
(p. 40)
RTI
Bypass Blockset (p. 64)
dSPACE FlexRayConfiguration Package (p. 80)

Application Fields
dSPACE Ethernet Configuration Package (p. 96)

Platform API Package (p. 196)
TargetLink® (p. 202)
Variable Editor (p. 255)
dSPACE ECU Flash Programming Tool (p. 257)
dSPACE XCP Service (p. 254)
AUTOSAR www.autosar.org
SystemDesk®
(p. 40)
VEOS®
(p. 112)
RTI AUTOSAR Blockset (p. 86)

TargetLink (p. 202)
Software

ETSI ITS www.etsi.org

NEW: V2X
Solution (p. 100)
(Intelligent
Transport Systems)
FlexRay www.iso.org
RTI
Bypass Blockset (p. 64)
ControlDesk®
Next Generation (p. 120)
DS2671 Bus Board (SCALEXIO®) (p. 348)

DS4505 Interface Board (p. 448)

MicroAutoBox® II (p. 548)

DS1450 Bus FIU Board (p. 532)
Hardware

FMI www.fmi-standard.org
VEOS
(p. 112)
(Functional Mock-up SYNECT® (p. 292, 302)

Interface) SCALEXIO®
(p. 318)
TargetLink
(p. 202)
ISO 26262 www.iso.org

AutomationDesk
(p. 172)
TargetLink
(p. 202)
SCALEXIO (p. 318)

dSPACE Simulator (p. 520)

Engineering
25
2016

Application Fields / Aerospace Industry
Aerospace Industry
The challenge of control system development
Efficiency and Reliability Suitable for Numerous Application Scenarios

The aerospace industry has some of the most rigorous The bandwidth of possible application scenarios for dSPACE
standards and regulations of any field – including the design products for the aerospace industry is very broad. You can
of electronic control systems. Developing such systems is a use dSPACE products for applications such as aircraft control-
high percentage of the overall cost. So efficiency is key. This ler design (FADECs, thrust reverser, cabin pressure control,
is why dSPACE prototyping systems, automatic code gen- etc.), for integration and test facilities (ITF), for helicopter
eration, and hardware-in-the-loop systems are used in applications, for civil or for defence aviation, for commercial
numerous applications throughout the aerospace industry. or scientific puposes: dSPACE products can accelerate your
dSPACE systems speed up the individual development development process and help you improve the quality of
phases and improve hand-off between them. Whether you your control software.
use dSPACE systems throughout the entire development
or at individual stages, you can rely on them to make a real Satellite Simulation Models
impact on the efficiency of your development cycle. ASM Satellite provides ECSS-compliant satellite models
DO-178C workflow document for TargetLink® based on Simulink® for simulating the attitudes and orbits
available (p. 239) of LEO, MEO and GEO satellites with high precision.
Aerospace-Specific Bus Interfaces

dSPACE offers special interface boards and software support The MicroAutoBox II can be equipped with an ARINC inter-
(via RTI blocksets and ConfigurationDesk) for connecting face on its IP module slot by dSPACE Engineering Services.
modular dSPACE real-time systems and SCALEXIO® to aero- MicroAutoBox II (p. 548)
space bus systems: dSPACE Engineering Services (p. 608)
MIL-STD-1553 (p. 352, p. 470)
ARINC 429 (p. 351, p. 472) Extended Visualization
ARINC 717 (p. 474) For additional visualization (out-the-window view) dur-
AFDX®1) (p. 353) ing the real-time simulation, dSPACE offers integration
with the X-Plane® flight simulator.
26
2016
1)
AFDX® is a registered trademark of Airbus.

Application Fields / Aerospace Industry
Introduction
Application Examples1)
Emergency Power Developing

a fuel-cell-based Fuel-cell-based
electricity independent of flight situation
System aircraft emergency power system Developed
with dSPACE prototyping system
Cabin Pressure Developing

cabin pressure Autocoded
software fulfils the strict requirements of aircraft
Control controls for a wide range of manufacturers and aviation authorities
Application Fields
aircraft types Automatic code generation with TargetLink according to safety

standard DO-178B level A
Simulating Satellite Simulating

the relative Testing
flight systems and studying the interaction of satellites and
Rendezvous navigation of two satellites for robots
tasks such as capturing disused dSPACE system used as the core of the hardware-in-the-loop

satellites simulation system
Satellites‘ real sensors used

Unmanned Aerial Subscale

UAV for test flights Study
of extreme flight situations
Vehicle (UAV) under extreme conditions dSPACE
system used as flight control computer (communication
via radio)
Complex real-time computations during test flights

Software
Electric Thrust First
fully electric thrust reverser Thrust
reverser integrated into major wide-body aircraft type
Reverser in commercial aviation Controller
developed using a dSPACE prototyping system according
to safety standard DO-178B level A
Integration and Evaluating

all systems integration Aircraft
systems hardware and software interconnected with actual
Test Facility (ITF) for a business aircraft with an aircraft electrical harnesses
advanced integration and test Real-time tests and simulation supported by dSPACE real-time

facility, also using dSPACE tools hardware and I/O
Sensor-Based Testing
landing aid algorithms for Sensor-based
landing aid with the help of dust-penetrating radar
Hardware
Landing Aid for enhanced safety of helicopter sensors to display the helicopter‘s position above ground
Helicopters missions under poor vision Tests with dSPACE Simulator and AutomationDesk

conditions (dust, sand, snow) Runnig the algorithms on a MicroAutoBox® in a flight simulator

Engineering
1)

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 they command far higher prices. As a consequence, both
electronics to optimize and expand the performance of the development process and the development tools in
applications for trucks, buses, and off-highway vehicles. the commercial vehicles industry have to be enormously
Efficiency, productivity, and innovation are key in today’s efficient and flexible to master cost and development time,
vehicle electronics world. New technologies such as hybrid and to handle variants and integration tasks. To be
drives are gaining momentum, and constant innovation equipped for the challenges, you need a partner that can
and optimization is necessary for control algorithms in provide you with a well-proven, highly efficient develop-
fields such as engine and powertrain, active and passive ment environment: dSPACE. We will support you from
safety, and special equipment. At the same time, ECU beginning to end, giving you proven, flexible, perfectly
software is becoming more complex, and numerous com- integrated solutions from a single source. dSPACE supports
ponents from suppliers have to be integrated into vehicles. all the development phases, from architecture-based sys-
Moreover, as a commercial vehicles manufacturer, you tem design and block-diagram-based function prototyping
usually have to handle numerous variants and custom to ECU autocoding, HIL testing/virtual vehicles, virtual
requirements. All this adds up to enormous complexity validation, and data management. dSPACE‘s products and
and diversity. And commercial vehicles are usually pro- development teams are in constant demand by many
duced in smaller quantities than passenger cars, though major commercial vehicle manufacturers and suppliers.
28
2016

Application Fields / Commercial & OffHighway Vehicles
Introduction
Virtual Bus Verifying

the maturity of a new Early
virtual test drives made possible by smooth interaction between
bus electrics/electronics archi the environment model and dSPACE Simulators
tecture with HIL integration tests Frontloading error detection in the testing process shortens

development and test times
Heavy Duty
Application Fields
HIL
and SIL tests for heavyduty ASM
diesel engine model and physical turbocharger model for testing
Equipment equipment with dSPACE the engine ECU of heavy duty equipment, combined with customized
Automotive Simulation Models drivetrain model
(ASM) Testing laboratory with numerous HIL test benches from dSPACE

Diesel Injection Electronic

control unit for diesel Focus
on improving injection and combustion processes and
Systems engines considerably reducing fuel consumption and exhaust emissions
TargetLink® for complex control functions

Hybrid Drive for Developing

a wheel loader with By
reducing fuel consumption, the hybrid drive lowers CO2 emissions
Wheel Loader a hybrid drive and provides considerable cost savings
Complete Truck Testing

complete truck electronics Customer
tested 33 networked ECUs with dSPACE Simulator
Software
Electronic Tests dSPACE ASM
for variant handling
Automated testing with virtual rebuild of buses and trucks

Agricultural Developing
transmission control TargetLink
boosts coding speed like an additional programmer
Equipment algorithms and further functio Requirements
with respect to code quality, readability and integration
nalities for farm tractors and capability were fully met
harvesters
Hardware
Engineering
1)

Application Fields / Electric Drives
Electric Drives
Efficient controller development
Driving for Precision

Electric drives have been used increasingly over the past few to power on demand, better controllability, and easier main-
years. Not only in drive and automation technologies, but tenance. dSPACE provides exactly the right products and
also in vehicles. They have numerous advantages and wide- solutions for simulating electric drives, and for developing
ranging application potential in many areas. Electric motors and testing their servos or control units. From flexible dSPACE
can be very small and fit almost anywhere. They have very development systems and special hardware and software for
high dynamics and can provide high torque at lower rota- electric drives to building complete systems, dSPACE will
tional speed. Other reasons are improved energy saving due accelerate your drive to the future.
Electric Motors for Automotive Applications Electric Motors for Non-Automotive Applications
In automotive applications, electric drives are increasingly Electric motors are also in widespread use in the capital
being incorporated into several complex, basic, and safety- goods industry, medical technology, and aerospace sector.
relevant vehicle functions. dSPACE products can accelerate Applications for dSPACE products in non-automotive control
the ECU software development for electric drive applications software development include wind energy converters, elec-
in many scenarios, such as for mild-/full hybrid cars, electric tric trains, printing machines, medical equipment, robots etc.
vehicles, electric brake systems, powertrain actuators, electric
power steering (EPS), auxiliary aggregates (oil pump, water
pump) etc.
30
2016

Application Fields / Electric Drives
Introduction
Servocontrollers Automated
software tests on a High
number of controller variants
in Industrial HIL simulator Uses
dSPACE Simulator including EMH Solution and ControlDesk®
Automation with Python scripts
Simulation model based on the ASM Electric Components Library

Application Fields
Mild Hybrid Car 48 V
belt-driven starter generator dSPACE
HIL systems for developing and testing the mild hybrid ECU
using an asynchronous machine The
systems use the DS5203 FPGA Board, the ASM XSG Electric
Components Library, and the XSG Utils Library.
Exact simulation of the induction machine

Instrumentation with ControlDesk Next Generation

Virtual Vehicle Test

system for over 20 Real-time
execution of Automotive Simulation Models (ASM) with a
networked ECUs and various network simulator
electric drives Function and diagnostic tests including random tests integrated into

test automation
Electric Vehicle Studying

control algorithms for Development
objective: a yaw-stable vehicle
electric vehicles In-wheel
motor technology
Software
Test drive with dSPACE hardware for fast algorithm calculation

dSPACE hardware drives the electric motors via converters

Mechatronic HIL
test system for steering Simulation
model provides features such as automatic parking and
Test Bench systems with optic feedback for lane-keeping assistants for enhancing comfort and active safety
Integration a realistic drive feeling HIL system and driving simulator use dSPACE ASMs, visualization is

performed by dSPACE MotionDesk
Successfully runs driver assistance systems

Electric Wedge Validating

a new wedge clutch Control
of the electric actuator executed on MicroAutoBox® II
Clutch concept on the test bench during tests
Hardware
Test environment user interface realized with ControlDesk Next

Generation
Permanent Magnet Real-time

modeling using FPGA- HIL
bench to emulate a permanent magnet electrical machine for
Electrical Machine based technology ECU functional validation
Simulation of electric motors with the ASM XSG Electric Component

Library and dSPACE Modular Hardware
For battery management application examples, please see p. 23
Engineering
1)

Application Fields / Medical Engineering
Medical Engineering
Control development for medical applications
Safe, Fast Development From Early Concept to Volume Production

Safety and reliability are the top priorities in medical engineer- dSPACE tools support all stages of model-based development
ing – and also a major challenge with the increasing complex- by integrating the MATLAB®/Simulink® environment:
ity brought by innovative procedures and combinations of Medical device design: Using dSPACE off-the-shelf
medical devices. The solution comes from reliable, sophisti- hardware components ensures efficient development
cated development tools, that support your process even of algorithms and controller functions. Medical devices
while minimizing the time and cost of your projects. can be validated at an early stage without expensive
dSPACE products enable the manufacturers of electronic and time-consuming in-house developments.
controls and control units to dramatically cut their develop- Automatic code generation: Target code is generated
ment times and costs, and systematically increase their pro- straight from your verified function models with no
ductivity. manual programming, ensuring consistency between
model and code. Different simulation options support
Tools with Years of Engineering Success the verification process from the model level early in
dSPACE products have proven to be valuable tools in the field the development process to the final code.
of medical engineering in many ways (see also p. 33). They Medical device tests: Single software functions or
have also played an important role in the automotive and whole medical devices are tested automatically in a
aerospace industries, as well as in mechatronic projects in simulated environment and with various test scenarios.
other industrial and academic fields, for many years.
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.
dSPACE Systems (p. 10)

Certification for developing safety-critical systems

(p. 238)
32
2016

Application Fields / Medical Engineering
Introduction
Artificial Neural
impulse measurement for Artificial
ventilation uses neural impulses to respond early to the
Respiration more comfortable artificial patient’s breath initiation
respiration DS1005, DS2002, DS2102 used for simulation and signal

measurement, and ControlDesk® for experiment control
Impedance Experimental
Application Fields
system helps to dSPACE
prototyping system and bypass techniques mimic a pacemaker
Sensor for Heart patent an impedance sensor for Replay
program for automated testing
Pacemaker blood flow measurement through
the heart
Blood Pump Developing

a controller that Mini-turbine
for cardiac assistance
Control continuously adjusts the output Automatic
speed control with a dSPACE prototyping system
of a blood pump to the patient’s
needs
Safe Surgical Semiautomatic

surgical saw for Avoiding
trauma to soft tissue adjacent to bones
Instruments safe sectioning of bones Intelligent, sensor-based
incision depth control
dSPACE real-time system for overall control

Software
Medical Training Childbirth
simulator for training Practicing
diagnostic and therapeutic manipulations safely with a
Equipment obstetricians and residents childbirth simulator
(robotic medical research project) ControlDesk used for configuration and MotionDesk for visualization

Prosthetic Wrist Prosthetic

wrist development for Wrist
simulator controlled by a dSPACE prototyping system for
more successful wrist replace- functional testing and comparative assessment of wrist prostheses
ment surgery
Hardware
Engineering
1)

Application Fields / Research and Education
Research and Education

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

dSPACE offers universities and research institutes flexible For universities and academic research facilities, dSPACE
systems with all the options needed for the model-based offers attractive packages of its groundbreaking products
development of mechatronic controls. dSPACE has pioneered for model-based development and mechatronic controls
and optimized tools for controller development for many testing. The price of each package is much lower than the
years as an independent system partner. Cooperating closely total for all its individual components. The different hard-
with the industry, we have created a comprehensive develop- ware and software packages let universities introduce their
ment environment that has become a standard in many students early on to the established dSPACE development
companies. dSPACE supports all the development phases, environment:
from architecture-based system design and block-diagram- Test even the most complex control in real time
based function prototyping to autocoding and HIL testing. Demonstrate high-end control development –
from block diagram design to online controller
optimization
MicroLabBox – Compact Power in the Lab Let your students gain experience with control
Discover the MicroLabBox, a compact all-in-one proto- development tools
typing system for the laboratory. It combines compact Work under easy-to-use, intuitive Windows® interfaces
size and cost-effectiveness with high performance and Implement your Simulink models on real-time hardware
versatility. within seconds
Read more on p. 540, Observe the effects of parameter changes on your
or have a look at the video: system‘s behavior
www.dspace.com/go/c2016_mlbxvideo
34
2016

Application Fields / Research and Education
Introduction
Re-Engineered Implementing
vehicle energy Testing
new control code while designing mechanical/electrical
Plug-In Hybrid storage and technology for electric subsystems at the same time
drives and ethanol-fueled engines Comprehensive dSPACE tool chain with SYNECT®, AutomationDesk,

ASM, dSPACE Simulator, ControlDesk® Next Generation,
and MicroAutoBox®
Application Fields
SYNECT as the key tool in automated testing

Gravitational Wave Gravitational

wave research with Researchers
have set up an observatory dedicated to detecting
Research dSPACE equipment gravitational waves
dSPACE equipment helps to eliminate seismic noise

Miniature Robot Miniature

robot for precision Control
via dSPACE prototyping system
assembly Positioning
workpieces at a repeat accuracy of under 10 μm
Test Bench for University

students constructed Control
function development with dSPACE tools
3-Phase Induction their own test bench for 3-phase Test
bench playing a key role in the transfer of rapid control
Motors induction motors prototyping technology between the university and industry
Software
High-Speed Robots Developing
new robots for high- Evaluating
sensor and camera signals for robot control
speed manipulation tasks dSPACE
modular hardware used for setting up a robust, high-
performance real-time system
Intelligent Flying Unmanned

aerial vehicle (UAV) Test
environment based on hardware-in-the-loop (HIL) test equipment
System that flies autonomously Developing
subsystems for communication between the UAV and
the ground station
Nanopositioning Developing
nanopositioning Positioning
processes controlled by a DS1006 Processor Board and
Machine machines with dSPACE tools various dSPACE I/O boards
Positioning precision: 1 nm in a 200 x 200 x 25 mm positioning range

Hardware
Engineering
35
1)
can be found on www.dspace.com and in the printed issues of dSPACE Magazine (formerly dSPACE NEWS).

Application Fields / Other Fields
Other Fields
The challenge of streamlined control development
Cutting-Edge Technology Accelerated Control Development

Wherever mechatronic control systems are used – in drives, Well-proven development methods have become the stan-
industrial automation, medical applications, and others – dard in controller development: rapid control prototyping
controllers have to perform ever more complex tasks. with a dSPACE prototyping system, automatic code genera-
Manufacturers have realized that the gap between increasing tion with TargetLink®, and hardware-in-the-loop testing with
complexity and shorter development times can only be dSPACE HIL systems. As a user of dSPACE systems, you will
closed by optimizing and parallelizing the development find the same familiar working environment for developing,
tasks. dSPACE provides a complete and seamless develop- programming and testing control systems. The result is an
ment process with user-oriented products. accelerated and simplified development process that helps
you put your ideas into practice faster and eliminate errors
sooner.
36
2016

Application Fields / Other Fields
Introduction
Regenerative Testing
regenerative energy Developing
the converter control
Energy supplies (wind and solar) in the Simulating
load conditions, wind strength, and solar radiation
megawatt range Uses dSPACE prototyping system including the AC Motor Control

Solution
Application Fields
Adaptive Ultra- Active
vibration control for Adaptive
loadbearing shell
Lightweight buildings Reduces
duration of vibration by 80 %
Structures Uses dSPACE prototyping system

Traction Control for Speeding

up traction control unit Number
of power test bench runs reduced by using dSPACE HIL
Railways development for AC electric system in a very early development stage
locomotives Using the DS5203 FPGA‘s fast computing feature for a highprecision

traction control simulation
Gas Turbine Ship Testing

the control software of a dSPACE
HIL system enables tough gas turbine ECU specifications to
Propulsion gas turbine propulsion system be met
Testing emergency shutdown and warning functions without

operating the turbine
Software
Personal New
personal transportation Developing
and testing control functions by using dSPACE proto
Transportation system uses MicroAutoBox as an typing systems
System onboard control unit MicroAutoBox® has a new job as a regular onboard control unit

Self-Navigating Developing
a selfnavigating Unmanned
marine vehicle for carrying out numerous measurement
Research Boat research boat with MicroAutoBox and observation tasks
on board MicroAutoBox performs all the tasks involved in navigating and

steering the vehicle
Beverage Filling Simulation

environment for dSPACE
HIL system for testing a programmable logic controller (PLC)
Hardware
Machines testing process control software reliably under the conditions of a simulated plant and for boosting
machine efficiency
Engineering
1)

Software
System Architecture Software ______________ 40
Implementation Software ________________ 48
Simulation Software ___________________ 112
Experiment and Visualization Software ______ 120
Test Automation Software _______________ 172
Production Code Generation Software ______ 202
ECU Interface Software _________________ 248
Real-Time Models _____________________ 258
Data Management Software _____________ 292

System Architecture Software / SystemDesk
SystemDesk®
Modeling system architecture and generating virtual ECUs
Highlights
ECU software architecture and system development for

AUTOSAR R3 and R4
Efficient modeling including plausibility checks and

correction suggestions
Quick and easy generation of virtual ECUs for early

validation with VEOS®, SCALEXIO® or MicroAutoBox II
Coupling with TargetLink® for function development

Complete and documented API for automation

Application Areas Key Benefits

SystemDesk is a system architecture tool that provides so- Efficient use due to convenient dialogs, editors, and

phisticated and extensive support for modeling AUTOSAR graphical diagrams
architectures and systems for application software. Com- Easy-to-use tool even for beginners of AUTOSAR

prehensive graphical support facilitates the first use but Easy and fast generation of virtual ECUs for validation

also enables efficient and error-reduced working during purposes
large-scale projects. Reliable project quality through comprehensive

Additionally SystemDesk makes validating ECU application rule-based validation of consistency and correctness
software possible at an early development stage. Therefore, Convenient development process due to automation

virtual ECUs (V-ECUs) are generated out of the application of recurring tasks or remote control by third-party tools
software and used as units under test with the dSPACE simu- via the automation API
lation platforms, such as the PC-based simulation platform
VEOS (p. 112) for validating the ECU software.
Two SystemDesk Versions for AUTOSAR

Because SystemDesk is an AUTOSAR tool, it supports all cur- SystemDesk 4.5 supports AUTOSAR R4.x projects, and Sys-
rent AUTOSAR versions and new versions are implemented temDesk 3.2 supports projects based on AUTOSAR R3.x.
continuously. Due to the considerable differences between
the latest AUTOSAR releases R3 and R4, SystemDesk is avail- For more details on the two versions, please see the table
able in two major versions to give both AUTOSAR versions on page 41.
comprehensive support.
40
2016

Introduction
Functionality Overview
Functionality Description
AUTOSAR modeling Modeling of software architectures and systems according to the AUTOSAR standard

Clear overview due to graphical modeling with diagrams

Sophisticated editors and dialogs for easy and faultless data entry

Data exchange: flexible and easy-to-configure import and export of ARXML files
Application Fields

Complete support of AUTOSAR meta model1)

Import of communication matrices (DBC, LDF, FIBEX)

V-ECU generation Generation of virtual ECUs for simulation with VEOS, SCALEXIO, and MicroAutoBox II

Mostly automatic configuration and generation of required basic software modules according the system

requirements
Partial configuration of basic software (such as COM)

Process support Comprehensive, rule-based validation of the system architecture and ECU software regarding consistency,

correctness, and completeness
Easy data exchange with dSPACE’s code generator TargetLink

Coupleable with every AUTOSAR-compliant basic software configuration tool

Completely documented automation API for automating tasks such as report generation, software

architecture creation and automatic V-ECU generation
Software
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
Product Description SystemDesk 4.x SystemDesk 3.x Order Number

SystemDesk Modeling Module Modeling AUTOSAR compositions and systems
  SYD_MOD

(p. 43) containing one or more networked AUTOSAR ECUs
Hardware
SystemDesk V-ECU Generation Generating virtual ECUs (V-ECUs) including  Add-on for SYD_GEN

Module (p. 46) nonoptimized RTE SystemDesk
Building simulation systems for offline simulation Modeling Module
with VEOS
SystemDesk RTE Generation Generating optimized RTE production code – Add-on for SYD_RTE

Module SystemDesk
Modeling Module
Relevant Software
Engineering
Product Description Order Number
TargetLink Production code generation
See p. 202
Integration of models, functions, and production code in software components and

architectures designed in SystemDesk
VEOS Offline simulation of virtual ECUs
See p. 112
Offline simulation of Simulink plant models together with virtual ECUs from SystemDesk

41
2016

Working with SystemDesk

SystemDesk supports your development process with
numerous features for intuitive working:
AUTOSAR-Compliant Modeling
Project Validation

Use SystemDesk’s authoring capabilities to create and edit Use SystemDesk’s validation to ensure that your AUTOSAR
software architecture and system descriptions according to architecture is complete and consistent before giving it to
the AUTOSAR standard. a project partner for BSW configuration and before gener-
ating a V-ECU – save time by finding problems as early as
Generation of Virtual ECUs for Simulation
possible. You can define your own custom validation rules
Use SystemDesk to generate virtual ECUs (V-ECUs) that to also check for company-specific project requirements.
include basic software modules to get a realistic represen-
tation of the real ECU. Simulate the V-ECU with VEOS (p. Complete and Documented Tool API

112), SCALEXIO® (p. 318) or MicroAutoBox II (p. 548) to Use the open tool API to automate recurring design tasks
validate your software when a hardware prototype is not and extend the features of SystemDesk according to project-
available (yet). specific requirements or even use it to create a completely
automated tool chain for V-ECU generation.
Dialogs and Diagrams

For an easy and efficient capture and configuration of com- Import and Export of AUTOSAR Files

mon AUTOSAR data, SystemDesk offers convenient, pre- SystemDesk offers comprehensive features for importing
configured dialogs. Additionally special diagrams of the and exporting AUTOSAR files. You can flexibly configure
software architecture and system elements help to keep an the data to be included in each individual project. Import
overview over your model. and export are done with just a few clicks.
Connecting and using configuration and version manage-
Data Exchange with TargetLink
ment tools with SystemDesk is made easy with special im-
You can exchange data seamlessly between SystemDesk and port and export options.
dSPACE's production code generator TargetLink (p. 202).
This gives you a safe process in a model-based development
environment for including the actual functionality in the
software architecture.
42
2016

Introduction
SystemDesk Modeling Module
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 model-
ing software components (SWCs) to specifying system
Application Fields
aspects including the hardware topology and network
communication.
Key Benefits
Easy workflow and intuitive working environment
Easy start in working with AUTOSAR
Ideally suited for large production projects
Reliable data exchange between different project
members
Software
Example Workflow:
Modeling an ECU Software Architecture According to AUTOSAR
Modeling the Software Architecture

The first step is to define the software components (SWCs), Additionally existing SWCs or other parts of the architecture,
Hardware
which each represent a functionality, and the data they ex- such as data types, can be imported for reusing existing soft-
change with each other. Since the components can be de- ware. SystemDesk supports the modeling process by a graphical
veloped individually, development work can be split between representation of the SWCs and their interconnections. New
several developers. For example, an OEM can develop an overall SWCs, their ports and connections are modeled in this diagram,
system design and then extract the specifications for suppliers providing developers with an intuitive working method and
to provide the SWCs. offering a well-defined overview of even the most complex
system.
Engineering
Designing Software Components

The next step is to define and configure the internal behav- dialogs. These dialogs offer guidance so you can enter data
ior of the software components. Among others, this com- easily and avoid potential errors.
prises runnables, which are C functions inside of software Additionally several integrated validation procedures make
components, and the means of communication between sure the modeled elements and references are AUTOSAR-
them and with the outside of the software component. compliant and consistent.
SystemDesk supports the configuration with sophisticated
43
2016

Data Exchange with TargetLink

After the software components are designed, their func- which can be opened from SystemDesk and TargetLink.
tions can be implemented from any C code generation tool. Once the options for the export are defined, such as which
SystemDesk is closely coupled with dSPACE's production files and data to include, the following import/export just
code generator TargetLink (p. 202). Both tools support an requires a few clicks.
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 AUTOSAR-
compliant 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
Modeling the System

In the last process step, a system consisting of a software ping editors present the data in a clear order and offer easy
architecture, a hardware topology, and a network com- means for working on specific tasks.
munication description is created. Once the system is modeled, it can be integrated either
The software architecture was developed in the first step in a basic software configuration tool to create the final
when designing the software components. ECU or in SystemDesk as a virtual ECU for simulation on a
The hardware topology of an E/E system can be specified dSPACE simulation platform.
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- Special editors in SystemDesk make the mapping convenient.
44
2016

Introduction
Data Transfer to Basic Software Configuration Tools

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. System-
Desk can be connected to any AUTOSAR-compliant basic
software configuration tool for generating and configuring
Application Fields
basic software modules such as OS and COM. You can flex-
ibly 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.
By default, SystemDesk supports data exchange with EB

tresos®. Additional support for further third-party tools can
be added.
Software
Cooperation with EB Automotive
dSPACE and EB Automotive cooperate to offer an optimal from SystemDesk, the parameters for the basic software can
tool chain for developing AUTOSAR-based ECU software: be configured in EB tresos® Studio. The tool automatically
dSPACE TargetLink®, dSPACE SystemDesk®, and EB tresos® generates the implementation code for the operating sys-
Hardware
Studio. tem and other AUTOSAR-compliant basic software modules.
EB tresos® Studio allows complete ECU basic software con- Together with the C code for the SWCs, the implementa-
figuration, integration and validation in one single tool tion code from EB tresos® Studio makes up the final code
environment. Based on the system description files exported for the ECU.
Engineering
45
2016

SystemDesk VECU Generation Module

Application Areas
For virtual validation applications, the SystemDesk V-ECU
Generation Module lets you configure and generate virtual
ECUs (V-ECUs). V-ECUs enable you to test the system's over-
all behavior with the PC-based simulation platform VEOS,
the hardware-in-the-loop (HIL) simulator SCALEXIO® or the
rapid control prototyping (RCP) platform MicroAutoBox II
as soon as the implementation with C code is available.
Key Benefits
Guided creation of virtual ECUs out of the software Automatic processes for V-ECU generation possible

architecture due to complete automation API
Automatic configuration of the basic software for Comprehensive validation of software architecture

simple and fast preparation of V-ECUs model for direct feedback in case of problems
Feature Overview
V-ECUs created with SystemDesk comprise components Preparing the V-ECU for connection to plant models is easy
from the application and the basic software, and provide with SystemDesk. You can even include intervention points
functionalities comparable to those of real ECUs. The Sys- at which errors for stimulating the RTE are inserted, which
temDesk V-ECU Generation Module makes it possible to is much easier than in a real ECU. This makes it easy to test
configure and generate BSW modules, e.g., the RTE, OS, the application software in various error scenarios.
the ECU State Manager or the NVRAM Manager. For a Besides the task of configuring and generating the V-ECU,
real ECU, configuring the basic software is often a tedious SystemDesk supports you during the whole process. A
task. Not so with SystemDesk, as you can choose to let Sys- powerful validation checks the AUTOSAR architecture and
temDesk automatically configure the BSW modules, which reports problems in the input ARXML file, enabling you to
is often sufficient for simulation purposes. If you want to fix these problems instead of running into them later during
configure a module specifically to your needs, SystemDesk RTE generation. And, thanks to the complete automation
also offers convenient editors, for example for mapping API, SystemDesk can also be used in automated processes
RTE events to tasks. for generating the V-ECUs.
Integration into the Development Tool Chain

V-ECUs can be simulated with the PC-based simulation system MicroAutoBox II. They can be simulated together
platform dSPACE VEOS for an early verification of the ECU with the physical plant, and be evaluated in the laboratory
software. VEOS offline simulation can be used for simulating or in the vehicle.
single V-ECUs and ECU networks including bus simulation, Irrespective of the simulation platform, you can use Con-
and also for software-in-the-loop (SIL) and processor-in- trolDesk® Next Generation for experimenting and visualizing
the-loop (PIL) simulation. Additionally, V-ECUs can be used the simulation, AutomationDesk for test automation and
for HIL simulation with dSPACE SCALEXIO, where ECU ModelDesk for model and environment parameterization.
hardware prototypes which are not available yet are sub- This has the advantage that you can create and test layouts
stituted by V-ECUs. For RCP purposes, the RTI AUTOSAR and automated tests for the HIL simulation on VEOS and
Blockset allows V-ECUs to be deployed on dSPACE’s RCP reuse them on SCALEXIO.
46
2016

Introduction
Use Cases
Simulation at Software Architecture Level Bus Simulation

The modeled software architectures can be verified and You can also distribute software components in System-
tested, without considering the underlying hardware topol- Desk to different ECUs, import predefined communication
ogy (virtual functional bus (VFB) mode). Hereby functional matrices and generate V-ECUs including a COM stack. The
errors or error behavior in the communication between V-ECUs can then be connected via a virtual bus. For each
Application Fields
software components can be found and fixed as soon as ECU, SystemDesk provides the required basic software
possible. SystemDesk provides the basic software modules components. You can use VEOS to simulate the bus com-
needed for simulation, such as RTE and OS, and offers munication between the ECUs. Arbitration effects, transfer
options for modeling, configuring and integrating basic times and transmission delays of bus messages or ECU and
software components. bus breakdowns can be simulated for CAN and LIN buses
Together with the PC-based simulation platform VEOS, and verified in an early phase of development. Networks
software architectures can be simulated early in the devel- including FlexRay buses can be modeled and simulated as
opment phase. idealized buses.
Software
Processor-in-the-Loop Simulation
Further Features

In addition to software-in-the-loop (SIL) simulation for Generate V-ECUs from Non-AUTOSAR Code

simulation at the software architecture level or bus simu- Integrate series BSW from any vendor into the V-ECU

lation, SystemDesk also supports processor-in-the-loop (PIL)
simulation. Therefore, you can use SystemDesk to build
virtual ECUs for different target processors and execute
Hardware
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.
Definition of a Virtual ECU
Engineering
A virtual ECU (V-ECU) is software that emulates a real ECU The abstraction level of a V-ECU depends on its applica-
in a simulation scenario. The V-ECU comprises components tion case:
from the application and the basic software, and provides V-ECU for developing a single ECU function (contains
functionalities comparable to those of a real ECU. Unlike a selected parts of the application software; the RTE and
soft ECU, which uses only a simplified Simulink®/Stateflow® necessary parts of the basic software are provided
model, a V-ECU usually has the same software components automatically)
as the finished ECU. There is no strict dividing line between V-ECU at application level (application software com
a soft ECU and a V-ECU, but a V-ECU generally represents ponents, RTE, operating system)
the real ECU more realistically. V-ECU including parts of basic software (application soft-
ware components, RTE, operating system, hardware-
independent basic software such as DEM, NVRAM,
ECU state manager, COM, etc.)
47
2016

Implementation Software / ConfigurationDesk
ConfigurationDesk®
Configuration and implementation software for dSPACE SCALEXIO® hardware
Highlights
Configure real-time applications graphically

Manage signal paths between external devices

(like ECUs or loads) and behavior model interfaces
Implement behavior model code and I/O function

code on dSPACE hardware
Multicore and multi-processing-unit applications

Import of virtual ECUs (V-ECUs)

Support of Functional Mock-up Units (FMUs)

Application Fields Key Benefits

ConfigurationDesk is an intuitive, graphical configuration With ConfigurationDesk, it is easy to implement the be-
and implementation tool. It is ideal for handling HIL real- havior model code (e.g., from MATLAB®/Simulink®/Simulink
time applications, and for implementing behavior models Coder™) and the I/O function code (from ConfigurationDesk)
and I/O function code on dSPACE SCALEXIO hardware. You on the dSPACE SCALEXIO hardware. The entire build process
can define and document external devices such as ECUs for a real-time application is handled by ConfigurationDesk.
and loads, including their signal properties (descriptions, Comprehensive documentation options and graphical dis-
electrical properties, failure simulation settings, load set- plays give you great project transparency – a great advantage
tings). ConfigurationDesk displays user-defined views of with large-scale HIL project especially. You can assemble
the signal path between the ECU pins/load pins and the and configure the project-specific hardware offline as a
behavior model interfaces. "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
2016

Introduction
I/O configuration and I/O configuration for connecting a behavior model to dSPACE SCALEXIO hardware:

documentation 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)

I/O functions (describe the functionality between a set of external device ports and a set of model ports

independently of the hardware topology)
Model port mapping (connections between function ports and model ports)

Model topology (model ports used for the ConfigurationDesk application)

Application Fields
Hardware resource assignment (mapping I/O functions to hardware resources)

Hardware topology (hardware resources used by I/O functions)

Documentation:

External device topologies (properties of ECU pins/load pins)

Model topology (describes the interface to the behavior model)

Hardware topology (describes the simulator hardware: boards, internal wiring, internal loads, board locations, etc.)

Microsoft® Excel® file with pin information for external wiring harnesses

CAN and LIN signals can be configured either with the Bus Manager or with the RTI CAN MultiMessage Blockset and

the RTI LIN MultiMessage Blockset. FlexRay nodes are configured with the dSPACE FlexRay Configuration Package.
Real-time code generation Complete build process for I/O functions (ConfigurationDesk) and the behavior model (e.g., MATLAB®/Simulink®/

Simulink Coder)
Order Information
Software
Products Order Number
ConfigurationDesk – Loader Version (SCALEXIO) Free of charge

For use without license, limited function range (downloading real-time License for SCALEXIO Real-Time Library is needed

applications possible, but no changes or builds allowed)
ConfigurationDesk – Implementation Version CFD_I_100 (implementation version for 100 functions)

(SCALEXIO) CFD_I_200 (implementation version for 200 functions)

CFD_I_300 (implementation version for 300 functions)

CFD_I_1000 (implementation version for 1000 functions)

CFD_I_UNLTD (for an unlimited number of functions)

Hardware
CFD_I_MC (implementation version for SCALEXIO multicore applications)

CFD_I_MP (implementation version for SCALEXIO multiprocessor applications)

License for SCALEXIO Real-Time Library is needed

Bus Manager for CAN or LIN restbus simulation (SCALEXIO) Please see p. 54
SCALEXIO Failure Simulation (p. 324) SCLX_FS_100 (for 100 functions)

SCLX_FS_200 (for 200 functions)



SCLX_FS_UNLTD (for an unlimited number of functions)

SCALEXIO Real-Time Library for downloading and handling real-time SCLX_RTLib

Engineering
applications for the SCALEXIO system SCLX_RTLib_MC (for multicore applications)

SCLX_RTLib_MP (for multiprocessor applications)

SCLX_RTLib_VECU (for applications containing V-ECUs)

Relevant Software
Software Order Number

Required Operating system
www.dspace.com/goto?os_compatibility
Optional MathWorks MATLAB®/Simulink®/Simulink Coder™

–
RTI CAN MultiMessage Blockset (p. 74)
RTICANMM_BS (for applications containing CAN bus configurations)

RTI LIN MultiMessage Blockset (p. 77)
RTILINMM_BS (for applications containing LIN bus configurations)

SCALEXIO Ethernet Solution (p. 93)
SCLX_ETH_SOL (for adding Ethernet I/O functions to ConfigurationDesk)

dSPACE FlexRay Configuration Package (p. 80)
FCP (for applications containing FlexRay bus configurations)

NEW: Bus Manager
Please see p. 54
Microsoft® Excel®
–
49
2016

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 Whole real-time applications can be managed in ConfigurationDesk. This includes not only the associated

ConfigurationDesk application data, but also general files such as project plans and specifications.
2. Define external devices It takes just a few clicks to define the interfaces and signal properties of external devices such as ECUs

and loads in ConfigurationDesk.
3. Select and configure I/O functions I/O ports can be connected to the external devices graphically. You can define different views to focus on

specific data sets. I/O functions automatically fetch failure simulation settings and load settings from the
definitions of external devices.
4. Create model ports The behavior model and ConfigurationDesk applications are connected via model port blocks.

5. Design the Simulink model 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 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 You can run the entire build process with ConfigurationDesk, both for the I/O functions and for
and create the application for the dSPACE the behavior model.
hardware
8. Download the application to the The real-time application can be transferred to the dSPACE hardware quickly.

dSPACE hardware
Failure Simulation License

To use failure simulation with SCALEXIO, you have to For further information on failure simulation with SCALEXIO,
activate it with an additional FIU license. This must match please see p. 324.
the number of configured I/O channels capable of failure
simulation.
Support of Multicore or Multi-Processing-Unit

Systems for Complex Models
Large, complex models can be distributed across multiple The intermodel communication in this workflow is trans-
processing units and processor cores to ensure the simula- ferred from Simulink® to ConfigurationDesk.
tion runs in real time. Two different workflows are possible One processor core executes one model. Several models
for this. The first is to use separate behavior models for are combined to processing-unit-applications. These can be
each core and import them into ConfigurationDesk. The assigned to processing units in ConfigurationDesk, which
intermodel communication in this workflow is configured automatically performs the core-to-model assignment within
in ConfigurationDesk. In the second workflow, there is one each unit.
overall Simulink® model for the whole application, and a One processing unit consists of several processor cores. One
special Simulink block is used to specify which of its subsys- processor core in each processing unit is always reserved for
tems should be computed together on one core. The overall communication with the host PC. The other cores can be
model is then automatically split into separate model files. used for behavior model calculation.
50
2016

Introduction
Importing Virtual ECUs
In ConfigurationDesk you can integrate virtual ECUs (V- ECUs. The V-ECUs can contain CAN or LIN controllers to
ECUs) into a real-time application just like any other behavior simulate CAN or LIN bus communication between the ECUs.
models. With the SCALEXIO real-time hardware (p. 328), For information on generating V-ECUs, please refer to
V-ECUs can be simulated alone or in combination with real SystemDesk® V-ECU Generation Module (p. 46).
Application Fields
Support of Functional Mock-up Units
ConfigurationDesk supports the open Functional Mock-up The user workflow for importing and connecting FMUs to
Interface (FMI) standard. This enables the users to use differ- other model interfaces and to I/O is identical to the workflow
ent modeling approaches (e.g., based on physical modeling for V-ECUs and Simulink® models.
with Modelica) by using Functional Mock-up Units (FMUs).
In HIL projects, FMUs can be integrated together with V-ECUs For more information on FMI and its support in the dSPACE
and Simulink® models. tool chain, please refer to page 25.
Software
NEW: Working with Simulink® Models
ConfigurationDesk provides two approaches for integrating SICs are ZIP containers including the C code and other ar-
Simulink® models: tifacts, such as precompiled libraries and a model interface
Directly importing the MDL files generated out of MAT- description.
Hardware
LAB®/Simulink®. The direct import approach is convenient With the two ways of importing Simulink models, Configu-
if the Simulink® model has to be changed frequently, rationDesk always provides the best solution for your project
because in this approach the entire build process for a needs and requirement.
real-time application – including starting Simulink Coder
– is handled automatically by ConfigurationDesk.
Generating Simulink implementation containers (SICs)
out of MATLAB®/Simulink® and importing these SICs into
ConfigurationDesk. Once the SICs are generated, they
can be reused in different projects, without having to
Engineering
generate the C code again, thus saving time. Therefore,
this approach is more favorable, when you want to reuse
models for different projects or variants.
51
2016

Configuration Version for RapidPro

Key Features
Configuring the RapidPro hardware (p. 568)
Monitoring the hardware states during operation
Support for wiring the RapidPro hardware to sensors
and actuators
Application Area Benefits

The configuration version offers you configuration and di- The hardware is displayed in an intuitive structured view.
agnostics functions for RapidPro hardware (p. 568) and You can change the configurations of the individual module
supports you in putting the hardware into operation. channels and monitor the hardware states during operation.
The RapidPro hardware acts as an extension to dSPACE Channel-specific diagnostics (open load, etc.) are provided in
prototyping systems to cover application scenarios which a list view. You can manage the configurations of different
require signal conditioning, power stages, and intelligent hardware setups via the Project Manager. A pinout list for
I/O subsystems. wiring the RapidPro hardware to sensors and actuators can
be exported as a comma-separated value (CSV) file or a
Microsoft® Excel® file.
52
2016

Introduction
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.
Application Fields
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 ConfigurationDesk’s 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.
Order Information
Software
ConfigurationDesk – Loader Version (RapidPro) Free of charge

For use without license, limited function range
ConfigurationDesk – Configuration Version CFD-C

(RapidPro)
Hardware
Engineering
53
2016

Implementation Software / Bus Manager
NEW: Bus Manager

Configuration for LIN, CAN, and CAN FD bus simulation
Highlights
One configuration tool for different bus systems

Work with several communication matrices for one
configuration
Customizable restbus configuration with tool auto-
mation interface

The dSPACE Bus Manager is the central tool for configuring One tool for homogeneously configuring several bus
bus communication for simulation purposes e.g., restbus systems at the same time
simulation, and for implementing the bus communication in Easy bus configuration via drag & drop
real-time applications for dSPACE SCALEXIO® systems. It sup- Work with several communication matrices for one
ports different bus systems, such as LIN, CAN, and CAN FD. configuration
The Bus Manager is available as an add-on for dSPACE Con- Modeling-tool-independent model interface
figurationDesk® to configure hardware-in-the-loop real-time Tool automation interface
applications for dSPACE SCALEXIO hardware.
Workflow
The Bus Manager offers a convenient and straight-forward If required, you can configure different parameters and

workflow for implementing bus simulations: properties of the simulated elements. For example, you
Import one or more bus communication matrices. All can enable the access to signal values during run time
relevant information is extracted automatically for the via experiment software such as ControlDesk® Next Genera-
subsequent bus configuration. tion. If the simulation requires signals whose values must
Create a bus configuration. For the configuration, differ- change dynamically during run time, you can use beha-
ent views for the dedicated tasks are available. vior models, e.g., MATLAB/Simulink behavior models or
Assign the communication matrices completely or in part Functional Mock-up Units (FMUs) to use behavior models
to the bus configurations. modeled in another modeling tool.
Specify the real-time hardware access. Finally, start the build process, and download and execute
the real-time application.
54
2016

Implementation Software / Bus Manager
Introduction
General Import of several communication matrices, such as AUTOSAR system description files, FIBEX, DBC, and

LDF files
Versatile communication matrix visualization with different views, folding, filtering, searching

Easy restbus configuration across communication matrices via drag & drop
Application Fields

Selectable and customizable restbus configuration view

Tree view and property grid for bus-element-based configuration

Table view for multiple-element configuration

Configuration of the bus hardware

Modeling-tool-independent model interface (model port blocks)

Support of Functional Mock-up Units (FMUs)

Convenient update of existing configurations with new communication matrices

LIN Send and receive of unconditional, event-triggered and sporadic frames/PDUs

Generation of LIN schedules

CAN Cyclic send and receive of CAN frames/PDUs

Support of multiplexed PDUs

CAN FD Cyclic send and receive of CAN FD frames/PDUs
Software

Support of multiplexed PDUs

Order Information
Product Order Number

Bus Manager (add-on for ConfigurationDesk) CFD_BUSMANAGER_BASE

Hardware
Relevant Software and Hardware

Required ConfigurationDesk (for SCALEXIO)
See p. 48
Optional ConfigurationDesk CAN Support
CFD_Implementation_CAN

ConfigurationDesk LIN Support
CFD_Implementation_LIN

Engineering
Hardware Order Number
Optional DS2671 Bus Board
DS2671
DS2680 I/O Unit (with bus support)
DS2680_2672
55
2016

Implementation Software / RealTime Interface
RealTime Interface
Implementation software for running models on dSPACE hardware
Highlights
Automatic implementation of MATLAB®/Simulink®/

Stateflow® models on dSPACE hardware
Automatic code generation

Graphical I/O configuration via comprehensive Simulink

block libraries
Easy and safe to use due to automatic consistency

checks
Support of model referencing hierarchies1)

Application Areas
No matter whether you are performing rapid control proto- for the seamless, automatic implementation of your
typing or hardware-in-the-loop simulation: Real-Time Inter- Simulink and Stateflow models on the real-time hardware.
face (RTI) is the link between dSPACE hardware and the The implementation time is greatly reduced. The hardware
development software MATLAB/Simulink/Stateflow from configuration for the real-time application is guided by
MathWorks®. automatic consistency checks to prevent parameterization
errors. For maximum flexibility, each RTI version supports
Key Benefits several different MATLAB releases (see www.dspace.com/
RTI lets you concentrate fully on the actual design process go/Compatibility). Models from most previous MATLAB and
and carry out fast design iterations. It extends the C code RTI releases are migrated automatically when newer versions
generator Simulink Coder™ (formerly Real-Time Workshop®) of RTI are used.
Working with RTI Comprehensive Functionalities

To connect your model to a dSPACE I/O board, just drag & RTI handles any kind of continuous-time, discrete-time, and
drop the I/O module from the RTI block library and then con- multirate system. Depending on the I/O hardware, different
nect it to the Simulink blocks. All settings, such as parameter- channels of the same I/O board can be used with different
ization, are available by clicking the appropriate blocks. sample rates, and even in different subsystems. RTI supports
Simulink Coder™ (formerly Real-Time Workshop®) generates asynchronous events and lets you set task priorities and task
the model code while RTI provides blocks that implement the overrun strategies for executing the interrupt-driven sub-
I/O capabilities of dSPACE systems in your Simulink models, systems. It also supports time-triggered tasks and timetables,
thus preparing the model for the real-time application. Your which allow you to implement tasks and groups of tasks
real-time model is compiled, downloaded, and started auto- with variable or predefined delay times in relation to an
matically on your real-time hardware, without you having to associated trigger event. This makes task handling in your
write a single line of code. RTI guides you during the con- model very flexible. In addition, RTI offers checks which help
figuration. RTI provides consistency checks, so potential errors avoid double or improper use of channels.
can be identified and corrected before or during the build
process.
56
2016 1)
Please contact dSPACE for information on features and limitations.

Implementation Software / Real-Time Interface
Introduction
I/O configuration Comprehensive block library for specifying the hardware setup

Configuration of dSPACE I/O simply by connecting the relevant blocks to the Simulink blocks

I/O
parameter specification, such as voltage ranges, resolutions, digital I/O, serial interface parameters,
and PWM frequencies
Automatic checks on parameter ranges and consistency

I/O access anywhere in your model and at different sample rates

Application Fields
Separate blocks for different functions of complex I/O boards

Data typing and data-typed I/O

Asynchronous execution of Simulink subsystems triggered by hardware or software interrupts

S-functions and user-written code

Generating real-time code Generation of C code by Simulink Coder™ (formerly Real-Time Workshop®)

C code optimization for real-time implementations

Support of Simulink Coder™ (formerly Real-Time Workshop®) code optimizations

Generation of initialization functions and I/O function calls

Automatic task definition Support of multirate systems and preemptive, priority-based multitasking

Single timer and multiple timer task mode

Asynchronous tasks

External hardware interrupts

Software
Software interrupts

Configurable priority and overrun handling for each task

Turnaround time measurement for each task

Optional synchronization of periodic timer tasks to external events

Time-triggered tasks and timetables

Non-real-time simulation modes

Invoking the compiler Automatic compiler call that compiles and links the model

Loading and starting the application Program download to the real-time hardware

Simulation control

Interactive control, monitoring, and data acquisition with ControlDesk® Next Generation (p. 120)

Data acquisition with time stamps

Hardware
Order Information

Real-Time Interface RTI

Engineering
57
2016


Required Microtec C Compiler (p. 111) for DS1103, DS1104, DS1005, and MicroAutoBox II CCPPPC

GNU C Compiler for DS1006
DS1006_COMP

DS1007_COMP

GNU C Compiler for MicroLabBox
MLBX_COMP

Operating system: www.dspace.com/goto?os_compatibility
–
Optional Real-Time Interface for Multiprocessor Systems RTI-MP (p. 62)
RTI_MP

Real-Time Interface Bypass Blockset (p. 64)
RTIBYPASS_BS

Real-Time Interface CAN Blockset (p. 71)
RTICAN_BS

Real-Time Interface CAN MultiMessage Blockset (p. 74)
RTICANMM_BS

Real-Time Interface LIN MultiMessage Blockset (p. 77)
RTILINMM_BS

FCP

RTI RapidPro Control Unit Blockset (p. 582)
RTIRAPIDPRO_BS

RTIAUTOSAR_PKG

RTI Electric Motor Control Blockset (p. 547)
RTI_EMC_BS

RTI FPGA Programming Blockset (p. 90)
RTIFPGA_BS

Stateflow®/Stateflow Coder® from MathWorks
–
Ethernet Blocksets (p. 92)
See p. 92

Required Pentium
®
4 at 2 GHz (or equivalent) –
1 GB RAM (minimum), 2 GB RAM or more (recommended)

Optional DS1103 PPC Controller Board (p. 358)
DS1103

DS1104 R&D Controller Board (p. 364)
DS1104

DS1005 PPC Board (p. 376)
DS1005

DS1006 Processor Board (p. 380)
DS1006

DS1007 PPC Processor Board (p. 386)
DS1007

MicroAutoBox II (p. 548)1)
See p. 548

MicroLabBox with front panel
MLBX_1302F

MicroLabBox with top panel
MLBX_1302T

1)
The former MicroAutoBox can also be used.
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 environ-
ment.
58
2016

Introduction
Graphical I/O Configuration Parameter Specification
When you have finished testing your model in Simulink, it I/O parameters are specified by double-clicking an I/O block
has to be prepared for implementation on the real-time and entering the data in graphical user interfaces. In this
hardware. The plant model is replaced by I/O blocks that example, the input signals are the feedback value and the
form the interfaces to the real controlled system. To add an reference signal. The reference signal now comes from an
I/O model, simply drag a block from the RTI I/O library to external signal generator and is read in by an ADC block.
Application Fields
the model and connect the block with the I/O of the con- The output signal from the controller is the control signal
troller. u_M, which is output by the hardware via a DAC block.
Software
Hardware
Engineering
59
2016

Implementation on dSPACE Hardware Interaction with Experiment Software

Automatic implementation of the Simulink model on dSPACE When your application is running on the real-time hardware,
hardware is the key to rapid design iterations. With RTI you the whole dSPACE experiment software is at your disposal.
will not see a single line of code during this process. A RTI ensures that you have control over each individual vari-
single click on Build starts the implementation, including able immediately after the implementation process.
code generation, compiling, and downloading. You can ControlDesk Next Generation provides an instrument panel
select an integration algorithm and a step size in the solver that enables you to change parameters and monitor signals –
page of the Simulation Parameters dialog. Build procedures without regenerating the code. ControlDesk Next Genera-
can also be automated with the help of scripts. This is tion also displays the time histories of any variable used by
especially useful for large models. your application.
60
2016

Introduction
Blocksets for Real-Time Interface
Supporting dSPACE Hardware
No matter whether you are using dSPACE systems with
single-board hardware, modular hardware, or MicroAuto-
Box II1): RTI supports all dSPACE real-time processors and
allows convenient model and I/O configuration of your
dSPACE system.
Application Fields
Real-Time Interface Real-Time Interface Real-Time Interface Real-Time Interface Real-Time Interface
for Multiprocessor Systems CAN Blockset CAN MultiMessage RapidPro Control Unit Bypass Blockset
Blockset Blockset
dSPACE FlexRay Real-Time Interface Real-Time Interface

Real-Time Interface
Configuration LIN MultiMessage FPGA Programming Ethernet Blocksets
AUTOSAR Blockset
Package Blockset Blockset
Real-Time Interface (RTI)
Software
Real-Time Interface for Multiprocessor Systems RTI Bypass Blockset
For graphical setup of multiprocessor structures. For configuring bypass applications.
RTI-MP (p. 62) RTI Bypass Blockset (p. 64)
CAN Blocksets RTI LIN MultiMessage Blockset
Hardware
For combining dSPACE systems with CAN communication For combining dSPACE systems with LIN communication
networks. networks.
RTI CAN Blockset (p. 71) RTI LIN MultiMessage Blockset (p. 77)
dSPACE FlexRay Configuration Package RTI RapidPro Control Unit Blockset

For configuring dSPACE systems in FlexRay communica- Extensive I/O functionalities for the MicroAutoBox II1) or
tion networks. DS1005 used in combination with the RapidPro Control
dSPACE FlexRay Configuration Package (p. 80) Unit, e.g., for engine, chassis, and drives control.
Engineering
RTI RapidPro Control Unit Blockset (p. 582)
RTI AUTOSAR Blockset RTI FPGA Programming Blockset

Using AUTOSAR software components in a MATLAB®/ Integrating FPGA models in dSPACE systems.
Simulink® environment. RTI FPGA Programming Blockset (p. 90)
Ethernet Blocksets RTI Electric Motor Control Blockset

Connecting dSPACE hardware to other devices via Ethernet. For combining dSPACE MicroLabBox with electric drive
Ethernet Blocksets (p. 92) systems.
61
1)
The former MicroAutoBox can also be used. 2016

Implementation Software / RealTime Interface for Multiprocessor Systems (RTIMP)
RealTime Interface for Multiprocessor Systems (RTIMP)

For graphical setup of multiprocessor structures
Highlights
Interprocessor interrupts for synchronized tasks

across several CPUs
Graphical setup of multiprocessor systems

within Simulink®

The multiprocessor option for Real-Time Interface (RTI-MP) RTI-MP offers a maximum of convenience to accomplish
supports multiprocessor and multicore systems based on tasks such as:
dSPACE‘s modular hardware and helps to increase the Partitioning the system for optimum processor load
performance of real-time simulations. It assists in setting Defining interprocessor communication channels
up multiprocessor networks, including the communication Producing the communication code for a network
channels. Multicore applications are configured in the same of several processors or cores
way as multiprocessor applications. System dynamics can be designed in Simulink.
Working with RTI-MP RTI-MP for dSPACE Simulator

RTI-MP enables you to partition your system model and al- In practical development work, several processor boards
locate the parts to the processors or cores by using simple are often connected to one networked dSPACE Simulator
drag & drop operations. Each processor submodel can be (p. 520), and highly dynamic simulation models exchange
adjusted individually for optimum performance, including simulation data via Gigalink modules. An easy way of specify-
step sizes, integration algorithms and trigger conditions. ing the topology of a whole network is therefore essential.
After specification, you can implement your model on the RTI-MP offers special blocks to configure Gigalink communi-
processor boards with a single mouse click. Build procedures cation within Simulink. The real-time application, including
can also be automated with the help of scripts. real-time synchronization between the simulators, can then
be generated with a single click.
62
2016

Implementation Software / RealTime Interface for Multiprocessor Systems (RTIMP)
Introduction
Partitioning the Simulink® model Adding Simulink blocks for model partitioning via drag & drop

Generation of highly optimized realtime simulation engine and communication code

Support of triggered subsystems distributed over multiple processors or cores

Full support of interprocessor interrupts

Optimizing speed and accuracy Integration algorithm and step size specific to each processor and core

Single/multitasking mode

Application Fields
Swinging buffer or shared memory communication mechanism for each individual connection

Interprocessor communication at different sampling rates

Testing and documenting Documentation of entire multiprocessor setup

Implementing the model on Automatic code generation for one processor or complete system

multiprocessor or multicore hardware Download and start with a single click

Data acquisition with time stamps

Profile information for communication channels for optimizing the partitioning

Communication mechanisms Communication via highspeed optical connection (Gigalink) enabled

Asynchronous data transfer in shared memory mode

Synchronized and unsynchronized block data transfer in swinging buffer mode

Buffering and unbuffering of data via communication connection

Software
Order Information
RealTime Interface for Multiprocessor Systems (RTIMP) RTI_MP


Required RealTime Interface (p. 56)
1)
RTI

Microtec C Compiler (p. 111) for DS1005 or CCPPPC
Hardware

GNU C Compiler (p. 111) (DS1006, DS1007, MicroLabBox)
See p. 111
1)
For information on standard hardware and software requirements for Real-Time Interface, please see p. 56.

Optional DS1005 PPC Board (p. 376) or
DS1005

DS1006

DS910 Gigalink Module (p. 379) or
DS910

DS911 Gigalink Module (p. 385)
DS911

Engineering
DS1007

Optional (only for MicroLabBox with front panel
MLBX_1302F

multicore applications) MicroLabBox with top panel
MLBX_1302T

Automatic implementation is started via

buttons: RTIMP downloads your model
to the multiprocessor system and starts

running it automatically.
63
2016

Implementation Software / RTI Bypass Blockset
Real-Time Interface Bypass Blockset

ECU interfacing for rapid control prototyping and intrusive testing of existing ECU software
Highlights
Supports rapid control prototyping (RCP) and white-

box testing of physical as well as virtual ECUs (V-ECUs)
No need for ECU source code or build environment

Synchronizing the execution of model-based

algorithms with ECU-internal functions and events
Real-time read and write access to ECU internal

variables and parameters

The dSPACE tool chain for bypassing and ECU interfacing As the RTI Bypass Blockset hides ECU-specific information
consists of the RTI Bypass Blockset and the ECU Interface on the bypass interface, control and test engineers can
Manager (see p. 248). It can be used for applications in completely concentrate on function design and test case
rapid control prototyping, hardware-in-the-loop (HIL) testing development. Based on the ECU description file (A2L file),
as well as for white-box testing of existing ECU software. users can flexibly select model inputs and outputs as well
When only some parts of an existing ECU software need to as triggers without modifying the ECU software.
be optimized or enhanced, bypassing is a powerful and A variety of ECU interfaces are supported, such as CCP, XCP
proven method for rapid control prototyping. It can be em- on CAN, XCP on Ethernet, XCP on FlexRay, and dedicated
ployed when no Simulink® models of the original control ECU interfaces such as dSPACE DCI-GSIs, or DPMEM PODs.
algorithms are available, or when there is no access to the If you use the dSPACE bypassing services (see p. 252 and
source code of ECU software. MATLAB®/Simulink models p. 253), dedicated mechanisms ensure data consistency and
can be used to bypass and, as a consequence, replace safe operation.
original ECU functions. The RTI Bypass Blockset is part of a complete tool chain
The dSPACE tool chain for bypassing and ECU interfacing for service-based bypassing that supports different bypass
also makes test case development considerably easier. You methods and different platforms for model execution:
can use the tool chain to apply test stimuli in real time that External bypassing on dedicated RCP systems
are triggered by ECU-internal events. In addition, ECU in- Internal bypassing directly on the target ECU
ternal memory can be read and written in real time. ECU Virtual bypassing of virtual ECUs in a PC-based
functions can be stimulated with specific, reproducible test simulation or on MicroAutoBox® II without using a
data, which makes it easier to cover test cases with a com- physical target ECU at all
plex setup. External sensors or actuators in the ECU that are The RTI Bypass Blockset supports all bypass methods and
difficult to stimulate or hard to access externally can be all ECU interfaces with the same intuitive look and feel. It
bypassed in order to directly stimulate the ECU functions is easy to switch between the different bypass methods and
under test. Thus, the test coverage of ECU software can be platforms, as no changes to the Simulink model are required.
enhanced considerably. 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 in-
tegration of the RTI Bypass Blockset into customer-specific
development tool chains.
64
2016

Introduction
Selecting ECU functions and variables Flexibly mapping new Simulink models to ECU functions to trigger their execution

Selecting ECU variables via an integrated A2L file browser or by defining new ones via

dialogs
Measurement and calibration Uploading and downloading ECU variables including data vectors

Real-time data acquisition and data stimulation of ECU variables including data vectors

Measuring of internal events and execution times of the ECU

Application Fields
Configuration of bypass interfaces and services Switching between bypass execution platforms without changes to the Simulink model

Specifying several variable description files (A2L files) for the same bypass interface

Model-based configuration of bypass service and interface based on A2L files

Dynamic model configuration Switching on/off the bypass function during run-time

Enabling and disabling service calls in the ECU code

Deactivating read/write access to selected ECU variables during run time without

recompiling the model
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
Tool automation Automation API for configuring bypass blocks via scripts
Software
External bypassing Supported ECU interfaces and XCP on CAN/CAN FD, XCP on Ethernet (UDP/IP), XCP on FlexRay

standards for external bypassing CCP (CAN Calibration Protocol)

Seed & key access to ECU for XCP and CCP

JTAG/OCDS, JTAG/SDI, JTAG/Nexus, Nexus/READI, AUD/AUD2, NBD, H-UDI

Dual-port memory (DPMEM)

Supported bypass services dSPACE Calibration and Bypassing Service (see p. 252)

dSPACE XCP Service for external bypassing via CAN, Flexray and Ethernet buses

Third-party XCP services for measurement and calibration

Safety Configurable failure checking and double buffer mechanism

Configurable fall-back strategy when the connection between the RCP system and ECU

is interrupted
Hardware
XCP-related options Switching calibration pages via XCP

XCP on CAN gateway functionality for arbitrated access to the ECU via multiple tools

Internal bypassing Microcontroller support1) Supported Microcontroller Families
Freescale MPC55xx, MPC56xx, and MPC57xx

ST Microelectronics SPC56 and SPC 57

Infineon TriCore incl. AURIX

Renesas V850 and RH850

Support of whole microcontroller families; no ECU-specific licenses required.

Reuse of existing software Integrating functions that are available as C source code into the Simulink model

functions Calling ECU-internal functions from the Simulink model

Engineering
Supported bypass services dSPACE Internal Bypassing Service (see p. 253)
Virtual bypassing Supported bypass services dSPACE Bypassing Service integrated in VEOS® and MicroAutoBox II
1)
Support for further microcontroller families is planned. Please inquire.
65
2016

Order Information

Real-Time Interface Bypass Blockset RTIBYPASS_BS


Required Real-Time Interface1) (p. 56)
RTI

Microtec C Compiler for DS1005 and MicroAutoBox II2)
CCPPPC

DS1006_COMP

Optional Internal Bypass Plug-In for RTI Bypass Blockset
RTIBYPASS_BS_INT

ECU Interface Manager
See p. 248

dSPACE Calibration and Bypassing Service
See p. 252

dSPACE Internal Bypassing Service
See p. 253

dSPACE XCP Service (p. 254)
DSPACE_XCP_SERVICE

Variable Editor (p. 255)
DSPACE_VAR

dSPACE ECU Flash Programming Tool (p. 257)
DSPACE_ECU_FLASH

VEOS (p. 112)
See p. 112


Optional DS1005 PPC Board (p. 376)
DS1005

DS1006

DS2202, DS2211 HIL I/O Boards (p. 406, p. 410)
DS2202, DS2211

DS4121 ECU Interface Board (p. 436)
DS4121

DS4302 CAN Interface Board (p. 442)
DS4302

DS4505 Interface Board (p. 448)
DS4505

MicroAutoBox II
2)
See p. 548

Generic Serial Interfaces DCI-GSI1 and DCI-GSI2 (p. 540)
See p. 540

1)
For information on standard hardware and software requirements for Real-Time Interface (RTI), please see p. 56.
2)
66
2016

Introduction
External Bypassing
This bypass method is an efficient approach to developing
Bypassing
new software functions and optimizing existing controller
RCP System
strategies. It can also be used for white-box testing of ECU New control strategy
software. (under development)
Application Fields
The external bypass method uses a dedicated RCP system Y=f(X)
to execute a new controller or test model, while the original

ECU
ECU runs on the target ECU, and can remain unchanged. interface
During the design and test phases, external bypassing allows X Y
even complex Simulink models to be executed, since there Existing control strategies
are almost no resource constraints such as available RAM,
ECU
ROM (flash), processor performance, or additional I/O chan-
nels. Real-time behavior is guaranteed even for complex White-Box Testing
bypass functions. Any additional sensors and actuators that dSPACE real-time system
are needed can be connected directly to the prototyping
Software
Test function
system. dSPACE supports numerous interfaces to connect
Stimulate Measure
the prototyping system to the ECU, such as CCP, XCP or
on-chip debug interfaces. ECU
interface
X Y
Control strategies under test
ECU
Hardware
RTI Bypass Blockset with
Internal Bypass Plug-In
Bypass model
Developer PC Rapid prototyping

systems
Engineering
ECU
Measurement interfaces
and calibration tool ECU service
code
External bypass workflow.
67
2016

Internal Bypassing
Internal bypassing can be used for on-target prototyping,
Bypass model
i.e., rapid control prototyping on the target ECU, as well as
for white-box testing. With internal bypassing, new control-
New control
ler or test models can be implemented directly on the exist-
strategy
ing ECU by using its free RAM and flash memory areas.
Y=f(x)’
Target code for the bypass model is generated from the
Simulink model and merged into the existing ECU image fn f(x) fm
ECU X Y
file (HEX file). No special rapid control prototyping or test Existing control strategies
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 in-
tegrated into very fast control loops.
RTI Bypass Blockset
A2L Bypass model

Developer PC
HEX
HEX’ A2L’
(with internal (with variables
related to internal
Measurement bypass function)
bypass function)
and calibration tool
Flash ECU
(including bypass model)
Workflow with the Internal Bypass PlugIn for the RTI Bypass Blockset.
68
2016

Introduction
Virtual Bypassing
With dSPACE VEOS (p. 112), 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 Virtual
Application Fields
bypass
of the RTI AUTOSAR Blockset (p. 86) and executed under
real-time conditions together with a physical plant.
New functions can therefore be tested and validated even Controller model
(under development)
before prototypes of the target ECU become available. 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 execut-
ed in the context of a V-ECU, synchronized to specific tasks
or runnables and with arbitrary access to the A2L variables
Software
of the V-ECU.

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

69
2016


Bypass model
A2L
Developer PC (with information
on bypass hooks)
A2L’
(with variables
related to internal
bypass function)
HEX
(with
bypass hooks)
HEX’
Measurement (with internal
bypass function)
MicroAutoBox II with V-ECU
Virtual bypass workflow for MicroAutoBox IIbased realtime execution of VECU.
Bypass Integration
In order to use the RTI Bypass Blockset for ECU interfacing ally into the ECU source code, or by using the ECU Interface
and bypassing purposes, a bypass service needs to be inte- Manager (p. 248). The ECU Interface Manager allows inte-
grated into the ECU software that handles the communica- grating the bypass into the original ECU Hex code of the
tion and synchronization between the new controller and ECU software. Thus, no access to the build environment or
test model, and the original ECU software. This can be source code is required.
achieved by integrating the service and service calls manu-
Importing ASAM-MCD 2MC Files

An ASAM-MCD 2MC ECU description file (A2L file) can be mapped to the respective addresses on the ECU. The block-
easily imported as a database. An intuitive variable browser set lets you access ECU variables via their names and auto-
with search options and hierarchical representation of vari- matically performs conversion between the ECU HEX rep-
ables facilitates the handling of large description files that resentation and the physical representation on the dSPACE
contain a high number of variables. The variable names are system.
70
2016

Implementation Software / RTI CAN Blockset
RTI CAN Blockset
Introduction
For combining dSPACE systems with CAN communication networks
Highlights
Application Fields
Ideal for developing and testing control functions

that communicate via a CAN bus system
Database file import

CAN raw data access

One Simulink® block for each functionality/

each message
Software
Application Areas
The RTI CAN Blockset is an extension for Real-Time Interface MultiMessage Blockset (p. 74) differ with regard to their
(p. 56) and can be used for combining dSPACE systems with features and application areas (rapid control prototyping/
CAN communication networks and for configuring these hardware-in-the-loop simulation).
CAN networks. The RTI CAN Blockset and the RTI CAN
Hardware
Key Benefits
The RTI CAN Blockset is especially suited for developing and The blockset’s multiple DBC file support allows simultaneous
testing control functions that communicate via a CAN bus use of several DBC files for one model, so the DBC file vari-
system. To set up a message with the RTI CAN Blockset, ants are easier to handle and can be switched during run
simply choose the appropriate block from the CAN block time. With the blockset, CAN raw data can be accessed
library and connect it to your Simulink model. Configuration directly from within Simulink. This means that, using the
information such as the baud rate, identifier, message raw data, protocols can be created on the Simulink model
length, and interrupts, can be entered in dialogs. level.
Engineering
71
2016

General Message-oriented Simulink blockset for combining dSPACE systems with CAN communication networks and

for configuring these CAN networks
One Simulink block for each functionality/each message

Initialization and configuration Importing database files (see below)

Configuring baud rate, sample mode, bit timing parameters, termination resistors, etc.

DBC file support

User-defined database support via custom parser

Multiple DBC file support allowing simultaneous use of several DBC files for one model

Signal and Dialog-based setup of receive, transmit, request and remote messages (for example, format, identifier, signal

message handling composition, and encoding/decoding)
Loop-back functionality: CAN messages sent by one CAN controller can be made available to the same

CAN controller
Gateway block to transfer messages between two CAN buses unidirectionally or bidirectionally, without message

or signal manipulation (not applicable to DS1103)
Displaying status information on CAN controller

Various options for manipulating signals and messages

Multiple message access: The same CAN messages can be sent and received from within different model subsystems

Block outputs for time stamp information: receive time, transmit time, delta time, delay time

Different sample times and tasks for different messages (each message represented by its own block)

Signal and message handling Custom encoding and decoding for the generation (TX) and verification (RX) of checksums and parity bits

Raw data manipulation directly from Simulink

User defined messages with signal representation

Manipulating CAN signals at model design

Fixed message cycle time

Interrupts Supported interrupts: receive, transmit, request and remote messages, bus off

72
2016

Introduction
Order Information

Real-Time Interface CAN Blockset RTICAN_BS

Application Fields
Required Real-Time Interface
1)
(p. 56) RTI

Microtec C Compiler for DS1005, DS1103 and MicroAutoBox II2) (p. 111) or
CCPPPC

DS1006_COMP

DS1007_COMP

MLBX_COMP


DS1005

DS1006 Processor Board (p. 380) DS1006
Software

DS1007

DS1103 PPC Controller Board (p. 358)
DS1103

DS2202 HIL I/O Board (p. 406)
DS2202

DS2211

DS4302

MicroAutoBox II2) (p. 548)
See p. 522

MicroLabBox
2)
(p. 540) with front panel MLBX_1302F

MicroLabBox2) (p. 540) with top panel
MLBX_1302T

Hardware
1)
2)
Engineering
73
2016

Implementation Software / RTI CAN MultiMessage Blockset

For combining dSPACE systems with CAN communication networks
Highlights
Ideal for handling complex CAN setups

Convenient configuration of extensive CAN setups

Database file import (DBC, FIBEX, AUTOSAR)

CAN FD and partial networking support

J1939 Add-On


The RTI CAN MultiMessage Blockset is an extension for The strong point of the RTI CAN MultiMessage Blockset is
Real-Time Interface (RTI) (p. 56) and can be used for com- handling complex CAN setups, especially in hardware-in-
bining dSPACE systems with CAN communication networks the-loop applications. You can control, configure, and
and for configuring these CAN networks. The RTI CAN manipulate a very high number of CAN messages from one
MultiMessage Blockset and the RTI CAN Blockset (p. 71) single Simulink® block. Not only does handling become very
differ with regard to their features. straightforward, but the size of the model files is also
reduced. This cuts code generation time and build time. CAN
descriptions can easily be read in from communication ma-
trix description files such as database container files
(DBC), ASAM-MCD2D (FIBEX), AUTOSAR System Template
files or ARXML files. CAN, J1939 formats and also the CAN
FD (Flexible Data Rate) protocol with a much higher data
rate and an extended payload data length are supported as
well. These functions make the RTI CAN MultiMessage
Blockset a time-efficient and cost-effective solution for man-
aging complex CAN setups.
Configuration of CAN interfaces Parameters and Messages

Working with large hardware-in-the-loop (HIL) systems Parameters can be directly accessed in ControlDesk® Next
means working with a considerable volume of CAN mes- Generation (p. 120) and AutomationDesk (p. 172) via user
sages. Moreover, the test environments and communication trace files. The CAN Navigator is also supported for easy
matrix (DBC, FIBEX, AUTOSAR) change frequently during handling of CAN configurations, including messages and
the development process. CAN configuration updates in signal manipulation in ControlDesk. Numerous test cases
large models and parameter changes can be done with just can be created via flexible manipulation on message and
a few clicks. 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
74 or signal manipulation. The message transmission and signal
2016
manipulation option can be changed during run time.

Introduction
General Database-file-oriented Simulink blockset for combining dSPACE systems with CAN communication networks

and for configuring these CAN networks
Managing a very high number of messages from one Simulink block

Supports ControlDesk Next Generation Bus Navigator (p. 150)
Application Fields

Support of CAN FD (ISO and Non-ISO)

Support of partial networking

Supports dynamic changes in communication behavior such as signal manipulations and error simulation/detection

Initialization and configuration Importing database files (see below)

Configuring baud rate, sample mode, bit timing parameters, termination resistors, etc.

Supports DBC, FIBEX and AUTOSAR files1)

User-defined database support via custom parser

Multiple database file support allowing simultaneous use of several database files for one model

Supports multiple database file variants that can be switched between during run time

Signal and message handling Multiple, fast, and ECU-dependent selection of transmit and receive messages

Trigger reactions for sending messages as result events for a received message

Software
Message composition read-only (given by database file)

All transmit (TX) messages are received automatically (loop-back) for transmit confirmation

Gateway block to transfer messages between two CAN buses unidirectionally or bidirectionally, without message

or signal manipulation (not applicable to DS1103)
Message transfer between two CAN buses configurable during run time (gateway)

Direct switch from gateway signal to other sources such as counters

Various options for manipulating signals and messages

Providing all messages, signals, and status information via Simulink bus for easy access everywhere in the model

Block outputs for time stamp information: receive time, transmit time, delta time, delay time

Internal
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
Hardware
Different sample times and tasks only for complete bus configurations

No support of remote/request messages

No interrupt handling (e.g., received interrupts)

Signal and message handling Custom CRC functionality

Internal parity calculation

Internal counter

Internal toggle

Custom Code functionality to manipulate raw data or signals

Raw data as input to or output from Simulink

Raw data manipulation from within experiment software (AutomationDesk, ControlDesk)

Configuration of database-independent (“free”) raw messages

Engineering
Capture messages: receiving messages in a given filter range as a stream to Simulink

Changing
CAN signals from experiment software for special signal behaviors such as different counter or
signal values for a defined number of transmissions
Changing CAN messages during run time

Dynamic message triggering: global enabling, spontaneous transmission (kick-out), cyclic message activation, etc.

Message definitions including IDs and lengths changeable at run time

Interrupts No interrupts supported

Supports trigger reactions

Optional: J1939 support J1939 support in RTI CAN MultiMessage Blockset

Support of the J1939 DBC Format

Support of J1939 Network Management (Address Claim)

Support of J1939 Broadcast Announce Messages (BAM)

Support of J1939 Request to Send/Clear to Send (RTS/CTS)

For more information, please contact dSPACE

Please contact dSPACE for appropriate version.

1)
75
2016

Order Information

Real-Time Interface CAN MultiMessage Blockset RTICANMM_BS

Add-On: RTI CAN MultiMessage-J1939 Blockset RTICANMM_J1939_BS


Required Real-Time Interface1) (p. 56) or
RTI

ConfigurationDesk (p. 48)
CFD_I_xxx

Microtec C Compiler for DS1005, DS1103 and MicroAutoBox II
2)
(p. 548) or CCPPPC
DS1006_COMP

DS1007_COMP

MLBX_COMP

Optional ControlDesk Next Generation with Bus Navigator Module
See p. 120

AutomationDesk
See p. 172


DS1005

DS1006

DS1007

DS1103 PPC Controller Board (p. 358)
DS1103

DS2202

DS2211

DS4302

DS4342 CAN FD Interface Module (p. 451)
DS4342

See p. 548

n MicroLabBox 2)
(p. 540) with front panel n MLBX_1302F
n MicroLabBox2) (p. 540) with top panel n MLBX_1302T
SCALEXIO Processing Unit (p. 328)
See p. 328

DS2671 (p. 348)
DS2671

DS2680 I/O Unit (with bus support) (p. 330)
DS2680_2672

1)
2)
76
2016

Implementation Software / RTI LIN MultiMessage Blockset
Introduction
For combining dSPACE systems with LIN communication networks
Highlights
Application Fields
Convenient configuration of LIN setups

For rapid control prototyping and hardware-in-the-loop

simulation
Database file import (LDF, DBC, AUTOSAR)

LIN raw data access

Software
The RTI LIN MultiMessage Blockset is an extension for Real- The strong point of the RTI LIN MultiMessage Blockset is
Time Interface and can be used for combining dSPACE sys- handling complex LIN setups, allowing you to control and
tems with LIN communication networks and for configuring configure all unconditional and event-triggered LIN frames
these LIN networks. from one single Simulink® block (configuration via database
file). LIN configurations can easily be read in from commu-
nication matrix description files such as LDF, DBC, FIBEX and
AUTOSAR System Template.
Hardware
General Databasefileoriented Simulink blockset for combining dSPACE systems with LIN communication networks and

for configuring these LIN networks
One Simulink block per bus configuration

Engineering
Signal initialization/configuration 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)

Node configuration 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

1)
77
2016

Frames Setting receive and transmit messages

Encoding input signals from the Simulink model as raw data and transmitting the raw data to the LIN bus

Decoding raw data and providing physical signals as outputs

Manipulating raw data, for example, using checksums, toggling bits, inserting parity bits

Support of event-triggered frames

Changing frame length during run-time and dynamically

Special run-time frame manipulation features: suppress response for n frames, corrupt LIN frame checksum for n frames

Capturing frames not defined in LDF file or model

Online switching between raw and signal data inputs

Special signal generation: counter, in-data user checksum

Bus events Energy saving modes (sleep/wake-up)

Sending wake-up and sleep requests

Schedule is always restarted with first frame in schedule

Fixed response time, manipulation of baudrate, break length, break delimiter, and LIN frame checksum

No interrupt support

LIN slave tasks Classic or enhanced checksum

Unconditional frames

Event-triggered frames

LIN master tasks Sending wakeup and sleep commands

Diagnostic frames (no diagnostic commands supported)

Go-to-sleep without sending sleep command

Further manipulation options Online source switch for each signal: input, counter, constant, signal error value (for manual and automated tests)

Enable saturation of signal-in ports

Handling characteristics Graphical “one-for-all” configuration interface

Interface to Simulink via bus selectors

User defined, automatically generated mapping

Generation of Simulink input ports for non-mapped signals

Generation of frame based ControlDesk® Next Generation layouts with Bus Navigator

Order Information

Real-Time Interface LIN MultiMessage Blockset RTILINMM_BS

78
2016

Introduction

Required Real-Time Interface1) (p. 56) or
RTI

CFD_I_xxx

Microtec C Compiler (p. 111) for DS1005 and
CCPPPC

Application Fields
MicroAutoBox II2) or
DS1006_COMP

DS1007_COMP

Optional ControlDesk Next Generation with Bus Navigator Module See p. 120


DS1005

DS1006

DS1007

DS4330 LIN Interface Board (p. 445)
DS4330

Software
See p. 548

See p. 328

DS2671 (p. 348)
DS2671

DS2680_2672

DS6301 CAN/LIN Board
DS6301

1)
2)
Hardware
Engineering
79
2016

Implementation Software / dSPACE FlexRay Configuration Package
dSPACE FlexRay Configuration Package

Configuring dSPACE systems in FlexRay networks
Highlights
Integrating dSPACE systems as simulation or

monitoring nodes in a FlexRay network
Efficient configuration of FlexRay simulations

For rapid control prototyping and hardware-in-the-

loop simulation, including restbus simulation
Blockset for creating application-specific

Simulink® models
Protocol data unit (PDU) support


The dSPACE FlexRay Configuration Package is used to inte- The dSPACE FlexRay Configuration Package is an extensive
grate dSPACE hardware as simulation or monitoring nodes solution for using FlexRay in dSPACE’s real time systems.
in a FlexRay network. Nodes are configured with the dSPACE The package makes FlexRay configurations easy and hides
FlexRay Configuration Tool according to a communication much of FlexRay’s complexity. Configuration settings can
matrix containing scheduling information for signals and be stored as and exchanged with project files. The dSPACE
frames transmitted via the FlexRay bus. The communication FlexRay Configuration Package has been designed in close
information is linked to a MATLAB®/Simulink model via the cooperation with advanced users of the FlexRay protocol to
RTI FlexRay Configuration Blockset. The resulting FlexRay ensure it meets your requirements.
application can be executed on a dSPACE system.
dSPACE FlexRay Configuration Tool RTI FlexRay Configuration Blockset

The dSPACE FlexRay Configuration Tool lets you configure Application-specific Simulink models can be created using
a dSPACE system as a simulation node in a FlexRay network. the RTI FlexRay Configuration Blockset as a basis. The block
It relies on the network and scheduling data available in a attributes are filled with data generated by the dSPACE
FIBEX or AUTOSAR XML representation. Numerous consis- FlexRay Configuration Tool. The blockset contains addi-
tency checks are performed when the communication de- tional blocks that can be used for task execution control,
scription is imported. Various views help in managing the interrupt and error handling, status information, and
FlexRay configuration. The tool generates the communica- controller reset. The RTI FlexRay Configuration Blockset
tion code and controller configuration. supports the sending and receiving of protocol data units
(PDUs), which are also used in AUTOSAR. Such units com-
prise several signals, which can be handled in the model
using only one Simulink block per PDU.
80
2016

Introduction
dSPACE FlexRay Configuration Tool
Importing communication descriptions 1)
Reads communication descriptions for FlexRay and validates via plausibility checks

Ignores irrelevant data

Support of various FIBEX versions2)

Support of various AUTOSAR System Template versions2)
Application Fields

Handling Hierarchical view of the communication description

Visualizes parameters

Filter and view options, as well as search masks for handling larger descriptions

Generates a report for the present configuration

Signal and frame selection Select
signals, PDUs and frames for creating blocks with the RTI FlexRay Configuration Blockset
(for use in simulation)
All the frames sent to a real ECU are automatically identified and configured for simulation (restbus simulation)

PDU handling PDU update bit manipulation

Alive counter for PDUs

CRC check for PDUs by user CRC C-code file

Raw data access for PDUs

Software
Frame handling Raw data access for frames with or without signals

CRC check for frames by user CRC C-code file

Enable/disable static frames via software: A null frame or old value (CHI Code option) is send

Enable/disable buffers of static slots via hardware: There is no bus activity in the slots

Task configuration Generate and configure communication tasks automatically or manually and according to the selected

signals, PDUs and frames
Consistency checks for eliminating invalid configurations in tasks

Configure dSPACE hardware, including the connected FlexRay communication controllers

1)
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.
Hardware
2)
RTI FlexRay Configuration Blockset
Model generation Generates MATLAB/Simulink blocks for FlexRay communication

Combine the model frames with application models, for example, for function prototyping or restbus simulation

Blocks for FlexRay controllers, tasks, and synchronization settings

Trigger blocks for dynamic frames

Engineering
Blocks for sending and receiving protocol data units (PDUs)

Simulation stage Use a dSPACE platform as a monitoring or simulation node in a FlexRay communication system
81
2016

Order Information

dSPACE FlexRay Configuration Package FCP

FlexRay Configuration Blockset (included with dSPACE FlexRay Configuration Package) RTIFLEXRAY_CONF_BS

dSPACE FlexRay Configuration Tool (included with dSPACE FlexRay Configuration Package) FLEXRAY_CONF_TOOL


1)
(p. 56) or RTI

ConfigurationDesk® (p. 48)
CFD_I_xxx

Microtec C Compiler for DS1005 and MicroAutoBox II (p. 548)
CCPPPC

GNU C compiler for AMD OpteronTM for DS1006
DS1006_COMP

DS1007_COMP

Optional Tools for generating a FlexRay communication matrix2)
–
ControlDesk Next Generation with Bus Navigator Module
See p. 120


Required Interface modules with FlexRay communication controller,
DS4340

such as the DS4340 FlexRay Interface Module3) (p. 450)
for PHS based systems
Optional DS1005 PPC Board4) (p. 376)
DS1005

DS1006 Processor Board4) (p. 380)
DS1006

DS1007 PPC Processor Board
4)
(p. 386) DS1007

See p. 548

See p. 328

DS2671 (p. 348)
DS2671

DS2680_2672

1)
2)
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)
82
2016

Introduction
Working with the FlexRay Configuration Package
Working with dSPACE Tools
dSPACE hardware systems – from MicroAutoBox II to mod- combination with dSPACE‘s RTI blocksets. The models are
ular hardware – can be used for various fields of FlexRay executed on the hardware in real time. Model execution
applications. The systems are equipped with slots for mod- and bus access are synchronized. The results can be visual-
ules containing a FlexRay communication controller. The ized in an experiment environment such as ControlDesk®.
application models are created in MATLAB®/Simulink® in
Application Fields
dSPACE FlexRay RTI FlexRay
Configuration Tool Configuration Blockset
Configuration FlexRay blockset

of signals, frames Generation of for modeling with
and tasks for Simulink MATLAB/Simulink
simulation model frame
Software
Simulation on
FIBEX
dSPACE hardware
AUTOSAR XML
Hardware
Selecting Signals, PDUs and Frames
The dSPACE FlexRay Configuration Tool is the bridge erarchical view. This is combined with additional display and
between the network or system level view and the node- or sorting options, and you can easily select all the PDUs (Pro-
ECU-specific view. After a communication matrix or network tocol Data Units) you want to use in your simulation. If you
description file is imported, the FlexRay network description want to set up a restbus simulation for a single ECU, just
and scheduling data are displayed in a clearly arranged hi- select the ECU and let the tool look up all the PDUs sent to it.
Engineering
83
2016

Creating a Task Schedule

You can create a task schedule by selecting signals, frames routines. Alternatively, you have full control to define it
for FIBEX 2.x and PDUs for FIBEX 3.x and AUTOSAR. The manually. When you do so, various checks are performed
schedule includes communication routines for sending and in the background to ensure the task schedule you define
receiving FlexRay frames, for both the static and the dy- is consistent. The third and final category of tasks covers
namic parts of the communication cycle. It also covers ap- the synchronization task. This is executed at the end of each
plication tasks for your functional or restbus simulation application cycle to align task execution to the global time
models. The task schedule can be derived automatically on the FlexRay bus.
according to a fixed scheme for positioning communication
Code Generation Creating the FlexRay Model

The configuration tool has been given all the information You can now take the results of the configuration tool,
it needs to generate the actual communication code and which acts as a kind of preprocessor tool, and continue with
the settings for initializing the FlexRay controller. The tool the usual model-based design flow. When a FlexRay model
also calculates the required number of FlexRay controllers, is created for the first time, blocks from the RTI FlexRay
taking into account the available communication buffers, Configuration Blockset library are copied to the model and
and startup and synchronization behavior. The code gen- their parameter values are set automatically according to
erator is prepared to support Freescale and Bosch E-Ray the configuration data that was generated previously. The
controller implementations for FlexRay1). 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)
84
2016

Introduction
Modifying the Model
Later on, you will most likely face modifications to the com- FlexRay application model is compiled for execution on a
munication description file, representing new integration dSPACE hardware system. The driver and initialization code
stages in the vehicle project. To preserve the modeling results of the configuration tool is integrated during this build
already obtained, the RTI FlexRay Configuration Blockset process. The generated code is downloaded to the dSPACE
comes with an update mechanism for handling changes in hardware and acts as a full-fledged node in the FlexRay
Application Fields
the configuration data, for example, introducing new signal network, sending and receiving FlexRay frames in real time.
and PDU blocks and discarding old ones. The resulting
Selected Failure Simulation Methods

Failure and restart of a FlexRay controller Alive counter manipulation via TRC file

Enable/disable transmission of a static frame Change CRC algorithms at run time

Enable/disable transmission of a cyclic dynamic Send and receive invalid signals

Software
FlexRay frame Simulate synchronization service breakdown

Enable/disable all event-based dynamic FlexRay frames Simulate time-triggered task execution breakdown

Enable/disable all cyclic FlexRay frames with optional restart at correct synchronization
(a null frame or old value is sent)
Hardware
Engineering
85
2016

Implementation Software / RTI AUTOSAR Blockset
RTI AUTOSAR Blockset

MATLAB®/Simulink®- and AUTOSAR-based co-development,
validation and prototyping on MicroAutoBox® II
Highlights
Combination of AUTOSAR software development

and model-based controller design in MATLAB/
Simulink
Support of virtual ECUs (V-ECUs) for software

validation and rapid control prototyping
Dedicated AUTOSAR operating system (OS) with a

comprehensive feature set
Seamless workflow from offline simulation to rapid

control prototyping to production software
development for target ECUs

The RTI AUTOSAR Blockset is an extension to Real-Time The RTI AUTOSAR Blockset lets you import AUTOSAR
Interface (RTI) with a focus on rapid control prototyping, software from SystemDesk® into MATLAB/Simulink in the
and ECU software testing and validation. form of virtual ECUs (V-ECUs) and use it on MicroAutoBox II.
You can use it to execute AUTOSAR software, from indi- V-ECUs are realistic representations of future ECU software.
vidual AUTOSAR SWCs to entire virtual AUTOSAR ECUs, on By using the RTI I/O libraries, the V-ECU can use the power-
dSPACE’s compact, in-vehicle-capable real-time system Mi- ful and flexible I/O of MicroAutoBox II. The model-based
croAutoBox II. These are some typical application scenarios configuration of the I/O blocks makes setting up a V-ECU
for the blockset: with physical I/Os quick and easy. Because of its compre-
Prototyping and evaluating new Simulink control hensive I/O range, the same MicroAutoBox II can be
algorithms that include existing AUTOSAR software equipped with different V-ECUs to stand in for a multitude
components (SWCs) of AUTOSAR ECUs.
Testing and validating AUTOSAR software under real- The RTI AUTOSAR Blockset brings with it a dedicated
time conditions before the target ECU becomes AUTOSAR OS for MicroAutoBox II. This OS supports
available AUTOSAR versions 3.x and 4.x. It conforms to AUTOSAR
Testing and validating AUTOSAR software together OS Conformance Class 1, ensuring a high level of com
with the physical plant, in the laboratory or in the patibility. By supporting advanced OS concepts, such as
vehicle extended tasks, the OS enables a powerful real-time
Preparing AUTOSAR-based ECU demonstrators execution of AUTOSAR software that closely resembles the
without access to the final target ECU behavior of production-grade target ECUs. The OS lets you
Testing outsourced AUTOSAR SWCs before they are test real-time aspects of the software even before
integrated into the production ECU software prototypes of a target ECU become available.
86
2016

Introduction
AUTOSAR OS on MicroAutoBox II Realtimecapable, preemptive AUTOSAR OS

Automatic configuration of OS and BSW services

Conforms to AUTOSAR Conformance Class 1 and comprises:

Application Fields
Full OSEK OS conformance (all conformance classes)

Support of all OSEK APIs

AUTOSAR Counter Interface

AUTOSAR Software Free Running Timer Interface (SWFRT)

AUTOSAR Schedule Tables

AUTOSAR Stack Monitoring

Measurement and calibration Synchronized measurement of Simulink signals and global VECU variables in parallel

Standard ASAM A2L file support

Extended measurement, calibration and debugging possibilities compared to RTEs on productiongrade

target ECUs to allow tracking RTE communication
Basis Software (BSW) Services ECU State Manager (EcuM)

NV RAM Manager (NvM)

Software
AUTOSAR CAN stack

Supported AUTOSAR versions Versions 3.1, 3.2

Versions 4.0.3 , 4.1.1, 4.1.2

Support for bypassing The RTI AUTOSAR Blockset prepares imported VECUs for virtual bypassing on MicroAutoBox II (see p. 548).
Working with AUTOSAR on MicroAutoBox II

The RTI AUTOSAR Blockset lets you import AUTOSAR soft- such as digital or analog input and output ports with pro-
Hardware
ware from SystemDesk into MATLAB/Simulink in the form duction tools is often a very complex and error-prone task.
of virtual ECUs (V-ECUs) and use it on MicroAutoBox II. The model-based I/O configuration with the dSPACE RTI I/O
V-ECUs comprise AUTOSAR application software, the AU- blocksets makes setting up a V-ECU with physical I/Os quick
TOSAR Runtime Environment (RTE), AUTOSAR Basic Soft- and easy. Its comprehensive range of I/O lets you adapt
ware (BSW) and OS configurations. MicroAutoBox II to a wide range of ECUs.
The RTI AUTOSAR Blockset automatically configures the In combination with the RTI AUTOSAR Blockset, MicroAuto-
AUTOSAR OS and the BSW services on MicroAutoBox II Box II can therefore flexibly stand in for a multitude of
according to the configuration settings. For instance, the different AUTOSAR ECUs – long before physical prototypes
AUTOSAR CAN stack is configured automatically based on of an ECU become available.
Engineering
the configuration you made in SystemDesk. Configuring I/O
SystemDesk
AUTOSAR SWCs (V-ECU generation) RTI AUTOSAR Blockset MicroAutoBox II
XML
.c
.h
V-ECU
87
2016

A Seamless Development Tool Chain

dSPACE offers a seamless tool chain for working with Blockset. Real-time-specific parts of the software behavior
AUTOSAR software. This tool chain consists of the dSPACE can thus be tested and the V-ECU can be validated under
tools TargetLink, SystemDesk®, VEOS®, and the RTI AUTO- realistic operating conditions. With this approach, the be-
SAR Blockset for MicroAutoBox II. havior of AUTOSAR software can be prototyped together
AUTOSAR SWCs are the building blocks of AUTOSAR soft- with a physical plant in the laboratory, and experienced
ware and can be developed in various ways. They can, for directly in the vehicle.
instance, be created manually as C source code. Or they In addition, when you use the virtual bypass method, the
can be developed with a model-based production code RTI Bypass blockset lets you optimize and enhance certain
generator such as dSPACE TargetLink. aspects of a V-ECU. For example, you can replace individu-
With SystemDesk, SWCs can be imported and combined al functions and runnables with new Simulink models.
into an AUTOSAR application software. In addition, System- Hence, you can evaluate and test the behavior of new
Desk lets you model entire software architectures, configure Simulink models in the context of an existing ECU software
the corresponding AUTOSAR OS and BSW services, gener- early on (see RTI Bypass Blockset, p. 64).
ate an RTE and export them as V-ECUs. This tool chain covers all phases of function and software
Such V-ECUs can be run and tested on a PC in the simula- development, from control design to software architecture
tor dSPACE VEOS to validate functional properties of the definition and integration, from offline simulation to in-
software. The same V-ECU can also be executed without vehicle RCP. The continuous use of ControlDesk® Next Ge-
modifications on MicroAutoBox II by using the RTI AUTOSAR neration leverages synergies, because the same measure-
ment and calibration data and experiment layouts can be
used across all platforms, and even in the production ECU.
AUTOSAR SWCs SystemDesk
XML
.c
.h
V-ECU
TargetLink/ MicroAutoBox II with Production ECU &

VEOS
Simulink RTI AUTOSAR Blockset basic software tools
PC-based Rapid Control Production

Function Design
Simulation Prototyping Software Integration
88
2016

Introduction
Order Information

RTI AUTOSAR Blockset RTI_AUTOSAR_VECU_BS

Application Fields

RTI

RTI XCP on Ethernet Blockset
RTIETHXCP_BS

RTI Bypass Blockset
RTIBYPASS_BS

SystemDesk V-ECU Generation Module
SYD_GEN

Optional VEOS
See p. 112
TargetLink
See p. 202
ControlDesk Next Generation
See p. 120
Software
RTI CAN Blockset
RTICAN_BS

See p. 74
RTILINMM_BS

FCP

Ethernet Blocksets
See p. 92
SystemDesk Modeling Module
SYD_MOD


Required MicroAutoBox II
See p. 548
Hardware
Engineering
89
2016

Implementation Software / RTI FPGA Programming Blockset
RTI FPGA Programming Blockset

Integrating FPGA models in dSPACE systems
Highlights
Easy connection of FPGA models to

processor models (Simulink®, RTI)
Model-based I/O configuration

Offline simulation in Simulink

Supports various dSPACE FPGA platforms


The RTI FPGA Programming Blockset is a Simulink blockset The dSPACE FPGA platforms provide a Xilinx® FPGA, for which
for using an FPGA model created with the Xilinx® System you can implement an application graphically using the Xilinx®
Generator blockset with a dSPACE system. It provides RTI System Generator in Simulink. The RTI FPGA Programming
blocks for implementing the interface between the FPGA Blockset allows you to integrate the resulting FPGA model in
mounted on a dSPACE board and its I/O, and the interface a Simulink model that runs on dSPACE hardware. The RTI
between the dSPACE FPGA board and its processor board. FPGA Programming Blockset is a convenient way to connect
The blockset can be used with the following dSPACE the I/O board’s I/O driver components and to model the
FPGA platforms, which provide user-programmable FPGAs: connection to a processor-based computation node (DS1005,
DS5203 FPGA Board (p. 462).
DS1006 or DS1007, SCALEXIO Processing Unit, MicroLabBox
DS2655 FPGA Base Board (p. 335).
or MicroAutoBox II). The data exchange supports fixed point
MicroAutoBox II 1401/1511/1514 and 1401/1513/1514 data types as well as floating point data types. Thus, FPGA
(p. 548) extended with a DS1552 Multi I/O Module. programming is seamlessly integrated into the Simulink en-
MicroLabBox (p. 540). vironment. With the FPGA blockset, you can synthesize, build
and program the FPGA or processor directly from Simulink
Typical application scenarios for rapid control prototyping for optimal convenience.
(RCP) and hardware-in-the-loop (HIL) simulation are: Alternatively, the handcode interface lets you program
Projects in automotives, industrial automation, the FPGA boards in VHDL (VHSIC Hardware Description
medical engineering, and aviation Language) or Verilog.
Signal preprocessing, adapting new interfaces,
very fast control loops, designing and testing
new concepts for electrified powertrains
Two worlds integrated: FPGA model components created with

the Xilinx® System Generator blockset and RTI blocks.
90
2016

Implementation Software / RTI FPGA Programming Blockset
Introduction
General Integrating an FPGA model on a dSPACE FPGA platform

I/O configuration

Automatic generation of a processor model template on the basis of a FPGA application

Application Fields
FPGA interface Programming the FPGA with the Xilinx® System Generator

Integrating an FPGA model created with the Xilinx® System Generator

Offline simulation in Simulink

Handcode interface Programming the FPGA in VHDL or Verilog

I/O access Connecting the FPGA model with analog and digital input and output signals with the RTI FPGA Blockset

Processor-FPGA communication Connecting the FPGA model with the processor model running on the computation node

(DS1005, DS1006 or DS1007, SCALEXIO Processing Unit, MicroLabBox or MicroAutoBox II)
Access
types for system bus communication with the dSPACE FPGA platforms:
register, register groups, buffer
Asynchronous tasks Implementing interrupt-driven tasks in the processor model triggered from the FPGA model.

Software
Order Information

RTI FPGA Programming Blockset FPGA Interface or RTIFPGA_BS

RTI FPGA Programming Blockset Handcode Interface RTIFPGA_HC


1)
(p. 56) RTI

Hardware
ConfigurationDesk (for SCALEXIO)
See p. 48

Xilinx® Vivado® Design Suite
Please see www.xilinx.com
Xilinx® System Generator for DSP only for FPGA Interface version (RTIFPGA_BS)

Microtec C Compiler for DS1005 (p. 111) and MicroAutoBox (p. 548)
CCPPPC

DS1006_COMP

DS1007_COMP

MLBX_COMP

Engineering
Optional DS5203 FPGA Board (7K325) or
DS5203_7K325

DS5203 FPGA Board (7K410) (p. 462)
DS5203_7K410

DS1005 PPC Board (p. 376) or
DS1005

DS1006 Processor Board (p. 380) or
DS1006

DS1007

DS2655 FPGA Base Board (p. 335)
DS2655

SCLX_RTPC

MicroAutoBox II 1401/1511/1514 and 1401/1513/1514 (pp. 548-541)

See p. 548

DS1552 Multi I/O Module for MicroAutoBox II (p. 558)
DS1552

MicroLabBox with front panel (p. 540)
MLBX_1302F

MicroLabBox with top panel (p. 540)
MLBX_1302T

1)
91
2016

Implementation Software / Ethernet Blocksets
Ethernet Blocksets
Overview of Ethernet implementation software
Highlights
Connection of dSPACE real-time systems to

Ethernet networks and devices
Convenient configuration of Ethernet setups

For rapid control prototyping (RCP) and

hardware-in-the-loop (HIL) simulation

Ethernet is an integral part of various dSPACE applications Ethernet is a long-established networking technology for the
and solutions, where it is used for communication between most diverse applications that was first used for networking
dSPACE systems and other systems, or for co-simulation local computers. Since its beginnings, the technology has
coupling, etc. It can also be used as a vehicle network or evolved and now offers great features such as flexibility,
bypassing interface. efficient pricing, and accumulated know-how. As an ISO
dSPACE Ethernet implementation software allows custom- Open Systems Interconnection (OSI) model, Ethernet can be
ers to efficiently integrate Ethernet functions into a wide tailored to many different applications, allowing it to enter
range of applications. more fields, such as industrial automation. Today, it is even
being used in the vehicle.
dSPACE Ethernet implementation software offers an easy-
to-use graphical user interface and application-tailored
solutions.
92
2016

Introduction
dSPACE Ethernet
RTI Ethernet Blockset RTI Ethernet (UDP) Blockset
Configuration Package1)
Supported dSPACE DS1007 PPC Processor Board (p. 386)
MicroAutoBox (p. 548)

platforms MicroLabBox (p. 540)
MicroAutoBox II (p. 548)

Application Fields



Additionaly required – LVDS_CAB13/14
–
hardware DS4121, LVDS_CAB14

Purpose Connects DS1007 and MicroLabBox to Connects dSPACE real-time systems to Supports automotive middleware
Ethernet devices. Ethernet devices and networks. SOME/IP.
Supports bypassing applications with Suitable for bypassing. Connects SCALEXIO-based simulator
DS1007-based real-time systems. systems to Ethernet devices and
networks.
SCALEXIO Ethernet Solution DS1006QC Ethernet Solution DS4504 Ethernet Solution
Software
Supported dSPACE Uses the second SCALEXIO® Processing DS1006 Processor Board (p. 380)

platforms Unit´s (p. 328) Ethernet interface. DS1006 Processor Board (p. 380)

Optional: additional 2-Port Ethernet
Package.
Additionaly required – DS921
DS4504, DS4504_ETX, DS381

hardware
Purpose Connects SCALEXIO-based dSPACE Connects DS1006-based modular Connects modular dSPACE real-time

real-time systems to Ethernet devices dSPACE real-time systems to Ethernet systems to Ethernet devices and

and networks. devices and networks. networks.

Hardware
1)
For more information, please see p. 96
Engineering
93
2016

Technical Features RTI Ethernet Blockset RTI Ethernet (UDP) Blockset dSPACE Ethernet Configuration Package
Ethernet standard 10/100/1000 Mb/s 100/1000 Mb/s 10/100/1000 Mb/s
(MABX II);
10/100 Mbit/s (DS4121, LVDS_CAB14)
Protocols UDP/IP, TCP/IP UDP/IP UDP/IP
Maximum number of sockets 256 4 96 receive, 96 transmit
Supported middleware – – SOME/IP
IP fragmentation Yes No –
Maximum payload of UDP 65507 bytes 1472 bytes –
datagram
Operation modes Full duplex/half duplex Full duplex –
Auto-MDIX Yes Yes –
DHCP client Yes No –
Dynamic change of Yes (UDP/IP) No –
destination address
Receive/transmit queue Yes/Yes Yes/Yes –
Send broadcast messages Yes No –
Technical Features SCALEXIO Ethernet Solution DS1006QC Ethernet Solution DS4504 Ethernet Solution
Ethernet standard 10/100/1000 Mb/s 10/100/1000 Mb/s 10/100 Mb/s
Protocols UDP/IP, TCP/IP UDP/IP, TCP/IP UDP/IP, TCP/IP

Maximum number of sockets 65535 96 receive, 96 transmit 96 receive, 96 transmit
Supported middleware – – –
IP fragmentation Yes Yes Yes
Maximum payload of UDP 65507 bytes (UDP/IP) 65507 bytes 65507 bytes
datagram
Operation modes Full duplex/half duplex Full duplex/half duplex Full duplex/half duplex
Auto-MDIX Yes Yes No
DHCP client Yes Yes Yes
Dynamic change of Yes (UDP/IP, TCP/IP) Yes (UDP/IP, TCP/IP) Yes (UDP/IP, TCP/IP)
destination address
Receive/transmit queue Yes/Yes Yes/No Yes/No
Send broadcast messages Yes Yes Yes
94
2016

Introduction
Order Information

RTI Ethernet Blockset RTI_ETH_BS

RTI Ethernet (UDP) Blockset RTI_ETH/UDP_BS

dSPACE Ethernet Configuration Package1) ECP

Application Fields
SCALEXIO Ethernet Solution SCLX_ETH_SOL

DS1006QC Ethernet Solution DS1006QC_ETH_SOL

DS4504 ETH Solution DS4504_ETH_SOL

1)
For more information, please see p. 96
For information about our 10 Mb/s Ethernet Interface

please see p. 499.
Software
Hardware
Engineering
95
2016

Implementation Software / dSPACE Ethernet Configuration Package
dSPACE Ethernet Configuration Package

For combining SCALEXIO® systems with Ethernet SOME/IP networks
Highlights
Enables the simulation of service-oriented, event-

based Ethernet communication in real-time systems
Supports SOME/IP middleware

Supports FIBEX 4 communication descriptions


The Ethernet Configuration Package enables the real-time The Ethernet Configuration Package consists of two parts.
simulation of service-oriented communication in Ethernet The first part is the dSPACE Ethernet Configuration Tool,
networks of electronic control units (ECUs). These networks which is used to configure a dSPACE system as a simu-
play an important role in modern driver assistance systems, lation node in a service-oriented Ethernet network. The
new comfort and entertainment functions, and numerous second part is the dSPACE Ethernet Configuration Blockset,
other functionalities. used for modeling the service-oriented communication in
With the dSPACE Ethernet Configuration Package, you can MATLAB®/Simulink®.
configure a dSPACE system as a simulation node in a service- A unique Multi-MAC (Media Access Control) simulation
oriented Ethernet network. feature lets you simulate several Ethernet nodes with one
port of the dSPACE system.
dSPACE Ethernet Configuration Tool dSPACE Ethernet Configuration Blockset

The dSPACE Ethernet Configuration Tool lets you configure Application-specific Simulink models can be created using
a dSPACE system as a simulation node in an Ethernet SOME/IP the dSPACE Ethernet Configuration Blockset as a basis. The
(scalable service-oriented middleware over IP) network. The block attributes are filled with data generated by the dSPACE
tool relies on a network description file available in a FIBEX Ethernet Configuration Blockset. The dSPACE Ethernet Con-
XML representation. Numerous consistency checks are per- figuration Blockset supports sending and receiving events.
formed when the communication description is imported. Such units comprise several signals, which can be handled
You can configure the network simulation based on the in the model by using only one Simulink block per event.
imported description via drag & drop. The tool generates
the communication code and a blockset generation file
according to this configuration.
96
2016

Implementation Software / dSPACE Ethernet Configuration Package
Introduction
dSPACE Ethernet Configuration Tool
General Support of Ethernet SOME/IP

Application Fields
Support of SOME/IP Service Discovery

Handling Hierarchical view of the communication description

Parameter visualization

Import communication description FIBEX
4.0 extended draft
FIBEX
4.1
FIBEX 4.1.1

Configuration Selectable clusters, nodes, services, event groups, and parameters

Multi-MAC simulation (for simulating several Ethernet nodes with one port of the dSPACE system)

Support of end-to-end communication protection

UDP network management

Service discovery manipulation options

Software
dSPACE Ethernet Configuration Blockset
Simulation Use a dSPACE SCALEXIO platform as a simulation node in an Ethernet SOME/IP communication network

Model generation Generation of MATLAB/Simulink blocks for SOME/IP communication

Use blocks to send and receive SOME/IP events

Use structured blocksets with basic configurations, service instances, and additional convenient functions

(e.g., model update)
Hardware
Order Information

dSPACE Ethernet Configuration Tool ETH_CONF_TOOL

dSPACE Ethernet Configuration Blockset ETH_CONF_BS

dSPACE Ethernet Configuration Package ECP

Engineering

Required ConfigurationDesk
CFD_I_xxx


Optional SCALEXIO Processing Unit See p. 328

97
2016

Implementation Software / ADASIS v2 HR Blockset
ADASIS v2 Horizon Reconstructor Blockset

Developing and testing mapbased driver assistance systems using the ADASIS v2 protocol
Highlights
Simulink® blockset for accessing electronic horizon

data via the ADASIS v2 protocol
Graphical selection of predictive road data for easier

development of map-based driver assistance
functions
Ready-to-use model blocks for road profiles,

intersections, stubs, and protocol metadata
Same reconstructor code as for production ECUs

from Elektrobit

Advanced driver assistance systems (ADAS) such as predic- Using the ADASIS v2 Horizon Reconstructor Blockset to-
tive powertrain control, curve lights and curve warnings use gether with the dSPACE PC-based simulation platform
predictive road data, called the “electronic horizon”, which VEOS®, the MicroAutoBox or AutoBox rapid prototyping
is calculated from digital road maps and from the vehicle’s system, you can develop driver assistance systems in short
current position and driving direction. iteration cycles and directly experience their effects on a PC
To facilitate the development and implementation of such or in the real vehicle.
driver assistance systems, the ADASIS Forum (www.ertico. Only a few mouse clicks are needed to select the predictive
com/adasisforum) specified the ADASIS v2 standard for the road data, connect it to the driver assistance function in
transmission of electronic horizon data. The ADASIS v2 the model, and generate the code and load it to the
Horizon Reconstructor Blockset lets you access the elec- development system. So function developers can give their
tronic horizon data from within a Simulink model, so you full attention to implementing the actual ADAS application
can use it during function development without having to without the time-consuming task of implementing the
implement the protocol yourself. 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.
98
2016

Implementation Software / ADASIS v2 HR Blockset
Introduction
General Access to the electronic horizon data from within a Simulink® model (e.g., to road curvature, slope

and speed limit information)
Graphical selection of predictive road data for connection to the actual driver assistance functions in

Application Fields
the Simulink model
Independent of the transmisson medium; can be combined with CAN or Ethernet blocksets

Dedicated blocks for road profiles, intersections, stubs, and protocol metadata

ADASIS v2 reconstructor code for target ECUs from Elektrobit

Order Information

ADASIS v2 Horizon Reconstructor Blockset ADASISV2HR_BS

Software

Optional Real-Time Interface1) (p. 56)
RTI

dSPACE VEOS
See p. 112

DS1005

DS1006

Hardware
DS1007

MicroAutoBox II2)
(p. 548) See p. 548
SCALEXIO®
See p. 318
1)
2)
Various MicroAutoBox variants are available.
Engineering
99
2016

Implementation Software / V2X Solution
NEW: V2X Solution

Developing and testing V2X applications
Highlights
Simulink blockset for easy access to V2X communi-

cation according to the IEEE 802.11p standard
Access to V2X message contents within the

Simulink model
Graphical selection of relevant V2X signals

Dedicated map instrument for analyzing the traffic

situation and V2X-specific information

V2X (Vehicle-to-X) technology enables the exchange of data The dSPACE V2X Blockset for Simulink® is a central compo-
between vehicles and between vehicles and the infrastruc- nent of the V2X Solution and lets engineers easily access
ture via wireless ad-hoc networks according to the IEEE WLAN ad-hoc communication according to IEEE 802.11p
802.11p standard. The network participants send mes- during rapid control prototyping and model-in-the-loop
sages that include information about details such as their (MIL), software-in-the-loop (SIL) and hardware-in-the-loop
position, speed and driving direction or events such as (HIL) simulation. In only a few steps, developers can connect
traffic jams. In Europe, the CAR 2 CAR Communication their applications directly to the appropriate communication
Consortium (C2C-CC) cooperates closely with standardiza- blocks via signal vectors, which gives them access to all or
tion organizations ETSI (European Telecommunications Stan- previously selected V2X message contents. Implemented
dards Institute) and CEN (Comité Européen de Normalisa- protocols and software layers help perform further steps
tion) to develop joint communication standards. The dSPACE according to current V2X standards. These layers include
V2X Solution facilitates the easy access to V2X communica- encoding and decoding V2X messages and the communica-
tion from Simulink and graphical analysis of V2X data. tion interface to a V2X hardware adapter via the Basic
Engineers can focus entirely on developing and testing the Transport Protocol. The direct access to all V2X signals
actual V2X applications without having to implement the within the model also simplifies the necessary data ma-
required V2X-specific protocols and software layers them- nipulation during robustness tests and the map instrument
selves. in ControlDesk allows an easy analysis of the corresponding
effects. All this takes work off the developers so that they
can focus completely on developing and testing their ap-
plications.
100
2016

Introduction
V2X communication Access to WLAN-based ad-hoc networks from within a Simulink model according to IEEE 802.11p and ETSI

Intelligent Transport Systems (ITS) standards
V2X message contents provided as signal vectors for V2X applications

Application Fields
Graphical selection of specific message contents required for V2X applications

Encoder and decoder blocks for Cooperative Awareness Messages (CAMs) and Decentralized Environmental

Notification Messages (DENMs), derived from the Abstract Syntax Notation One (ASN.1) protocol description files
Bidirectional exchange of V2X messages between a simulation platform and a suitable V2X hardware

adapter via the Basic Transport Protocol (BTP)
Local Dynamic Map (LDM) for storing and filtering incoming V2X messages and distributing relevant

message contents to individual applications
Positioning and timing Dedicated blocks for encoding and decoding Global Navigation Satellite System (GNSS) data according to the NMEA
0183 standard by the National Marine Electronics Association
Visualization Map-based
instrument for dSPACE ControlDesk® Next Generation
Most
recent traffic situation and the latest V2X-specific information provided by the LDM
User-configurable content

Supported V2X hardware adapter MK5-OBU by Cohda Wireless
Software

Further hardware support on request

Order Information

V2X Solution V2X_SOL

Hardware

Optional RTI Ethernet (UDP) Blockset
RTI_ETH/UDP_BS

RTI Ethernet Blockset
RTI_ETH_BS

DS1006QC Ethernet Solution
DS1006QC_ETH_SOL

SCALEXIO Ethernet Solution
SCLX_ETH_SOL

VEOS
VEOS_BASE

Engineering
Required MK5-OBU by Cohda Wireless
V2X_MK5

Optional MicroAutoBox II
See
p. 548
MicroLabBox
See
p. 540
DS1006 Processor Board
DS1006

DS1007 PPC Processor board
DS1007

SCALEXIO®
See
p. 318
101
2016

Easy Access to V2X Communication

The V2X blockset provides dedicated blocks for handling ControlDesk
Map instrument
V2X messages. The contents of each message are provided
as signal vectors in Simulink. Users can configure a filter for
V2X signals, so only the message contents that are relevant V2X application
for an application are displayed in the modeling environ- Signal vectors
ment. The coding and decoding blocks are derived from the
Simulink Model
LDM
V2X Blockset
ASN.1 description files standardized by ETSI. Incoming V2X
messages are stored in the LDM and the relevant message CAM/DENM CAM/DENM
contents can be distributed to individual V2X applications. Encoding Decoding
The Simulink model is connected to the radio channel via

NMEA 0183 Transport
Ethernet and a suitable V2X hardware adapter, such as the Decoding BTP
MK5-OBU by Cohda Wireless. In addition to the V2X-spe-
cific blocks the V2X Solution offers a dedicated blockset for Position and time V2X messages
encoding and decoding GNSS data according to the NMEA Ethernet

UDP/IP
0183 standard.
Overview of V2X communication with the V2X hardware adapter
dSPACE V2X Blockset and ControlDesk Next Generation.
V2X Map Instrument in dSPACE

ControlDesk Next Generation.
Visualization and Data Analysis in ControlDesk

Next Generation
The V2X Solution extends dSPACE ControlDesk with a spe- and classification of individual traffic participants and other
cific map instrument, which is continuously updated with V2X-specific information. The configurable map instrument
new data from the LDM. The map instrument therefore lets you conveniently perform data analysis and plausibility
always displays the same contents that are available to the checks for V2X applications.
V2X applications like the position, velocity, driving direction
102
2016

Introduction
Tool Chain Overview
Application Fields
V2X Blockset in Simulink® ControlDesk
 CAM/DENM/BTP/LDM  Data logging/analysis
 NMEA 0183  Data manipulation
 Integration in ASM  V2X map instrument
Software
MIL/SIL simulation Rapid control prototyping HIL simulation
Ethernet (UDP/IP)
V2X hardware adapter
Source: Cohda Wireless

V2X communication in the
dSPACE tool chain.
Hardware
Engineering
103
2016

Implementation Software / XSG Utils Library
XSG Utils Library

Readytouse function blocks for faster implementation of FPGA models
Highlights
Completely open models for Simulink® and

Xilinx® System Generator (XSG)
Real-time FPGA programming

Wide range of function blocks

For rapid control prototyping (RCP) and

hardware-in-the-loop (HIL) simulation projects

The XSG Utils Library offers users of real-time FPGA appli- The XSG Utils Library contains essential, often needed function
cations enhanced function blocks for implementing their blocks for FPGA programming, similar to standard Simulink®
own projects. The library is completely open and can be functions. The high-quality function blocks are ready-to-use
used in rapid control prototyping (RCP) projects as well as and easy to adapt to your project, so they greatly facilitate
hardware-in-the-loop (HIL) simulation. your FPGA programming. They range from enhanced I/O,
scope, and look-up table functions to an average calculator,
Due to the generic programming, the library can be applied sine generator and wavetable encoder.
to all freely programmable dSPACE real-time FPGA platforms So that you can buy just the function set you need for your
with Xilinx® FPGA. Please see the list of optional hardware own FPGA application, dSPACE offers the XSG Utils Library
on p. 105 for an overview. as a subset of the functions in the XSG Electric Components
Library (p. 271) or XSG ACMC Library (p. 106). Different
dSPACE offers a variable license model: versions of all these libraries are available for developers
XSG Utils Library for developers of FPGA and processor and for users of FPGA applications.
applications The XSG Utils Library offers pre-built custom instruments
XSG Utils Interface Library for users to embed pre-con- that enable a quick access to the most used functions out
figured FPGA applications into existing Simulink models of ControlDesk® Next Generation (p. 120).
Available Function Blocks

Scope Sine Generator

PWM Measurement Discrete PT1

PWM Generator Scaling

Look-up Table Wavetable Encoder

I/O Access Functions APU

Integrator Small Apps

PI Controller Version Info

Average Calculator
104
2016

Implementation Software / XSG Utils Library
Introduction
Technical Details of the Main Functions
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.
Application Fields
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.
Order Information

XSG Utils Interface Library FPGA_XSG_UTILS_IF

Software
XSG Utils Library (includes XSG Utils Interface Library) FPGA_XSG_UTILS

XSG Electric Components Interface Library including XSG Utils Interface Library FPGA_XSG_EC_IF

XSG Electric Components Library including XSG Utils Library and XSG Electric Interface Components Library (p. 271) FPGA_XSG_EC

XSG AC Motor Control Interface Library including XSG Utils Interface Library FPGA_XSG_ACMC_IF

XSG AC Motor Control Library including XSG Utils Library and XSG ACMC Interface Library (p. 106) FPGA_XSG_ACMC

Hardware
Required Real-Time Interface depending on the target See p. 56
ConfigurationDesk for use with DS2655 See p. 48
RTI FPGA Programming Blockset See p. 90
Xilinx® Vivado® 1) Please see www.xilinx.com
Optional ControlDesk® Next Generation See p. 120

Optional DS5203 FPGA Board for use with dSPACE Simulator See p. 462
Engineering
DS2655 FPGA Base Board for use with dSPACE SCALEXIO® See p. 335
MicroAutoBox II with I/O extensions for Simulink-programmable FPGA See p. 548
MicroLabBox See p. 540
Please note that due to the introduction of the Vivado® software, Xilinx® no longer supports the Xilinx System Generator for DSPs
1)
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 105
2016

Implementation Software / XSG AC Motor Control Library
XSG AC Motor Control Library

FPGAbased control design for MicroAutoBox II, MicroLabBox, SCALEXIO and PHSbased systems
Highlights
FPGA library for high-speed electric drive control

High performance position sensor processing

Flexible PWM generation

Connection of diverse position encoders

Examples of controller models for various AC motors

Key Benefits Purpose

The XSG AC Motor Control library is used for high-perfor- The XSG AC Motor Control library lets you program inside
mance e-drive control with sample rates above 50 kHz by the FPGA. This mainly involves the high-performance proces-
performing custom control algorithms or parts of it on an sing of various position sensors and in conjunction with the
FPGA. FPGA library components can be combined freely (e.g. included XSG Utils library (p. 104), the flexible generation
encoder interfaces and PWM) on various FPGA platforms of PWM patterns. You can use the RTI FPGA Programming
with different I/O modules and can also be connected to Blockset (p. 90) to position and combine these components
custom design components. however required.
Features
All library components are open and accessible to users SSI (synchronous serial interface) and SPI (serial peripheral

Incremental encoder processing (TTL or sine) interface) sensor processing
Hall sensor processing Flexible PWM generation (using included XSG Utils library)

Resolver and LVDT processing Small applications and components for control

Examples of controller models for various AC motors

Supported Hardware
System Platform
PHSbased system DS5203 (7K325/7K410)

DS5203 (7K325/7K410) with DS5203M1

MicroAutoBox II DS1514 with DS1552

DS1514 with DS1553

SCALEXIO DS2655 with DS2655M1

MicroLabBox MLBX_1302F (front panel)

MLBX_1302T (top panel)

+ d-current ctrl
KINTEX ®
i d* = 0A u d* u a*
d,q
id -
Order Information
u b*
speed ctrl q-current ctrl
n* i q* u q* u c*
a,b,c
- -
n iq
Product Order Number d,q ia
XSG ACMC Interface Library including FPGA_XSG_ACMC_IF

ib

ic
XSG Utils Interface Library

a,b,c
XSG ACMC Library including XSG Utils Library FPGA_XSG_ACMC

and XSG ACMC Interface Library
106
2016

Implementation Software / XSG Advanced Engine Control Library
NEW: XSG Advanced Engine Control Library
Introduction
FPGA library for cylinder pressure indication and incycle control of combustion engines
Highlights
Application Fields
Controlled intervention in active combustion cycle and

hence immediate reaction to abnormal combustion
Support for various types of combustion engines

Numerous ready-to-use engine control elements

Model-based FPGA programming

Open XSG Blockset

Software
The XSG Advanced Engine Control Library gives you numer- The XSG Advanced Engine Control Library lets you imple-
ous ready-to-use, configurable elements for common engine ment controller features in both the CPU and the FPGA of
control functionalities like crank and cam signal processing, various dSPACE real-time systems. Due to the ready-to-use
ignition and injection control, or even cylinder pressure in- engine control functionalities, you do not have to deal with
dication. This way, the in-cycle control of combustion en- complex signal preprocessing and can fully concentrate on
gines is available for rapid control prototyping, enabling a developing new control algorithms. The Advanced Engine
controlled intervention in the combustion process within a Control Library is designed as an open XSG Blockset that
Hardware
few microseconds. gives you detailed insights into the algorithms and lets you
modify them where necessary.
Features
Real-time cylinder pressure indication

Processor High-level
Injection and ignition multipulse generation controller,
uses data
Crank-/cam-based angular computation unit
Control
from last com-
(out-of-cycle)
Incremental encoder processing
bustion cycle
IMEP, QB, MFB, etc. φinj, Tinj, φign, Tign
Auxiliary components (angle transformations, angle-based

pulses, interrupts, RapidPro interfaces)
Engineering
CPI I&I
XSG Utils Library (p. 104) included
p
Supported Hardware Low-level

Control controller,
Angle (in-cycle) corrects
System Platform injection and
Crank/cam ACU ignition
MicroAutoBox II DS1514 with DS1552
during
active cycle
RapidPro RapidPro Power Unit

FPGA
PHSbased system DS5203 (7K325/7K410)

DS5203 (7K325/7K410) with DS5203M1

Order Information

NEW: XSG Advanced Engine Control Library (including XSG Utils Library) FPGA_XSG_ENGCON

107
2016

Implementation Software / Electrical Power Systems Simulation Package
NEW: Electrical Power Systems Simulation Package

Easy real-time simulation of power electronics circuits developed with SimPowerSystems™
Highlights
Real-time simulation of SimPowerSystems™ circuits for

hardware-in-the-loop applications
Processor-based approach for mid-latency simulation

down to 20 µs simulation step size
FPGA-based approach for low-latency simulation with

less than 2.5 µs simulation step size

The dSPACE Electrical Power Systems Simulation Package For processor-based simulation, there are mean value models
allows the real-time simulation of electrical models devel- for bridge circuits used in power electronics to assure pre-
oped in SimPowerSystems™. The package provides various cise simulation of power semiconductor switching devices.
ways to integrate SimPowerSystems™ models in a dSPACE Library functions for easy integration of multirate systems
hardware-in-the-loop (HIL) environment, e.g.: help avoid interference effects.
DC/DC converters For FPGA-based simulation, there are preconfigured FPGA
Rectifiers and inverters applications to allow easy integration without time-consum-
Microgrids ing FPGA synthesis. In particular, no FPGA-specific software
Wind/solar converters is required.
The speed of both simulation types is increased by precal-
Using the processor-based approach, a library containing culating the model states. By providing model separation
equivalent models for power electronics is available for modi- (model splitting), the package lets you use multiple dSPACE
fying a SimPowerSystems™ model to allow real-time-capable real-time platforms simultaneously for computation.
code generation on dSPACE real-time processors by means
of Simulink Coder™. The FPGA-based approach involves
configuring a ready-to-use FPGA application according to
the given SimPowerSystems™ model. This achieves low
latency HIL simulation.
108
2016

Introduction
General n Ready-to-use FPGA applications provided for FPGA-based approach
n Automatic code generation for dSPACE real-time platforms
n Model analysis tools for enhanced usability
Application Fields
n Supports a combination of FPGA- and processor-based simulation for simulating large distributed systems
Processor-based approach n Standard SimPowerSystemsTM components for linear parts and slow-switching semiconductors, such as rectifiers
n Mean value models for fast-switching semiconductors and connecting to dSPACE I/O channels for PWM measurement
n SimPowerSystems in separate triggered tasks (task handling)
n Supports model separation (model splitting)
n Precomputation of switch-configuration-dependent matrices (mode caching)
FPGA-based approach n Standard SimPowerSystemsTM components
n Preconfigured FPGA applications for calculating SimPowerSystems™ models
n Supports model separation (model splitting)
n Precomputation of switch-configuration-dependent matrices (mode caching)
Software
Hardware
FPGA-based Processor-based
Engineering
Workflow overview
109
2016

Order Information

Electrical Power Systems Simulation Package n Please inquire
for Processor-based Approach
Electrical Power Systems Simulation Package n Please inquire
for FPGA-based Approach
Relevant Software and Hardware for Processor-based Approach

Required Real-Time Interface or See p. 56
ConfigurationDesk® See p. 48
XSG Utils Library See p. 104

Required DS1006 Processor Board or n DS1006
SCALEXIO® Processing Unit n SCLX_RTPC
Optional DS5202 EMH Solution See p. 464
DS5203 FPGA Board See p. 462
DS5203M1 Multi-I/O Module See p. 465
DS2655 FPGA Base Board See p. 335
DS2655M1 Multi-I/O Module See p. 336
Relevant Software and Hardware for FPGA-based Approach

Required ConfigurationDesk® See p. 48

Required SCALEXIO® Processing Unit n SCLX_RTPC
DS2655 FPGA Base Board See p. 335
Optional DS2655M1 Multi-I/O Module See p. 336
110
2016

Implementation Software / Compilers
Compilers
Introduction
For translating C code into object code
Highlights
Application Fields
Support of C++

Support of ANSI standard C

Including shell programs for single-step compiling,

assembling, and linking
Automatic invocation during code generation

process when used with Real-Time Interface (RTI)
Software
Overview
Compilers Features dSPACE Products
Microtec PowerPCC Compiler Generates executable object code for PowerPC processors
DS1103 (p. 358)

Sophisticated optimization pass for efficient, compact object code
DS1104 (p. 364)

Assembler and linker included
DS1005 (p. 376)

Run-time libraries included

Texas Instruments TMS320 Generates executable object code for TI‘s C31 and VC33 DSPs
DS2211 (p. 410)

Hardware
Optimizing C Compiler Sophisticated optimization pass for efficient, compact object code
DS2302 (p. 416)



GNU C Compiler Generates executable object code for x86 processors

DS1006 (p. 380)

Sophisticated optimization pass for efficient, compact object code
DS1007 (p. 386)

MicroLabBox (p. 540)


1)
Order Information Engineering

Microtec PowerPC C Compiler CCPPPC

Texas Instruments C3X/4X Code Composer TMDS3240130

GNU C Compiler for DS1006 DS1006_COMP

GNU C Compiler for DS1007 DS1007_COMP

GNU C Compiler for MicroLabBox MLBX_COMP

111
2016

Simulation Software / VEOS
VEOS®
Platform for PCbased simulation of models and ECU network communication
Highlights
Early validation of ECU software by PC-based

simulation
Comprehensive, realistic simulation of ECU

network communication for CAN and LIN buses
Seamless integration with RCP and HIL tool chains

Openness through support of significant standards

like AUTOSAR and Functional Mock-up Interface
Support of multi-model scenarios


dSPACE VEOS is a PC-based simulation platform that pro- Running on a standard PC, VEOS gives function developers,
motes the use of virtual validation in the development of software architects and ECU testers numerous new options
electronic control units (ECUs). VEOS makes it possible for virtual validation in an early project phase.
to simulate a wide range of different models − function New functions can be integrated with the overall ECU
models, Functional Mock-up Units (FMUs), virtual ECUs software to test how they interact.
(V-ECUs), and vehicle models – independently of any A virtual test bench with powerful engine and vehicle
specific simulation hardware in early development stages. dynamics models is permanently available for designing
For multi-model scenarios VEOS supports importing, con- complex controller strategies.
necting and running any number of functions and plant Complex vehicle and environment models can be inte-
models based on Simulink or Functional Mock-up Interface grated with virtual ECUs to simulate and test an entire
(FMI) thereby extending the scope of your applications. virtual vehicle.
In preparation for hardware-in-the-loop simulation, mod-
els and tests can be created, set up and run on a PC
independently of the hardware-in-the-loop (HIL) system.
Systematic Extension to the dSPACE Tool Chain

VEOS works hand in hand with other dSPACE products to TargetLink® for generating AUTOSAR and non-AUTOSAR

provide a complete tool chain for the development and simulations based on production code
testing process. This means that tools and models which SystemDesk® for generating virtual ECUs

are commonly used in rapid control prototyping and hard- RTI Bypass Blockset for extending V-ECUs with Simulink

ware-in-the-loop simulation can also be used in the virtual controller models
world. Similarly, layouts from HIL simulation can be reused Automotive Simulation Models for complex environment

in PC-based simulation with VEOS and vice versa. VEOS models
also provides open interfaces to connect and utilize your ModelDesk for graphically configuring and parameterizing

existing tools. environment models
Simulink® and dSPACE Run-Time Target for generating ControlDesk® Next Generation for experimenting and

C-code-based simulations visualizing simulations
MotionDesk for visualizing simulation scenarios

112 AutomationDesk for creating tests and automating simu-

2016
lation runs

Introduction
PC-based simulation Simulation of different models, from function models to virtual ECUs, bus systems, and vehicle models

No additional hardware needed for simulation

Simulink support Simulation
of Simulink function models and Simulink environment models (such as dSPACE ASMs)
Application Fields
Support
of S-functions, model referencing, multitasking, triggered or enabled subsystems and tunable
parameters
Simulation of Simulink implementation containers (SICs) generated from Simulink models by the dSPACE Run-

Time Target in different projects
FMI support Simulation of Functional Mock-up Units (FMUs) based on the Functional Mock-up Interface (FMI) for Co-Simulation

Support of FMI 2.0 functionalities and access/monitor support for all variables and parameters defined by an

FMU
TargetLink support Simulation of TargetLink-generated code used in virtual ECUs (V-ECUs) or FMUs

Support for AUTOSAR as well as non-AUTOSAR TargetLink code

AUTOSAR support Simulation
of virtual ECUs which are generated by SystemDesk
Support
of realistic AUTOSAR operating systems
Support of AUTOSAR basic software modules, such as DEM, NVRAM or ECU state manager

Software
Support of AUTOSAR R3.0, R3.1, R3.2, and R4

Bus simulation Simulation of ECU network communication on CAN and LIN buses, including messages, scheduling and arbitration

Idealized
bus simulation for FlexRay
Virtual Bypass Support Replacing existing ECU functions with new Simulink models using the virtual bypass method

XIL API support Support of XIL API Model Access port

XCP support Access to Simulink and TargetLink models as well as V-ECUs via XCP on Ethernet

Debugging C code debugging during a running simulation

Code coverage Analyzing the extent to which code has been tested with CTC++ from Testwell

Processor-in-the-loop (PIL) simulation Running ECU code for the target processor on an evaluation board

Support of Freescale MPC 5604B and Infineon TriCore 1797 evaluation board

Hardware
Tool chain integration Off-the-shelf integration into the dSPACE rapid control prototyping (RCP) and hardware-in-the-loop (HIL) tool chain

Engineering
113
2016

Order Information
Application Description Order Number

Offline simulation of Simulink models Basic variant
VEOS_BASE

Simulation of several Simulink models or FMUs

The dSPACE Run-Time Target for generating Simulink implementation containers (SICs)

from Simulink models (Simulink Coder required) is needed
Offline simulation of one or more Add-on to the base variant VEOS_BASE
VEOS_ECU

virtual ECUs Simulation of Simulink models or FMUs together with 1... n SystemDesk V-ECUs

Offline simulation of virtual ECUs with Add-on to VEOS_ECU
VEOS_CAN

virtual CAN or LIN bus simulation Connecting
SystemDesk V-ECUs via CAN or LIN bus VEOS_LIN

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

loop simulation Offline simulation for testing the virtual ECU with the target processor
Relevant Software
Software
Required Operating system: www.dspace.com/goto?os_compatibility

Optional Simulink
TargetLink (p. 202)

SystemDesk (p. 40)
dSPACE Automotive Simulation Models (p. 258)

ModelDesk (p. 283)
ControlDesk Next Generation (p. 120)

MotionDesk (p. 156)

RTI Bypass Blockset (p. 64)

114
2016

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

To make exchanging simulation models easy, dSPACE of-
Software
fers a Model Interface Package for Simulink® (MIPS) for + MIPS
generating Simulink implementation container (SIC) files. Modeling

Expert
With the free-of-charge MIPS, modeling experts can gen-
erate the (C code) SIC file with Simulink Coder, without
needing a VEOS or ConfigurationDesk license. Out of their SIC (C code)
Simulink models and together with dSPACE Run-Time Tar-
get, they can generate code and create ZIP files that con- Model
Integrator
tain all the necessary code and artifacts for executing the
Hardware
models on different simulation platforms, such as VEOS
and SCALEXIO®.
Model integrators using SIC files do not have to generate
code again for building the simulation. Using SICs therefore
significantly reduces the amount of time needed for reusing
the SICs in different projects.
Engineering
Comprehensive Bus Simulation Openness Through Automotive Standards
Using VEOS, you can also simulate a network of AUTOSAR VEOS can easily be integrated into your existing tool
virtual ECUs. These include a realistic operating system and chain, as it supports automotive standards such as
can be extended with basic software such as DEM, NVRAM ASAM
or the ECU state manager as the simulation scenario re- AUTOSAR
quires. A predefined COM stack can be included or config- Functional Mock-up Inferface (FMI)
ured for a virtual ECU in SystemDesk. CAN and LIN buses
and their bus-specific effects can be simulated with VEOS So when you add VEOS to your rapid control prototyping
on a PC without additional hardware. This gives you precise or HIL tool chain to perform PC-based simulation, you can
simulation of distributed functions, including ECU network keep your existing tools. By deciding to use VEOS, you gain
communication, very early in the development process. high flexibility and investment protection for new projects
and challenges.
115
2016

Use Cases
VEOS for Virtual Test Drive
Use your own PC for closed-
loop tests of ADAS functions
Reuse plant and environment
models
Model and Instruments,
Visualization and
Use models and automated environment Simulation model
animation
simulation control
parameterization and validation
tests seamlessly throughout
all development phases
Support of Simulink®, Target-
Link®, legacy C code, AUTO-
SAR, and FMI
Virtual test drive

using your own PC
Function/
Software Developer
Virtual Test Bench FMU
PC as virtual test bench C Code

XML
available at all times
Integration of specialized
models from the computation
Instruments,
Functional
department using FMI Mock-Up Unit
Simulation model Stimulus simulation control
and validation
Realistic simulation using
virtual ECUs and complex
simulation models on the PC
Use of an integrated tool chain
Execution of function tests

with realistic stimulus and
simulation models
HIL Tester
116
2016

Introduction
Virtual bypassing with VEOS
Incremental function develop-
ment without the need for
ECU hardware prototypes
Application Fields
V-ECU
Fast iterations without ECU
Reuse of existing New Simulink
software rebuild virtual ECUs function, to be tested
Reuse existing bypass func-
tions
Realistic closed-loop simu- Reuse of the same
Simulink model for
lation with virtual ECUs and external and internal
bypassing
complex environment models Developing new
Seamless path from offline control functions in
Simulink and testing
development to real-time inside a V-ECU in
a virtual environment
simulation
Software
Function/
Software Developer
Virtual ECU tests with VEOS
Hardware
Integration tests on the developer's PC .c .c .h .o
Use of established tools for debugging, 001110
110001
001110
code coverage, and parameter analysis
Early integration tests without a hard-
ware prototype
Virtual ECU tests even without AUTOSAR
Generation of Generation of
C code modules V-ECU
Engineering
Integration tests
using your own PC
Function/
Software Developer
117
2016

Virtual ECU Testing

Continuous integration of ECU
software using the PC
Benefit from familiar debugging,
code coverage and parameter
analysis settings Integration of Instruments,
software components simulation control
Processor-in-the-Loop simulation and generation of VECUs and validation
of virtual ECUs
Support of AUTOSAR-based and
non-AUTOSAR-based workflows
Execution of integration
tests with virtual ECUs
Software
Integrator
Preparing Hardware-in-the-
Loop Tests
Preparing HIL test artifacts
such as automated tests,
layouts, and model confi-
Model and dSPACE and third-
Instrumentation and Test automation
gurations on the PC environment
simulation control
party simulation
and reporting
parameterization models
Identifying errors in the HIL
tests even before execution
Maximizing HIL simulator
utilization
Support of the XIL/HIL API
standard Development and test Enhancing and
of HIL models, layouts reusing HIL tests
and test scenarios
HIL Tester Simulator
118
2016

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

on a PC with virtual ECUs
Software
HIL Tester
Hardware
Engineering
119
2016

Experiment and Visualization Software / ControlDesk Next Generation
ControlDesk® Next Generation

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

software for ECU development
Integrated ECU calibration, measurement and

diagnostics access (CCP, XCP, ODX)
Synchronized data capture across ECUs, RCP and HIL

platforms, and bus systems
Powerful layouting, instrumentation, measurement
and post-processing (ASAM MDF)
Support for the entire dSPACE virtual validation tool chain

ControlDesk Next Generation is the dSPACE experiment ControlDesk Next Generation unites functionalities that
software for seamless ECU development. It performs all the often require several specialized tools. It provides access
necessary tasks and gives you a single working environment, to simulation platforms as well as to connected bus sys-
from the start of experimentation right to the end. These tems and can perform measurement, calibration and diag-
are some of the tasks it can be used for: nostics on ECUs, e.g., via standardized ASAM interfaces.
Rapid control prototyping (fullpass, bypass) Its flexible modular structure (p. 122) provides high scalabil-
Hardware-in-the-loop simulation ity to meet the requirements of specific application cases.
ECU measurement, calibration, and diagnostics This gives you clear advantages in terms of handling, the
Access to vehicle bus systems (CAN, CAN FD, LIN, FlexRay) amount of training needed, the required computing power,
Virtual validation with VEOS® and SCALEXIO®1) and costs.
Rapid control ECU

Virtual prototyping Hardware-in-the- (measurement, Access to vehicle
validation1) (fullpassing/ loop simulation calibration and bus systems
bypassing) diagnostics)
Synchronized time base on all platforms/devices
CAN / CAN FD
LIN
FlexRay
PC-based
offline simulation
120
2016 1)
Please see p. 138 or www.dspace.com/go/viva_en for more information on virtual validation in the dSPACE tool chain.

Introduction
Versions Description
ControlDesk Next Generation – Basic Version Same tool for rapid control prototyping, HIL simulation, offline simulation, ECU calibration and diagnostics

Easy creation of layouts and instruments

Synchronous measurement on all data sources

Integrated project and experiment management

Integrated measurement data management (with ASAM MDF 4.1 support for import and export)

Compatibility with several ASAM standards (such as MDF, XCP, CCP, ASAP2, ODX)

Application Fields
Powerful tool automation capabilities for user-specific extensions and optimal process integration

CAN access by dSPACE hardware and PC bus interfaces (e.g., DCI-CAN1 and DCI-CAN2):

CAN monitoring, CAN logging, and dedicated instruments for CAN bus objects
Operator mode (protects your projects and experiments against unauthorized changes)

Support of virtual validation test scenarios (p. 138) with dSPACE VEOS and SCALEXIO

ControlDesk Next Generation – For using projects and experiment data that were already created with the Basic Version

Operator Version Protection against altering and creating projects and experiments

Platform Modules Description

Standard Platforms Module Support of dSPACE RCP and HIL platforms (DS1005, DS1006, DS1007, DS1103, DS1104, MicroAutoBox,

MicroLabBox)
Software
Multiprocessor Module For using ControlDesk Next Generation with dSPACE multiprocessor systems based on

DS1005, DS1006 or DS1007
Support of multicore applications for DS1006, DS1007, and MicroLabBox

Add-on to Standard Platforms Module

SCALEXIO Platform Module1) For using ControlDesk Next Generation with dSPACE SCALEXIO

SCALEXIO Multicore Module Support of multicore applications for dSPACE SCALEXIO

Add-on to SCALEXIO Platform Module

SCALEXIO Multiprocessor Module2) Support of multi-processing-unit applications for dSPACE SCALEXIO

Add-on to SCALEXIO Platform Module

XIL API MAPort Platform Module Access to test benches by using an ASAM XIL API MAPort server for reading, writing and capturing variables

Hardware
Additional Modules Description
ECU Interface Module AUD, NBD, JTAG/Nexus, JTAG/OCDS and JTAG/SDI

CCP3) (CAN Calibration Protocol)

XCP on CAN3), XCP on Ethernet4) (TCP/IP and UDP/IP), XCP on FlexRay

ECU Diagnostics Module Compliance with the ODX database standard (ASAM MCD-2D v2.0.1 and v2.2.0 (ISO 22901-1))

Support of ISO protocols for CAN and K-Line

Dedicated instruments for executing diagnostic services and reading or clearing the ECU fault memory

ECU flash programming via diagnostic interfaces

Support of ASAM MCD-3D v2.0.2

Engineering
Signal Editor Module5) For graphical stimulus definition

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

in dSPACE VEOS
Measured data can easily be replayed

Several stimulus patterns can be executed independently

Support of XIL API stimulus format (.STZ files, i.e., zipped .STI files)

Bus Navigator Module Support of CAN (incl. J1939), CAN FD, LIN, and FlexRay buses for dSPACE hardware or PC bus interfaces

Replaying recorded CAN messages

Dedicated instruments for LIN and FlexRay bus objects

LIN monitoring and logging for dSPACE hardware

FlexRay monitoring and logging via PC bus interfaces

MCD3 Automation Module6) Automation interface for measurement, calibration, and diagnostics according to the ASAM MCD-3 standard

Continuous data acquisition in real-time rasters

Remote ASAM MCD-3 access to ControlDesk Next Generation via COM/DCOM API

1)
The SCALEXIO Platform Module includes the Standard Platforms Module.
2)
The SCALEXIO Multiprocessor Module includes the SCALEXIO Multicore Module.
3)
Support for CAN FD with DCI-CAN2. 121
4)
Also for access to simulated virtual ECUs. 2016
5)
Signal generation not supported for DS1103 and DS1104.
6)
The MCD3 Automation Module is not supported by the ControlDesk Next Generation – Operator Version.
Module Overview
ControlDesk Next Generation: Modules

1)
Comprehensive Basic Version;
a free Loader Version (platform
handling only) is also available.
ControlDesk Next Generation – ControlDesk Next Generation – 2)
Protection against altering
Versions Basic Version1) Operator Version2) and creating projects and
experiments.
3)
Add-on to the Standard
Standard Platforms XIL API MAPort Platforms Module.
Multiprocessor Module3) 4)
Includes the Standard
Module Platform Module Platform Module.
Platform 5)
Add-on to the SCALEXIO
support Platform Module.
SCALEXIO SCALEXIO SCALEXIO 6)
Please note: The MCD3
Platform Module4) Multicore Module5) Multiprocessor Module5)7) Automation Module is not
supported by the Operator
Version.
7)
The SCALEXIO Multiprocessor
ECU Interface Module ECU Diagnostics Module MCD3 Automation Module6) Module includes the SCALEXIO
Multicore Module.
Add-on 8)
The Failure Simulation Module´s
modules functionality, the CDNG_FS GUI
The Failure Simulation and its tool automation, will be
Signal Editor Module Bus Navigator Module Module is discontinued available as part of the Failure
as a separate product.8) Simulation Package (p. 198)
until Release 2016-A.
Order Information

ControlDesk Next Generation – Basic Version CDNG_BASIC

ControlDesk Next Generation – Operator Version CDNG_O9)

Standard Platforms Module CDNG_STD

Multiprocessor Module10) CDNG_MP

SCALEXIO Platform Module11)12) CDNG_SCLX

SCALEXIO Multicore Module13)14) CDNG_SCLX_MC

SCALEXIO Multiprocessor Module13)15)16) CDNG_SCLX_MP

XIL API MAPort Platform Module CDNG_XIL_API_MAPORT

ECU Interface Module CDNG_ECU

ECU Diagnostics Module CDNG_DIAG

Signal Editor Module CDNG_SE

Bus Navigator Module CDNG_BNV

MCD3 Automation Module CDNG_MCD3

ControlDesk Next Generation – Loader Version Free of charge

9)
CDNG_O is free of charge, but is available only if ordered together with CDNG_STD or CDNG_SCLX.
10)
Add-on to the Standard Platforms Module
11)
The SCALEXIO Platform Module includes the Standard Platforms Module.
12)
Also requires the SCALEXIO Real-Time Library for downloading and handling real-time applications for the SCALEXIO system.
13)
Add-on to the SCALEXIO Platform Module
14)
Also requires the SCALEXIO Real-Time Library for Multicore Systems for downloading and handling multicore real-time applications for the
SCALEXIO system.
15)
The SCALEXIO Multiprocessor Module includes the SCALEXIO Multicore Module.
16)
Also requires the SCALEXIO Real-Time Library for Multiprocessor Systems for downloading and handling multi-processing-unit (multi-PU)
applications for the SCALEXIO system.
122
2016

Introduction
Relevant Software and Hardware1)

Required Operating system: www.dspace.com/go/os_compatibility
–
Optional dSPACE VEOS® for PC-based simulation
See p. 112
dSPACE SYNECT® for storing ControlDesk projects in the SYNECT database
See p. 292
Application Fields
Failure Simulation Package for working with the XIL API EESPort GUI in ControlDesk2)
FAILURE_SIM
Hardware
Required Intel Core 2 Duo processor at 2 GHz or equivalent (Intel Core i7 processor or equivalent recommended)

2 GB RAM for 32-bit operating systems (4 GB RAM recommended),

4 GB RAM for 64-bit operating systems (8 GB RAM recommended)
NEW: ControlDesk 5.5
Software
Feature Area Improvement
Variable Management The Variable Browser now supports the display of structured variables (structs and struct arrays)

Support of enhanced code generation features of Simulink Coder

Platform Management and Support of DCI-CAN2 (p. 594) including CAN FD support for bus monitoring, CCP, and XCP on CAN

Platforms/Devices CAN Bus Monitoring device: Support for FIBEX and AUTOSAR system description files

FlexRay Bus Monitoring device: Support for AUTOSAR system description files

Automatic Reconnect for DS1007 PPC Processor Board, MicroLabBox, SCALEXIO, and XIL API MAPort

Instrumentation Connection assignment for instruments to create special variable-instrument connections, such as connecting a

group of variables to multiple instruments in one step
The Time and Index Plotters now offer enhanced functionality like saving time plotter data or x-axis

Hardware
synchronization
Measurement and Recording Use of ASAM MDF 4.1 as primary data format for measurements

Measurement configuration optimized for handling a large number of rasters

Data Set Management Use of ASAM CDF 2.0 (CDFX) as primary format for data sets

Signal Editor Module Support of MicroLabBox

Full support of DS1007 multicore and multiprocessor systems

Bus Navigator Module Support of CAN FD for SCALEXIO

Support of DCI-CAN2 (CAN and CAN FD)

Layout generation for Bus Manager (p. 54) applications (CAN, CAN FD, and LIN)

CAN bus communication replay via MicroLabBox

Engineering
NEW: XIL API EESPort GUI Successor to ControlDesk’s Failure Simulation Module2)

Interactive graphical configuration of error configurations and error sets compliant with ASAM AE XIL API standard

(EESPort)
Requires the Failure Simulation Package (p. 198)

ControlDesk Next Generation Product Support Center

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

users and provides information about releases, compatibility
1)
ControlDesk Next Generation is also approved for the MicroAutoBox Embedded PC (running under Microsoft®
Windows® 7, 32-bit Ultimate).
2)
The Failure Simulation Module is discontinued as a separate product. Its functionality, the CDNG_FS GUI and its
123
tool automation, will be available as part of the Failure Simulation Package (p. 198) until Release 2016-A.
2016

ControlDesk Next Generation – Basic Version

Comprehensive Functionalities Intuitive, Ribbon-based User Interface
The ControlDesk Next Generation – Basic Version is a State-of-the-art GUI technology (ribbons)
comprehensive basic module offering many fundamental Ribbons to group commands for customer workflows
features for experiment creation and management, instru- (different sizes and icons indicate importance to improve
mentation, etc. The module can be extended with further memorability and touchscreen usability)
ControlDesk Next Generation modules. With the Control Backstage view for central opening, importing and
Desk Next Generation – Basic Version, you can prepare saving of projects
project/experiment data (such as layouts, data sets and Start page for easy access to most recently opened
measurements) for later use in the operator mode or in the projects and user documentation
ControlDesk Next Generation – Operator Version (p. 139).
Start page for easy access to recent projects and user

documentation.
Description
Easy creation of layouts and instruments

Synchronous measurement on all data sources

Integrated project and experiment management

Integrated measurement data analysis

Compatibility with several ASAM standards

Powerful tool automation capabilities for user-specific extensions and optimal process integration

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
Operator mode (protects your projects and experiments against unauthorized changes)

Support of virtual validation test scenarios (p. 138) with dSPACE VEOS and SCALEXIO

Camera interface and video instrument (p. 133)

Order Information

ControlDesk Next Generation – Basic Version CDNG_BASIC

124 1)
To access the CAN interfaces of dSPACE hardware (i.e., to send and receive CAN messages), the Standard
2016 Platforms Module (p. 140) is necessary.

Introduction
Project Management
Organizing Projects and Experiments
ControlDesk Next Generation organizes your work in level is for organizing your instrument panels (layouts),
projects and experiments. A project is the outer organi- variable descriptions, data sets, signal generators, failure
zational frame for your work on a topic. Within the proj- simulation systems, and more. All your data is well structured
ect you can have many experiments, for example, each at all times and easy access is provided by the ControlDesk
representing a unique hardware setup. You can also assign Next Generation Project Manager. You can manage your
Application Fields
different variable descriptions to a single platform/ ControlDesk Next Generation projects with your version
device in the experiment and easily switch between control system. Check-out and check-in operations are
them later on. The project level also holds global docu- directly supported by ControlDesk Next Generation.
ments such as specifications or reports. The experiment
Software
Selecting a project and experiment in ControlDesk Layouts can be grouped in folders.
Next Generation.
Hardware
Using a SYNECT® Server for Managing
ControlDesk® Data
Option to store entire ControlDesk projects in
the SYNECT database1)
Modified projects and file-based items (such as layouts)
can be submitted to the database
ConfigurationDesk build results can be directly
Engineering
imported from the database1)
Multiuser database, usable from different PCs
Versioning projects in connection with SYNECT server
Support of different SYNECT server versions
Example project in ControlDesk Next Generation’s

Project Manager.
Access to SYNECT running on the same PC is free of charge. SYNECT Base is only necessary to access
1) 125
a SYNECT database running on a separate PC. 2016

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 experi-
ment, and the list can be filtered.
NEW: The new Variable Browser feature of ControlDesk 5.5
also supports structured variables.
NEW: ControlDesk now lets you customize the connection
assignment to create special variable-instrument connec- Customized connection assignment.
tions, such as connecting a group of variables to multiple
instruments in one step.
The Variable
Browser supports
structured variables.
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.
Instrument
Table Editor
Selector
126
2016

Introduction
Variable Array Editing 3-D Maps
With the Variable Array instrument it is easy to quickly visual- ControlDesk Next Generation has powerful features
ize multiple variables. Each variable is displayed in a row of for editing 3-D maps:
the instrument. The variables are marked via multi-selection Interpolation when axis values are changed
and dragged to the layout. The Variable Array provides Interpolation of all maps related to the
different column and cell types. This combination of both lets same shared axis
Application Fields
you individually specify what is displayed in the instrument XZ and YZ projections of 3-D maps
cells and how you can change a parameter value. Easy exchange of data with Microsoft® Excel®
Software
Variable Array
Hardware
3-D map in the Table Editor
Multiswitch Instrument
Instrument for changing variable values by clicking

sensitive areas in the instrument and for visualizing
different states, depending on the current value of the
Engineering
connected variable
You can easily implement different switch types, e.g.,

rotary switches (with different positions, optionally
spring-loaded), manual and automatic gearshifts,
ignition locks
Multiswitch instrument
127
2016

Plotter Instruments
The plotter instruments in ControlDesk Next Generation are the Automatic calculation of maximum, minimum, mean

central components for data visualization. With plotters, the value, and standard deviation over displayed time interval
measured data can be compared to online data. Plotter data Option to synchronize the time intervals of multiple
can be displayed continuously or triggered (similar to an plotters
oscilloscope). Save selected signals and time interval to a new

The plotter instruments provide a variety of features dedi- measurement file, with or without data reduction
cated to efficient data analysis: Move and copy signals from one y-axis to another,

XY cursor or to another instrument (drag & drop)
Time cursor A leading raster can be assigned to the plotter to

Zoom and move a view directly connect the triggered visualization to a
Option to display several y-axes in a stacked view triggered measurement raster
Scroll bar below display area for navigation
Time Plotter and Index Plotter

The Time Plotter lets you display signals
that are measured in a time-based ras-
ter (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 and Index Plotters
have an enhanced performance.
Time Plotter
Index Plotter
On a touch screen, use multi-touch gestures to move

Change manual trigger settings directly within the

and zoom into the chart instrument
Use the plotter toolbar for quick function access
Benefit from high drawing performance by using hardware
Analyze curves via data cursors
acceleration
Make axes invisible
Animation continues while zooming

Set an individual background color or picture
NEW: Save time plotter data

Benefit from triggered display without flickering
NEW: Synchronize the x-axis of Time and Index Plotter

Use automatic triggering
NEW: Use additional line styles (like Area and Staircase)

128
2016

Introduction
XY Plotter
Visualization of several curves (xy pairs of signals)
Triggered XY Plotter visualization (specially suited for
high-frequency applications such as electric drive systems)
Background picture possible
Easy zooming and moving
Application Fields
Data cursors to analyze the curves
XY Plotter
Steering Controller
The Steering Controller provides a graphical representa-
tion of a connected game controller device and lets you
calibrate scalar parameters by moving the device or press-
Software
ing its buttons or switches. The instrument provides force
feedback support.
Hardware
Engineering
129
2016

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
Browser Instrument
The Browser instrument allows you to integrate objects such
as web pages and other documents (like PDF files) directly
on ControlDesk layouts.
130
2016

Introduction
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.).
Application Fields
Extending Instrument Functionalities via Python
You can add a Python script to each instrument and as-
Software
sign Python code to the events of the selected instrument.
This lets you extend the instrument’s functionality via auto-
mation more flexibly.
As one example, the stopwatch instrument was created by

using the new Python script feature for instrument exten-
sion as described above.
Hardware
Stopwatch instrument
General Handling
Engineering
View Sets
ControlDesk Next Generation’s View Sets are named con-
figurations 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.
Customized View Set toolbar View Set dialog

131
2016

Measurement
Easy Configuration of Measurements Triggered Measurements
To handle measurements and recordings, ControlDesk You can define real-time triggers to influence the data stream
Next Generation provides the Measurement Configuration between the PC and the dSPACE hardware. The plotter can
tool. Using ASAM MDF 4.1 as the primary data format, be synchronized with these settings for an oscilloscope-like
the Measurement Configuration tool gives you access to presentation.
all the variables selected for measurement and record-
ing, 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.
NEW: In ControlDesk 5.5, the existing multi-raster measure-
ments feature has been optimized for handling an even
larger number of different rasters.
Measurement configuration.
Multi-raster measurements feature.
Multiple Recorders
You can record to different destination files concurrently,
with independent start/stop triggering.
132 Multiple recorders.

2016

Introduction
Camera Interface and Video Instrument
An integrated camera interface with associated video and to make audio recordings. The instrument also provides
instrument lets you record and replay camera images/videos file-based video streaming.
(e.g., with a USB webcam) synchronously to a measurement A real camera can be replaced by video files/streams that
recording. This makes it a lot easier to interpret measure- allow replaying in synchronicity to other data sources for
ments. It is possible to preview recordings in the online mode postprocessing within ControlDesk.
Application Fields
Software
A typical use scenario is the validation of a vehicle’s wiper the wiper control unit, the vehicle bus and the video camera
Hardware
control and rain sensor, where an extra video camera is usu- time-synchronously. ControlDesk can also replay the logged
ally mounted in the vehicle during test drives. This camera is data for detailed analysis later on. A dedicated video instru-
used to record the ambient weather conditions, the movement lets you select and visualize individual video frames
ment of the wipers and the raindrops on the windscreen. and associate them with other measurement data.
ControlDesk Next Generation can be used to log data from
Engineering
Camera view
Windscreen
ControlDesk
Next Generation
Sensor and
control unit
LIN, CAN, FlexRay
Ethernet, USB
Camera
Recording and replaying video
and bus data synchronously.
133
2016

Measurement Data Pool

The Measurement Data Pool gives you an overview of all the show the relevant information. Complete measurement files
measurement files loaded in ControlDesk Next Generation can by assigned to an existing layout. Data can be imported
and displays the variables and bookmarks associated with and exported in standard formats (such as ASAM MDF).
each file. Powerful filter options make it easy to find and
Measurement Data Pool
Bookmarks
You can set bookmarks during a measurement or recording Next Generation. The bookmark navigator is linked with the
to mark certain measurement points you want to analyze visualization in the Plotter instrument. When a bookmark is
later. Bookmarks can be set either manually or automatically, selected in the navigator, the correct time context is displayed
for example, by definable triggers. The bookmark navigator in the plotter and the associated bookmark is highlighted.
gives you a list of all the bookmarks in the current measure- You can edit and search for bookmarks in the navigator.
ment and in the measurement files loaded in ControlDesk
Calculated Variables
You can create new variables, called calculated variables, ControlDesk Next Generation and recorded in measurement
whose values are calculated from other variables in the files just like normal measurement variables. You can also
associated description file. A formula editor helps you create calculated variables based on variables in measure-
define the calculation method. It is even possible to access ment files during postprocessing. Import and export options
previous values in order to implement filters, derivations, for calculated variables and formulas makes it easy to reuse
integrations or statistical functions such as mean values. them in different experiments and projects.
Calculated variables can be connected to instruments in
134
2016

Introduction
Tool Automation
ControlDesk Next Generation API
An object model in ControlDesk Next Generation – ating a project and experiment with your custom settings.
Basic Version lets you access many of its functions by The API also lets you implement individual functionality, such
automation scripts. The Application Programming Inter- as exporting data sets in a custom file format, to ensure that
face is accessible from .NET programming languages (e.g., ControlDesk Next Generation integrates perfectly into
Visual Basic and C#) and COM/DCOM-based program- your existing development process. (For automation based
Application Fields
ming languages (e.g. Python and C++). With scripts you can on the ASAM MCD-3 standard, please see p. 153, MCD-3
perform your complex workflows in no time, such as cre- Automation Module).
Key Benefits Use Case Examples for Tool Automation

Automated processing of recurrent, time-consuming
Layout and instrument handling

tasks, such as parameter studies Data set handling

Automated experiment creation and configuration
Experiment handling

Powerful event mechanism to react to tool and user
Platform handling

Software
events, for example Project handling

ControlDesk Next Generation tool automation library
Failure simulation

available with AutomationDesk Controlling monitoring, logging, and replay of Bus

Navigator
Read and write variables directly without instruments

Hardware
Advanced ControlDesk Automation Python Editor
Event handling: React by automation scripts or ControlDesk Next Generation has an integrated Python
external tools (such as AutomationDesk to tool events editor with syntax highlighting and automatic code completion
from ControlDesk Next Generation (such as “start (IntelliSense). In conjunction with the Python interpreter, which
measurement”) also ships with ControlDesk Next Generation, you have all
Procedural and object-oriented programming features you need to write automation scripts efficiently. The interactive
Manual modification of generated scripts for advanced command line interpreter in ControlDesk Next Generation
operations with built-in Source Code Editor lets you test your lines of code on the go while scripting.

Engineering
Available with AutomationDesk:

Tool Automation Library for ControlDesk
Event Configuration dialog Next Generation
135
2016

Data Sets
Data Structures with Parameter Values Calibrating Variables
Different operations can be performed on data sets load- ControlDesk Next Generation offers many input instruments
ed in ControlDesk Next Generation. You can copy and for adjusting parameter values. Of course, it is possible to
rename data sets and export them as a CDF file (Cali- calibrate scalar as well as multidimensional parameters.
bration Data Format, primary data format as standard- Parameter changes can be made as physical values or as
ized by ASAM CDF 2.0, CDFX), DCM file, or Microsoft® represented on the target platform, as HEX, decimal, or
Excel®-compatible file. Data sets can also be write-protected. binary values.
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. You can store data sets in a global
pool and compare them with data sets from other proj-
ects and experiments. You can import .par files from
ControlDesk 3.x into an experiment as a data set.
Data Set Manager
136
2016

Introduction
Failure Insertion and Simulation
NEW: XIL API EESPort GUI
The XIL API EESPort (Electrical Error Simulation port) GUI Graphical user interface for interactive handling of

replaces ControlDesk Next Generation´s Failure Simulation electrical error simulation compliant to ASAM AE XIL
Module1). It not only provides for a convenient control of API standard (EESPort)
electrical failure insertion hardware (via the XIL API EESPort Creation of error configurations, error sets and errors

server), it also allows for an interactive graphical configu- Performing electrical error simulation (like downloading

Application Fields
ration of error sets and error configurations (equivalent to and activating error configurations, and triggering of
failure patterns) directly from ControlDesk as the XIL API error sets)
EESPort client. By complying with the ASAM XIL API stan- Covers dSPACE SCALEXIO, dSPACE Simulators Mid-Size

dard, this solution offers uniform support for all dSPACE and Full-Size
SCALEXIO and PHS Failure Insertion Units (FIU). Convenient and uniform use of XIL API Error

Configurations and Error Sets across different types of
failure insertion units
Requires the Failure Simulation Package (p.198)

Software
Hardware
Engineering
Definition of various error sets with the XIL API EESPort GUI.
1)
The Failure Simulation Module is discontinued as a separate product. Its functionality, the CDNG_FS GUI and its
tool automation, will be available as part of the Failure Simulation Package (p. 198) until Release 2016-A.
137
2016

Virtual Validation
ControlDesk’s Role in the Tool Chain
Using virtual validation allows developers to pre-draw a VEOS is the dSPACE platform for virtual validation in the
significant number of design, verification and validation tasks development of electronic control units (ECUs). The software
to earlier stages in the development process, saving time and tool makes it possible to validate ECU software early by PC-
money as well as increasing product maturity and safety. In based simulation and to realistically simulate ECU network
doing so, virtual validation moreover reduces the number communication (CAN). ControlDesk Next Generation and
of additional test systems and ECU prototypes required. VEOS together allow you to run and access a wide range
of different models: function models, virtual ECUs (V-ECUs),
The seamless dSPACE development and testing tool chain and vehicle/environment models.
offers virtual validation capabilities in line with two simula-
tion platforms: dSPACE VEOS® for PC-based simulation or In connection with dSPACE HIL systems like SCALEXIO,
dSPACE SCALEXIO® for hardware-in-the-loop (HIL) simula- ControlDesk Next Generation can, for example, be utilized
tion. Models, data, layouts and experiments from Control- to reuse V-ECUs for restbus simulation in HIL tests with a
Desk® Next Generation can be conveniently exchanged and real ECU. Furthermore, V-ECUs can help out in HIL simula-
reused between the different simulation platforms without tion scenarios for which a real ECU hardware prototype is
further modifications. not available yet.
Adding Multiple Platforms/Devices

For virtual validation scenarios, ControlDesk offers a simplified
way to add and configure multiple platforms and devices that
Plant Model
refer to an application containing virtual ECUs and, option-
ally, an environment model executed on VEOS or SCALEXIO.
When working without an environment model, applications
(*.rta or *.osa) can be added instead of a variable description.
XCP
PCbased simulation with VEOS and

138
2016

Introduction
ControlDesk Next Generation – Operator Version
Protection Against Unauthorized Changes
ControlDesk Next Generation – Operator Version is a cost-
effective 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,
Application Fields
data sets and measurements) that were previously created
and saved with ControlDesk Next Generation – Basic Version
(p. 124). The Operator Version provides the same function-
alities as the operator mode of the Basic Version.
Description
Use projects and experiment data that were previously created with the Basic Version

Protect against altering and creating projects and experiments

Perform measurements on platforms/devices (corresponding platform/device module licenses needed)

Software
Use existing layouts (without modification)

Reload variable descriptions

Record data files (automatically added to the experiment)

Export measurement data files

Change the working data set

Duplicate and export data sets

Use tool automation (for all functionality available with the Operator Version)

Work with Bus Navigator instruments included on existing layouts

Monitor, log and replay bus data with the Bus Navigator (CDNG_BNV license needed)

Perform signal generation with existing signal descriptions (CDNG_SIGNALEDITOR license needed)

Work with failure patterns of existing failure simulation systems (CDNG_FS license needed)

Hardware
Please note: The MCD3 Automation Module is not supported by the Operator Version.

Order Information

ControlDesk Next Generation – Operator Version CDNG_O1)

Engineering
139
1)
CDNG_O is offered free charge, but is only available by ordering together with CDNG_STD (p. 140) or CDNG_SCLX (p. 142). 2016

Standard Platforms Module1)

Access to dSPACE Real-Time Platforms
The Standard Platforms Module is an optional software mod-
ule which provides access to the dSPACE real-time platforms
DS1103, DS1104, DS1005, DS10062), DS10072), MicroAuto-
Box, 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 Information

Standard Platforms Module 1)
CDNG_STD

140 1)
Upgrade to SCALEXIO Platform Module possible (p. 142)
2016 2)
The Multiprocessor Module is also necessary when you use multicore applications on a DS1006, DS1007, or MicroLabBox.

Introduction
Multiprocessor Module
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, DS1006 and DS10071) as well as to using multicore
applications on the DS1006, DS1007, and MicroLabBox.
Application Fields
Example:
MicroLabBox
DS1007 (Dual-Core)
Software
DS1006 (Quad-Core)
Gigalink
3 x DS1006 (Single-Core)
Hardware
or 3 x DS1005 or 3 x DS1007
Using ControlDesk Next Generation with the Multiprocessor Module for multiprocessor applications (DS1005, DS1006, DS1007) and
multicore applications (DS1006, DS1007, MicroLabBox).
Order Information
Engineering
Multiprocessor Module CDNG_MP

141
1)
The Multiprocessor Module is also necessary when you use multicore applications on a DS1006, DS1007, or MicroLabBox. 2016

SCALEXIO® Platform Module1)2)

Access to dSPACE SCALEXIO Background Information: SCALEXIO Hardware
The SCALEXIO Platform Module is an optional software With SCALEXIO’s flexible component design, each sys-
module which provides access to a dSPACE SCALEXIO tem is precisely scalable to any desired size, completely
system. software-configurable, and versatile enough to be used
in different test tasks.
Real-time processor with the latest processor
technology
IOCNET: serial I/O network
I/O board types: HighFlex, MultiCompact and
SCALEXIO I/O Boards
User-programmable FPGA
Flexible component design
Powerful configuration software (ConfigurationDesk)
Gigabit Ethernet Host Interface
Access to a dSPACE SCALEXIO system.
Order Information

SCALEXIO Platform Module CDNG_SCLX

142 1)
The SCALEXIO Platform Module includes the Standard Platforms Module (p. 140).
2016 2)
Also requires the SCALEXIO Real-Time Library for downloading and handling real-time applications for the SCALEXIO system.

Introduction
SCALEXIO® Multicore Module1)2)
Even More Flexibility
The SCALEXIO Multicore Module provides access to multi-
core applications running on dSPACE SCALEXIO. Three cores
can be used for computing models and I/O, resulting in more
available computation power.
Application Fields
Software
Support of multicore applications
Support of multicore applications for dSPACE SCALEXIO.
Hardware
Order Information

SCALEXIO Multicore Module  CDNG_SCLX_MC
Engineering
1)
Add-on to the SCALEXIO Platform Module (p. 142). 143
2)
Also requires the SCALEXIO Real-Time Library for Multicore Systems for downloading and handling multicore real-time 2016
applications for the SCALEXIO system.

SCALEXIO Multiprocessor Module1)2)3)

More Power
SCALEXIO supports the coupling of two or more SCALEXIO Module provides access to the multiprocessor (and multi-
Processing Units to increase the computing power avail- core) features of a dSPACE SCALEXIO multi-processing-unit
able for complex simulations. The SCALEXIO Multiprocessor system.
Multiprocessor support for SCALEXIO.
Order Information

SCALEXIO Multiprocessor Module  CDNG_SCLX_MP
1)
Add-on to the SCALEXIO Platform Module (p. 142).
144 2)
Includes the SCALEXIO Multicore Module (p. 143).
2016 3)
Also requires the SCALEXIO Real-Time Library for Multiprocessor Systems for downloading and handling
multi-processing-unit (multi-PU) applications for the SCALEXIO system.

Introduction
XIL API MAPort Platform Module
Access to Additional Hardware
With the optional XIL API MAPort Platform Module,
ControlDesk Next Generation provides access to third-party
test benches and other hardware by using an ASAM XIL API
MAPort server for reading, writing and capturing variables.
Application Fields
Third-party test bench data supported by the ASAM XIL API
standard can be visualized on ControlDesk layouts and can
be integrated in synchronous measurements and recordings
together with other platform or device data.
To ensure optimal interfacing, dSPACE offers compre-

hensive consulting and engineering support for the
ControlDesk Next Generation XIL API MAPort Platform.
Please enquire.
Software
Third-party test
benches / HIL
Simulators
XIL API
Hardware
MAPort server
Other third-
party hardware
(e.g., oscillo-
scopes)
Order Information
Engineering
XIL API MAPort Platform Module CDNG_XIL_API_MAPORT

145
2016

ECU Interface Module

Calibration and Measurement
The ECU Interface Module is an optional software module
for calibration and measurement access to electronic
control units.
Support of ASAM A2L files (ASAM MCD-2 MC)

Seed & key access to ECU for XCP and CCP

Online and offline calibration
Calibration of ECUs without dedicated data segments

Support of single-page and two-page concepts with
NEW: Support of CAN FD (CCP and XCP on CAN with

a working and reference page DCI-CAN2)
Automatic reconnect to unplugged ECUs for resuming

measurement
JTAG, AUD, Serial calibration

Nexus, etc.
On-chip
RAM Generic Serial Interface
CAN, CAN FD (DCI-GSI1, DCI-GSI2)
µC XCP on CAN, CAN FD1), CCP
FlexRay
On-chip
XCP on Ethernet
flash Ethernet XCP on FlexRay
1)
with DCI-CAN2 (p. 594)
Overview of ECU interfaces and protocols of ControlDesk Next Generation.
Order Information

ECU Interface Module CDNG_ECU

146
2016

Introduction
ECU Diagnostics Module
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.
Compliance with the ODX database standard

Support of ControlDesk’s application programming

Application Fields
Support of ISO protocols for CAN and K-Line
interface (API) for access to diagnostics functions
Dedicated instruments to execute diagnostic services
(p. 135)
and to read or clear the ECU fault memory Support of ASAM MCD-3D v2.0.2 (COMPARAMs

ECU flash programming via diagnostic interfaces
according to PDU API v2.2, ISO 22900-2)

ECUs can be interfaced via the ISO-standardized diagnostic The ControlDesk Next Generation ECU Diagnostics Module
Software
protocols KWP2000 (ISO 14230), Diagnostics on CAN (ISO enhances ControlDesk Next Generation to a comprehensive,
15765), UDS (Unified Diagnostic Services) (ISO 14229-1), integrated measurement, calibration, and diagnostics tool
OBD (ISO 15031), and Transport Protocol (TP 2.0) on CAN. (MCD tool). Additional instruments for working with an
The ECU Diagnostics Module is fully compliant with ODX ECU’s fault memory, and diagnostic services and jobs, are
(Open Diagnostic Data Exchange), the ASAM MCD-2D seamlessly integrated into ControlDesk Next Generation.
standard (v2.0.1 and v2.2.0 (ISO 22901-1)). Combined The easy generation of diagnostic variables from ODX allows
with the ControlDesk MCD3 Automation Module, a stan- you to use DTCs, measurements and parameters with the
dard automation interface according to ASAM MCD-3 D standard instruments and together with signals from other
Hardware
(v2.0.2) is provided for the remote control of diagnostic sources. The integrated ECU flash programming support
tasks. Alternatively, many of ControlDesk’s diagnostics func- lets you update the ECU with the latest software version or
tions can be accessed by automation script via a dedicated calibration data via diagnostic protocols.
application programming interface (API) (p. 135).
Fault Memory Instrument
With the Fault Memory instrument you can read and dis-
play 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.
Engineering
The fault memory can be cleared either completely or par-
tially. 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.
147
2016

Diagnostics Instrument Instrumentation of Diagnostic Variables

With ControlDesk Next Generation’s Diagnostics instru- With ControlDesk Next Generation you can handle diagnostic
ment, you can work with diagnostic services and Java jobs identifiers from an ODX database in the same way as variables
described in the ODX database. The available services and from other sources such as the ASAM MCD-2 MC file. For
jobs are presented concisely in a tree structure for easy instance, diagnostic measurement identifiers can be displayed
finding and selection. You can select a service or job, together with signals from other sources on a common time
parameterize and execute it, and monitor the associated base in the same Plotter instrument and can be saved to
ECU responses and results. You can perform execution once the same measurement file. Diagnostic parameter identifiers
or cyclically. Diagnostic communication can be logged and can be adapted with ControlDesk Next Generation’s regular
saved to file. 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 moni-
tored on screen.
Quick and easy ODX-based ECU flash

programming with ControlDesk Next Generation.
Remote Access via ASAM MCD-3 D API

or ControlDesk’s Automation API
A COM/DCOM implementation of the standard automa- via a dedicated application programming interface (API)
tion interface according to ASAM MCD-3 D (v2.0.2) is pro- (p. 135). For example, ControlDesk’s tool automation feature
vided in conjunction with the MCD3 Automation Module provides the complete configuration of experiments and
(p. 153). ControlDesk Next Generation experiments are used extended and improved functionality for MCD-3 D. This
as MCD-3 D projects, but MCD-3 D requires the experiments allows ECU diagnostic tasks to be performed during test
to be preconfigured. Alternatively, many of ControlDesk’s automation, e.g., via AutomationDesk, which has separate
diagnostics functions can be accessed by automation script libraries for the two remote access options.
Order Information

ECU Diagnostics Module CDNG_DIAG

148
2016

Introduction
Signal Editor Module
Graphical Stimulus Definition
The Signal Editor Module is an optional software module Support of SCALEXIO®

used to graphically define and execute signal generators for Support of MicroLabBox and DS1007, including

stimulating model variables of real-time applications running multicore and multiprocessor systems
on dSPACE real-time hardware1). Support of PC-based simulation with dSPACE VEOS

Powerful editor for graphical stimulus definition Support of ASAM XIL API standard, including a new

Application Fields
Easy replay of measured data (incl. ASAM MDF) Data File Segment type that lets you replay referenced
Dynamic stimulus options (e.g., segment switching, ASAM MDF 4.x data with a flexible start time and
properties) duration
Independent execution of several signal generators
Signals can easily be used by AutomationDesk
Signal generators can be executed concurrently on
all nodes of a multiprocessor system
Synthetic signal com-
Software
posed of different seg-
ment signals (repeated)
Measurement signal
imported from the
measurement data pool
Hardware
Combination of the
synthetic signal and
the measurement signal
(multiplication)
Defining Time-Synchronous Stimulus Signals
Engineering
You can define several time-synchronous stimulus signals such 50 km/h.”). It is possible to use recorded signals from the
as sine, ramp and noise in the graphical Signal Editor, and measurement data pool in the Signal Editor for real-time data
couple changes in signal form to conditions (e.g., “Gener- replay. The Signal Editor saves the specified signal behaviors
ate a sine signal as long as the vehicle speed is lower than according to the ASAM XIL API standard.
Order Information

Signal Editor Module CDNG_SE

149
1)
Signal generation not supported for DS1103 and DS1104. 2016

Bus Navigator Module

Overview of Bus Communication
The Bus Navigator is a ControlDesk Next Generation com- ule supports dSPACE hardware and PC-CAN interfaces
ponent that lets you handle several types of items for all (e.g., dSPACE DCI-CAN1).
platforms in a project: CAN messages (incl. J1939), LIN NEW: Layout generation supported for Bus Manager
frames, and FlexRay PDUs that are configured by blocks (p. 54) applications
of the RTI CAN MultiMessage Blockset, blocks of the NEW: CAN FD support for SCALEXIO® and DCI-CAN2
RTI LIN MultiMessage Blockset, and settings in the dSPACE NEW: CAN bus communication replay via MicroLabBox
FlexRay Configuration Package. You can manipulate
messages, frames, and PDUs before transmission, exclude
them from being transmitted, etc. The Bus Navigator Mod-
Features of the Bus Navigator

The Bus Navigator has numerous features and lets you per-
form many tasks:
Support of CAN (incl. J1939), LIN and FlexRay buses
Support of dSPACE hardware and PC CAN interfaces
(e.g., DCI-CAN1, DCI-CAN2, Vector VN16xx)
Dedicated bus instrument for handling entire
messages, frames and PDUs
Create instruments to view RX messages, frames and
PDUs and configure and trigger TX messages, frames
and PDUs
Monitor and log bus data (CAN messages, LIN frames,
and FlexRay1) PDUs).
(Only for CAN) Replay logged CAN bus communications
CAN TX layouts for PC bus interfaces
Automation support for creating bus instruments and
controlling bus monitoring, logging, and replay The Bus Navigator
offers easy access to
CAN, LIN, and FlexRay
communication.
Handling CAN communication.
150
2016 1)
FlexRay support for PC bus interfaces only.

Introduction
Support for dSPACE Hardware
PC CAN Interface Hardware

DCI-CAN1 (USB-to-CAN interface)

DCI-CAN2 (USB-to-CAN and USB-to-CAN FD interface)

Calibration Hub (USB hub with two USB-to-CAN interfaces)

Application Fields
Real-Time Bus Interface Hardware
MicroAutoBox II

MicroLabBox

DS1103 PPC Controller Board

DS2202 HIL I/O Board



DS4302 CAN Interface Board

DS4330 LIN Interface Board

DS4505 Interface Board1)

Software
DS2671 Bus Board

DS2680 I/O Unit (with bus support)

Support for Third-Party Hardware
PC CAN Interface Hardware

Eberspächer FlexCard Cyclone II

Eberspächer FlexCard Cyclone II SE

Eberspächer FlexCard USB

Hardware
Kvaser LAPcan

Kvaser LAPcan II

Kvaser Leaf Light HS interface

Kvaser Leaf Professional

Kvaser Memorator Professional

Kvaser USBcan II

Kvaser USBcan Professional

Vector CANcardXL

Vector CANCardXLe

Vector CANcaseXL

Engineering
Vector VN16xx series

Vector VN5610

Vector VN7600

Vector VN89xx

151
1)
The DS4505 Interface Board requires additional DS4340 FlexRay Interface Modules. 2016

PC LIN Interface Hardware

Kvaser LAPcan

Kvaser LAPcan II

Kvaser Leaf Professional LIN (USB)

Vector CANcardXL (PCMCIA)

Vector CANCardXLe

Vector CANcaseXL (USB)

Vector VN16xx series

Vector VN89xx

PC FlexRay Interface Hardware

Eberspächer FlexCard Cyclone II

Eberspächer FlexCard Cyclone II SE

Eberspächer FlexCard USB

Vector VN7600

Vector VN89xx

Order Information

Bus Navigator Module CDNG_BNV

152
2016

Introduction
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.
Automation interface for measurement,
calibration, and diagnostics according to
Application Fields
the ASAM MCD-3 standard Validation of diagnostic functions

Continuous data acquisition in real-time raster ECU test automation

Remote control of ControlDesk Next Generation Optimization of control strategies on

via COM/DCOM API rapid control prototyping systems
Application Areas
The MCD3 Automation Module makes it possible to auto
Software
mate measurement, calibration, and diagnostic tasks with
ControlDesk Next Generation. It is typically used for:
Automated optimization of calibration parameters
at test benches
Data capturing, data analysis, and tuning of calibration
parameters in MATLAB® or other COM/DCOM-capable
applications

Hardware
Engineering
1)
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.
2)
Tool automation without ASAM MCD3 is included in ControlDesk Next Generation – Basic Version (p. 124) 153
3)
Please note: The MCD3 Automation Module is not supported by the ControlDesk Next Generation – Operator Version. 2016

Key Benefits
The MCD3 Automation Module features a COM/DCOM The diagnostic part of the automation interface lets you
interface based on the ASAM MCD-3 standard for auto- access the ECU via its diagnostic interface. During test
mating measurement, calibration and diagnostic tasks. The automation, this allows verification of the ECU diagnostics
interface lets you perform tasks such as uploading variables interface itself, besides providing assistance to comprehensive
associated with a device in ControlDesk Next Generation ECU function testing.
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.
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.
154
2016

Introduction
 Select ControlDesk experiment Automation and/or  Select ODX project
 Select ECU optimization tool  Select vehicle
 Select variable description  Select ECU (logical link)
COM / DCOM
 Upload available variables  Upload available services
 Calibrate offline or online and jobs
 Perform online/offline  Perform online/offline transition
Application Fields
transition  Execute diagnostic services
 Switch calibration page (send requests, receive
 Capture data synchronously ASAM- ASAM- responses)
to ECU raster or in polling MCD 3MC MCD 3D  Execute jobs
raster  Perform ECU flash programming
 Record data in measurement file
Automation of measurement, ECU

calibration and diagnostics with the
ASAM MCD3 MC and ASAM MCD3 D
standard automation interfaces.
Software
AutomationDesk
Remote Remote
Calibration (COM) Diagnostics (COM)
Library Library
ASAM MCD-3 MC ASAM MCD-3 D
MCD-3 Automation Module
ASAM MCD-2 MC Basic ASAM MCD-2 D
Hardware
(ASAP2) (ODX)
Application example:
ECU ECU
Interface Diagnostics AutomationDesk and ControlDesk
Database Module Module Database
Next Generation with the MCD3 Automation
Measurement and calibration
interfaces or protocols,
Diagnostic protocol, e.g.
Unified Diagnostic Services (UDS),
Module, the ECU Interface Module, and the
e.g., CCP, XCP, ... KWP2000 on CAN,
KWP2000 on K-Line
ECU Diagnostics Module for ECU access via
1)
calibration and diagnostic interfaces during

test automation.

MCD3 Automation Module CDNG_MCD3

1)
It is also possible to access dSPACE hardware. In this case, the Standard Platforms Module (p. 140) or the SCALEXIO 155
Platform Module (p. 142) is also required. 2016

Experiment and Visualization Software / MotionDesk
MotionDesk
3D online animation of simulated mechanical systems in real time
Highlights
Tight integration to ModelDesk and ASM

Enhanced support for all aspects of advanced driver

assistance systems (ADAS)
Intuitive graphical scene design

3-D object library with objects in COLLADA format

Powerful rendering engine guarantees detailed and

realistic visualization
Integrated 3-D Scene Editor

New instruments and instrument functionality

Application Area Key Benefits

When you develop a mechatronic control system such as an MotionDesk helps you get more out of your HIL simula-
advanced driver assistance system, you need to be certain tor, visualizing your simulation in virtual worlds that exactly
that it performs correctly. You can do this by running HIL represent the simulation scenarios. MotionDesk reads the
simulations. The best way to understand the behavior of a data from the HIL simulator and displays the animation of
simulated system is to use animated visualization in realistic the moving objects (vehicle, wheels, steering wheel, etc.)
3-D scenes. Combining a simulation system with real-time in real time, using the perspectives and render modes that
animation is the ideal way to get the whole picture. Since you choose yourself, to give you a clear understanding of
animations can be recorded and replayed, it is easy to how the simulated objects actually behave. You can store
compare different controller development strategies by us- the animations as experiment files and record video files to
ing overlay techniques. MotionDesk enhances the dSPACE document and illustrate your developments.
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 MotionDesk’s rendering engine guarantees detailed and
advanced driver assistance systems (ADAS), where the com- realistic visualization. Even complex scenes can be rendered
plexity of an action has to be seen to be understood. When at a steady rate of 60 frames per second, and beyond.
an ADAS is tested, the visualization must be realistic enough
for object recognition, and a high frame rate is crucial.
156
2016

Introduction
Main Features and Benefits
Feature Description Benefit
Instant animation Powerful rendering engine
Detailed and realistic visualization

Low latency between simulation and animation
Even complex scenes can be rendered at a steady 60

Intuitive motion model to accurately position the observer
frames per second
Application Fields
in the scene Realistic man-in-the-loop simulation
Smart objects for simulating and visualizing state-dependent

objects stimulated by the real-time simulation model (e.g.,
traffic lights, brake lights, direction indicators)
Multitrack mode Visual comparison of simulation run with reference data tracks Parameter behavior studies

Force vector visualization Forces represented graphically, e.g., by arrows
You can easily see which forces influence motion and how

3-D scene creation Graphical interactive scene design
Easy, intuitive operation

Scene creation integrated in MotionDesk
Operation from one tool

All done by drag & drop
Fast scene creation and modification

Automatic generation of guard rails, noise barriers and
Synergy with other tools for optimized workflow

environment objects
Automation API for remote-controlling MotionDesk

Automatic scene generation based on ModelDesk scenery
Software

types like city, highway, country road, alley, etc.
3-D Object Library 3-D object libraries based on standardized COLLADA file format Easy migration from older MotionDesk versions

Imports and migrates VRML2
3-D object libraries can be extended by user-defined

3-D object search via keywords and names
objects in COLLADA
Grouping 3-D objects
Better overview of all objects

Steadily growing library of 3-D objects: cars, houses, trees, etc.
Better scene structures

NEW: Animated characters (optional)

NEW: International traffic signs (optional)

Lossless, time-based data Time-based simulation data acquisition with equidistant
Synchronized replay of recorded animations in real time

acquisition time stamps
Hardware
Speed control Variable slow- and fast-motion replay
You can slow the animation to observe details and speed

it up during uneventful sections
Video file generation Animations exported into video files (AVI, MPEG-4, etc.)
Archiving and distributing important animations

Multi-PC support Scalable visualization system for interactive driving
More views increase realism during man-in-the-loop

simulators via Multi-PC Interface Kit or directly with simulation
SCALEXIO® simulators (p. 318)
NEW: Features in MotionDesk 3.7
Engineering
Instrument Panels Panels for logical grouping of instruments
Group instruments

for logically grouping Movable and scalable

instruments Optional background image

Minimizable: display replacement text to concentrate on

most important parameters
New instruments Multistate Text and Multistate Picture for conditional
Set up highly realistic head-up displays

display Visualize different textual information on different

conditions
Important for V2X and ADAS applications

Instruments can be displayed on several observers
Make instruments visible for several observers (cameras)

in MotionDesk without reconfiguring them
Single-sourcing of instruments

Instruments can be copied
Copy and paste instruments with all their attributes to

quickly set up multiple instruments.
157
2016

Order Information

MotionDesk MOTIONDESK_OFF

(Offline simulation with Simulink® and VEOS®)
Add-on: MotionDesk Hardware Access MOTIONDESK_HWA

Add-on: MotionDesk Animated Characters MOTIONDESK_ANIM_CHAR

Add-on: MotionDesk Traffic Signs MOTIONDESK_TRF_SIGNS

MotionDesk Multi-PC Interface Kit MotionDesk Multi-PC Interface Kit


Included Blockset MotionDesk Blockset to extend Simulink®
–
Required Integrated development environment MATLAB®/Simulink/Simulink® Coder™ (formerly Real-Time
–
Workshop®) from MathWorks
Operating system www.dspace.com/goto?os_compatibility
–
Optional dSPACE Simulator interface Real-Time Interface
RTI

SCALEXIO interface ConfigurationDesk
See p. 48
VEOS Platform for PC-based offline simulation
See p. 112

Required Recommended PC system Please visit our website at www.dspace.com/go/mdhwrequ
–
dSPACE Simulator DS1005 PPC Board (p. 376) or
DS1005

(PPC board) DS1006 Processor Board (p. 380)
DS1006

NEW: DS1007 PPC Processor Board (p. 386)
DS1007

Single-board hardware DS1103 PPC Controller Board (p. 358)
DS1103
MicroLabBox hardware Support for MicroLabBox
See p. 540
MicroAutoBox hardware Support MicroAutoBox II1)
See p. 548
SCALEXIO Support for SCALEXIO
See p. 318
Optional MotionDesk 10 megabit/s Ethernet card for each connected PC
MotionDesk

Multi-PC Interface Kit Multi-PC Interface Kit
1)
Various MicroAutoBox variants are available. Please contact dSPACE for advice on which variant you need.
158
2016

Introduction
Functionality at a Glance
3-D Animation of Simulated Mechanical Systems
Lossless, time-based data acquisition with time stamps Intuitive operation

Synchronized replay of different simulations in multiple tracks Support of multichannel visualization with highest

Replay function with faster/slower replay speeds graphical requirements (p. 169)
Up to 500 movable objects Optional: Import of road networks and predefined

Data acquisition from DS1005 PPC Board, DS1006 Pro- sceneries from dSPACE ModelDesk’s Road Generator
Application Fields
cessor Board, DS1007 PPC Processor Board, DS1103 PPC Examples: country roads, tree-lined roads, and
Controller Board, MicroLabBox and MicroAutoBox II urban areas
Data acquisition from running Simulink simulations Automatic 3-D scenery generation in MotionDesk,
Runs on the host PC (p. 168), separate PCs (p. 169), or including road embankment or border area, tree
VEOS (p. 112) spacing, reflector posts, street lights, building
File-based recording and analysis of motion data types, etc.
Video file generation (e.g., AVI, MPEG-4) to export Fine adjustments in MotionDesk’s 3-D Scene Editor
MotionDesk’s animations to high-quality video files
Software
Realistic Visualization
Connection of objects and model data streams via drag Various rendering techniques (wire frame, flat shading,

& drop Gouraud shading, textured)
Simulation of changing weather conditions like rainfall, Render modes selectable for whole scene and for indi-

fog, and snow vidual objects
Simulation of different light conditions and shadows Driver camera with realistic viewpoint (smooth follow

Freely configurable observers that can follow movable behavior)
objects with different behaviors Scene statistics

Hardware
Everything You Need in One Tool Preparation of HIL Tests via Offline Simulation
MotionDesk is easy to handle. You can perform all the im- You can use VEOS®, dSPACE’s platform for PC-based simula-
portant operations, such as 3-D scene creation, in one tool, tion, to set up models, layouts and tests in an early phase
mainly by drag & drop. before the HIL tests. With VEOS, you can configure and
Scene Navigator validate models, layouts and tests on a standard PC, without
2-D scene view any HIL hardware.
New rendering kernel MotionDesk, like all other dSPACE software for HIL simu-
Engineering
3-D library lation, interacts with VEOS just like with a HIL simulator.
Property grid MotionDesk is perfect for visualizing simulations, and as
Instruments soon as the HIL simulator is available, simulation runs can
be started without unnecessary delays.
Scene Property
Navigator grid
2-D scene
view
3-D library
159
2016

Optimized for Driver Assistance Systems

MotionDesk provides enhanced support for all aspects of be realistic enough for object recognition, and a high frame
advanced driver assistance systems (ADAS), where the com- rate is crucial. MotionDesk can simulate changing weather
plexity of an action has to be seen to be understood. When conditions, such as rain and snow, and offers highly realistic
camera-based ADAS systems are tested, the simulation must shadow visualization.
NEW: Pedestrian Detection

A critical part of ADAS systems is the real-time detection of means that pedestrian detection also recognizes road us-
pedestrians via camera. Pedestrians are hard to recognize, ers through their motion behavior and draws important
especially in cities or obscure corners, where colors, forms, conclusions on the road users’ possible motion trajectories.
and motion make precise detection much more difficult
than on a highway. ADAS pedestrian detection uses neural To test pedestrian detection systems via simulation, Mo-
networks which are trained on the basis of real data. This tionDesk 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 – it’s
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).
International traffic signs

The new traffic sign add-on to MotionDesk lets you exten- With this comprehensive library, you can conveniently and
sively test traffic sign recognition and visualization. It includes quickly test the functionality of ADAS systems in different
the complete German traffic sign catalog and all the most countries and for different road characteristics.
important traffic signs from China, Japan and the United
States, with more than 700 traffic sign models.
160
2016

Introduction
V2X systems
MotionDesk will support the development of V2X systems,
such as collision avoidance, intersection management, and
other communications-enabled vehicular safety systems.
Application Fields
Instruments
MotionDesk has several instrument types for observing the Numeric instrument, e.g., showing forces that affect

values of simulation variables. In MotionDesk’s Scene Viewer the vehicle
Software
you can attach instruments to movable objects or give them Gauge instrument, e.g., speedometer or engine speed

static positions in a scene. You can also specify several in- Bar instrument, e.g., showing the filling level

strument properties such as the size, position and color. The LED instrument, e.g., selected gear or indicator

following instrument types are available: NEW: Panels for logical grouping of instruments

NEW: Multistate Text and Multistate Picture for condi-

tional display
The instruments can be placed inside or outside the vehicle.
Hardware
Engineering
Multistate Picture instruments and Multistate Text instruments, especially You can group instruments in panels, which can be collapsed or
useful for V2X applications, such as emergency vehicle warning. expanded. Panels, including all their properties, can be re-used from
any observer, making it possible to single-source instrument definitions.
161
2016

3-D Authoring: Creating a Virtual World

Automatic scene generation from ModelDesk
ModelDesk and MotionDesk work together hand-in-hand in creating complex traffic scenarios for the development and
a tool chain. ModelDesk’s Road Generator (p. 285) lets you test of advanced driver assistance systems (ADAS).
define scenes for the automatic generation of 3-D sceneries For example, you can define country roads, tree-lined roads
in MotionDesk. and urban areas, and completely parameterize them with
ModelDesk’s Road Generator is the graphical user interface a road embankment or border area, tree spacing, reflector
for defining road networks and sophisticated road features. posts, street lights, building types, and so on.
Roads can be assembled from geometric segments or im-
ported. The road design interacts closely with MotionDesk Fine adjustments can be done afterwards in MotionDesk
to define the environment. The Road Generator is ideal for and its integrated 3-D Scene Editor.
A scene defined in ModelDesk and

automatically generated in MotionDesk.
Manual Scene Generation in MotionDesk

In addition to automatic scene generation in ModelDesk, 3-D CAD applications. The comprehensive library of 3-D
you can always design or modify scenes yourself. You can objects lets you set up scenes very fast by simply selecting
use the integrated 3-D Scene Editor to modify scenes for and positioning the objects. A 3-D Library Browser helps you
running 3-D animations of simulated data or create com- find the objects you need, for example, by keyword search.
pletely new scenes. Expanding the library is easy, as the 3-D object geometries
are described in the COLLADA standard. Road geometries
MotionDesk gives you a complete 3-D authoring package for automotive applications can be generated automatically,
so that you can create and modify virtual worlds easily. You using vehicle dynamics models such as the dSPACE ASM
can choose objects from libraries and import 3-D data from Vehicle Dynamics Simulation Package.
162
2016

Introduction
Integrated 3-D Scene Editor
3-D editor for assembling a scene from 3-D objects Library of generic objects and robotics objects

Interactive graphical scene design Custom library of 3-D objects

Scenes observable from any viewpoint 3-D Library Manager for importing and coloring objects

Easy, intuitive mouse navigation through scenesOpen, Object library management by grouping or by keywords

extendable 3-D object library Positioning, rotating and scaling 3-D objects in any direc-

Application Fields
Geometry objects in COLLADA standard (VRML2 tion (graphically via mouse, or by editing the property
geometries imported into the 3-D object library by 3-D values)
Library Manager) Wide range of textured, real-time-capable objects for

dSPACE object library of miscellaneous objects for vehicle dynamics simulation: chassis, wheels, roads, etc.
building a virtual world: ground plates, sky domes, Each object can have its own render mode

houses, trees, etc.
Software
Assembling a Scene Manually
To add objects to a scene, just
drag the objects from the 3-D ob-
ject 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
Hardware
range and obscure objects that are
far away.
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.
Engineering
Authoring at a Glance Animation with MotionDesk
3-D scenes assembled from 3-D library objects by Once created, a 3-D scene comes to life in MotionDesk.
drag & drop dSPACE Simulator provides the motion data, and Motion-
Templates for complete sceneries Desk moves the 3-D objects in the scene accordingly. For
Comprehensive automotive object libraries example, when a car is simulated, the motion of the chassis
NEW: International traffic signs (optional) is displayed with four individually rotating wheels, including
Import customized 3-D objects and graphics force vectors visualizing the forces between road and wheel.
In MotionDesk, you can adjust the transformations, scalings,

Automation API colors, and render modes of the objects.
MotionDesk can also be remote-controlled from other tools,
such as dSPACE’s ModelDesk, via a publicly available au-
tomation interface. External tools can create a scene and
add objects to it, start or stop the simulation, and switch
to full screen mode.
163
2016

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.
Main Features Typical Applications

Synchronized replay of several simulations
Parameter behavior studies
Transparent overlaying of objects
Reference comparisons
Equidistant time stamps

Comparisons Technology
The multitrack mode in MotionDesk is a smart way to visual- To replay several simulations synchronously, MotionDesk
ize simulations, allowing you to integrate several simulations offers two important features:
in one single animation. The method is ideal for reference Time stamps for simulation data
comparisons and in all cases where strategies for a particular Several replay tracks
maneuver need to be assessed. For example, different vehicle You can synchronously replay any simulations that are re-
dynamics strategies can be compared with one another in corded on the same time basis. The animated objects can
the specification phase, and later, actual results can be tested be cloned as required and assigned to different tracks. You
against a reference. This is also an ideal way to document can also give the objects different colors and render modes
results visually. so that the individual simulations are clearly distinguishable.
Track Generation Data Sources

The tracks are created in MotionDesk’s Scene Navigator. Tracks can receive their data from different sources.
Track generation automatically creates clones of the mov- Online simulation
able objects and observers in the scene. Simulink offline simulation
Stored simulation (MDF files)
If simulations from different sources need to be compared,
they all must use the same time basis.
164
2016

Introduction
Maneuver Comparisons
MotionDesk’s multitrack mode makes maneuver compari- replays data from previous simulation runs. These tracks also
sons easy and clear. It synchronously replays multiple simu- contain clones of the moving objects defined for reference.
lations that have been assigned to different tracks. One Synchronized replay makes it easy to pick the best strategy
track acts as the reference, playing either online, offline, or for your control application.
stored simulations. Each of the other tracks synchronously
Application Fields
Braking on a Split-µ Surface
The same maneuver is shown with and without Electronic
Stability Program (ESP). MotionDesk displays the two dif-
ferent simulations in one animation.
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.
Software
Both cars brake on a partially slippery surface (splitµ).
The yellow car starts skidding and turning.
Hardware
At the end of the maneuver, the red car is still on track,
Engineering
but the yellow car turned around the yaw axis.
165
2016

MotionDesk Blockset: Model and Animation

Prepare for Animation
This blockset lets you run animations as early as the control and create references. MotionDesk is therefore the ideal
design stage. You can perform the usual ECU-based simu- tool to visualize certain features and their results at the very
lation and animation, and also check behaviors very early beginning of a project.
The Blockset at a Glance

Interface between simulation platform and Motion- Single communication block with dialog pages to easily

Desk configure data transfer
Visualization of PC-based Simulink simulations Fast model initialization in Simulink

Visualization of real-time simulations Fast computation for real-time execution

Support of simulation platforms: DS1005, DS1006, Kinematic chains (e.g., robot kinematics or wheel

DS1007, DS1103, SCALEXIO, MicroLabBox, motion in relation to the vehicle) created by connecting
MicroAutoBox II, VEOS, and Simulink transformation blocks in Simulink
Transformation blocks for easy description of the 3-D Ready-to-use demo models for vehicle and robotics

objects’ positions and orientations Easy connection of existing vehicle models via

kinematics block
Special blocks collect the motion data and time-stamp it in MotionDesk.
166
2016

Introduction
Connect 3-D Objects and Models
Six Degrees of Freedom Transform State Variables
Real-time models in Simulink use state variables, such as a The MotionDesk Blockset provides Simulink blocks that
wheel’s steering angle or position in relation to the suspen- prepare the real-time model for 3-D animation and make
sion. In contrast, 3-D animation requires a system with 6 the data streams available in MotionDesk. During Simulink
degrees of freedom to determine the objects’ positions and simulations and real-time simulations, the Simulink blocks
orientations in the 3-D world. The MotionDesk Blockset directly transform state variables into the required 6 degrees
Application Fields
lets you transform the state variables into these 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.
Coordinate Transformation
Simulink blocks for 3-D coordinate transformation
Software
Convenient setup of kinematic chains
Euler or Cardan angle interpretation
Transformation from rotation to translation, and vice versa
Hardware
Connection to 3-D objects, data collection and transfer to MotionDesk:
all done in the Simulink blocks and dialogs.
Maneuver Synchronization with Multitrack Support

The blockset supports maneuver synchronization with all can also synchronize animations to certain events – which is
Engineering
data sources (dSPACE real-time hardware, VEOS, and Simu- useful if you want to watch the animation only at a certain
link simulation). At the beginning of a maneuver, you can speed or milestone.
reset time stamps used for the animation to zero without af- Special blocks collect the motion data and time-stamp it
fecting the current simulation time. This provides convenient in MotionDesk.
handling when new maneuvers start. In MotionDesk, you
167
2016

Typical Application: Automatic Driving Maneuvers

Control and Visualize
One typical application scenario is the visualization of auto-
ControlDesk
matic driving maneuvers calculated by dSPACE Simulator. Next Generation
ControlDesk is used to control and monitor the simula-
tion. ControlDesk and MotionDesk can run on the same
PC, since there is no need for interactivity with low latency
requirements.
SCALEXIO MotionDesk
Data Transfer
MotionDesk visualizes the simulation results in a 3-D scene. Simulator to the host PC via dSPACE link boards. To display
dSPACE Simulator calculates the absolute positions and ori- ControlDesk and MotionDesk on two separate monitors,
entations of the movable objects for the visualization. Data the graphics board must have two connectors (dual head).
for ControlDesk and MotionDesk is transmitted from dSPACE
Further Application Fields

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

Introduction
MotionDesk on Multiple PCs
Improved Visualization
MotionDesk is ideal for applications in which a human driver ent views of the same scene at the same time. ControlDesk
controls a virtual car. Such tests are important if you want to and MotionDesk run on separate PCs, which improves the
run not only a suite of automated tests, but also interactive visualization performance and provides the full functionality
tests. The driver feedback obviously has to be highly realistic, and performance of both tools. Moreover, you can add any
which requires a high frame rate and low latencies. number of MotionDesk PCs to set up a driving simulator with
Application Fields
For even greater realism, MotionDesk provides scalable visu- several screens for the most realistic visualization.
alization for interactive driving, for example, displaying differ-
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 interac-
Software
tive driving simulator.
Hardware
Engineering
A typical multiPC setup (SCALEXIO) with MotionDesk: The human driver can see different views of the same scene simultaneously for greater realism.
169
2016

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
Required only for systems based on peripheral high-speed Full ControlDesk functionality and maximum Motion-

(PHS) bus technology Desk performance at the same time
Extension to MotionDesk for highest graphical Scalable number of MotionDesk PCs for multichannel

requirements visualization (e.g., for interactive test drives)
ControlDesk and MotionDesk run independently on Smart solution for setting up driving or flight simulators

different PCs Synchronized animation start/stop on all MotionDesk PCs

Connect Multiple PCs Network Connection

The MotionDesk Multi-PC Interface Kit is an extension to The MotionDesk Multi-PC Interface Kit allows multi-faceted
MotionDesk that enhances visualization performance and visualizations by letting you connect any number of Mo-
allows the same experiment to be visualized from different tionDesk PCs in the real-time data stream. The hardware
points of view – and from different PCs. A typical applica- is installed in your dSPACE Simulator. The connection to
tion is man-in-the-loop: You cannot get the most realistic the MotionDesk PCs is via Ethernet, so you only need an
impression of the simulation unless the driver sees different Ethernet card in the PCs for high-speed data transfer and
perspectives of the scene, such as the front view, side view, minimum latencies.
and rear view.
170
2016

Introduction
Hardware Details Software Details
ISA bus board for providing the real-time data (DS1005 Programmable via a network sender block
and DS1006 supported) (included in MotionDesk Blockset))
Ethernet connection between PCs
Application Fields
System Requirements for Software Requirements for
MotionDesk Multi-PC Interface Kit MotionDesk Multi-PC Interface Kit
Same as MotionDesk, plus MotionDesk for each PC
dSPACE Simulator (DS1005 or DS1006)
10 Mb/s Ethernet card for each connected PC
Software
Hardware
Engineering
171
2016

Test Automation Software / AutomationDesk
AutomationDesk
Powerful test authoring and automation tool
Highlights
Graphical description of test routines

Advanced custom library concept

Automatic report generation

Offline test execution and development

Certified for ISO 26262 and IEC 61508

NEW: Signal-based test authoring

NEW: XIL API support; Automatic migration from

HIL-API-based simulator access
Application Areas
AutomationDesk is a powerful test authoring and automa- engineers increase test coverage and improve ECU software
tion tool for testing electronic control units (ECUs). Au- quality while saving time and costs.
tomationDesk users can create and edit test routines in AutomationDesk lets you describe test routines graphically,
a graphical format without requiring programming skills. be it block-based test authoring based on library elements,
AutomationDesk’s interface libraries, compliant to the ASAM or signal-based test authoring based on stimulus signals
standards, allow seamless reuse of automated tests across and evaluation of captured signals.
different development stages such as MIL and SIL simulation AutomationDesk’s library concept, including the Frame-
with VEOS®, (dSPACE's platform for PC-based simulation) work Builder and Test Builder, helps develop and maintain
and HIL simulation with SCALEXIO®. templates for the test implementation – independent from
the current tests.
Key Benefits AutomationDesk has been certified by TÜV SÜD for test-
AutomationDesk provides libraries containing a large number ing safety-related systems according to ISO 26262 and IEC
of predefined test steps for easy access to the HIL simulator, 61508. The TÜV SÜD certificate confirms AutomationDesk's
a failure insertion unit (FIU), or calibration or diagnostics suitability for developing and testing safety-related systems
software, for example. With AutomationDesk, tests can in automotives, commercial vehicles, aerospace and many
be executed 24 hours a day, seven days a week, letting other industries.
Advanced Sequence Builder Graphical test development

Librarybased test development via drag & drop

Access to simulation platforms and tools from within the automation sequences

Test project management and execution 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

172
2016

Introduction
Automation libraries ASAM XIL API library to access simulation platforms , failure insertion units, and HIL simulators compliant

with the ASAM XIL 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
Application Fields
Access to diagnostics tools like ControlDesk Next Generation and Softing DTS 7 via ASAM MCD3 D

Access to MATLAB®

Convenient access to tools in the dSPACE tool chain

Electrical failure simulation systems
RealTime Test Manager
ModelDesk
MotionDesk
Open architecture Open COM API enables remote execution of tests, e.g., by test management tools

Edit and execute Python code or call Python scripts in AutomationDesk

Introduce and maintain custom libraries to develop and maintain reusable, testdomain specific blocks

Software
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 automation artifacts in projects and libraries

Test documentation Automated generation of test reports in PDF or HTML

Report library to define the contents of the generated report

Test Builder library Readytouse library of templates for tests, test steps and further blocks

Framework for test development with implicit uniform and structured reporting

Framework Builder library Library that allows building up highly customizable templates as a test framework

Build up own templates (e.g., for test steps and tests) like in the Test Builder library

Templates feature implicit functions: e.g., for reporting and exception handling

Templates can be maintained with the AutomationDesk library mechanism

Hardware
Evaluation library Powerful evaluation of measured signals

Automatic report generation, including plotted signals

Order Information

AutomationDesk Basic AUD_BASIC

AutomationDesk – Automation Server AUS_BASIC

Relevant Software Engineering

Required Operating system: www.dspace.com/goto?os_compatibility
–
Optional ControlDesk Next Generation
See p. 120
SYNECT Test Management
See p. 294
VEOS
See p. 112
PLATFORM_API

Failure Simulation API Package
FAILURE_SIM_API

RealTime Testing
RTT

173
2016

NEW: Features of AutomationDesk 5.0/5.1

The new version offers many improvements in usability and
handling and several innovative features for test automation.

SignalBased Testing Graphical description of signals for stimuli and evaluation
Intuitive test authoring as on a piece of paper

XIL API 2.0 MAPort Successor of the HIL API MAPort 1.0
Switch from HIL API to XIL API without migration effort

support Automatic migration from HIL API to XIL API
Seamless use of simulation platforms from different vendors

Functional enhancements: e.g., stimulating time intervals of
Gain from functional enhancements

measured signals
Platformindependent handling of simulation applications

XIL API 2.0 EESPort Hardwareindependent function blocks for failure insertion
Easy to use blocks for all failure insertion systems

support units (FIU) Access to dSPACE FIU systems, independently from

Convenient blocks for the most common FIU test scenarios
Base library enables using the whole range of supported

EESPort functions
MotionDesk Library Library to automate MotionDesk
Easy implementation of tests where online animation is

involved: e.g., tests for camera based ADAS systems.
Variable Mapping Mapping Editor
Convenient access to variable mappings

Clear allocation of variables, signals, parameters and
Centralized mappings

variants Exchangeable mapping definitions compliant with
ASAM XIL
Import/export of ASAM XIL mapping XMLs
Mapping Viewer

Overview window with information on current variable
mapping
Create and manage mappings in AutomationDesk or
Certified for SafetyRelated Applications According to ISO 26262 and IEC 61508
AutomationDesk 5.0, like its predecessor AutomationDesk IEC 61508 and ISO 26262
4.1, has been certified by TÜV SÜD for testing safety-related IEC 61508 is the internationally recognized generic standard
systems according to ISO 26262 and IEC 61508. The TÜV for the development of safety-related electronic systems.
SÜD certificate confirms AutomationDesk's suitability for de- ISO 26262, the standard for functional safety in passenger
veloping and testing safety-related systems in automotives, vehicles, replaces IEC 61508 for the automotive industry.
commercial vehicles, aerospace and many other industries.
It also confirms the high quality of the development process
and extensive quality assurance performed for Automa-
tionDesk 5.0.
AutomationDesk is the first hardware-in-the-loop test auto-
mation software product to be awarded such a certificate.
Together with the new AutomationDesk Safety Manual,
the certificate gives users a valuable support for validat-
ing and qualifying safety-related systems according to ISO
26262 and IEC 61508, and for using AutomationDesk 5.0
for developing and testing them.
174
2016

Introduction
NEW: Signal-Based Test Authoring
Application Fields
Software
Hardware
n Intuitive test authoring as on a piece of paper
Drag & drop to define which stimulation signals and
n
capture signals to evaluate
One block solution with implicit evaluation and
n
descriptive reporting
Wide variety of evaluation methods
n
New “InsideRegion” evaluation functionality:
n
allows time- and amplitude-tolerant evaluations
Engineering
175
2016

NEW: Variable Mapping
The new Mapping Editor: Assign variables of a simulation model (left) to an alias in an editable mapping table (right).
Convenient Access to variable mappings

Centralized mappings

XIL API-based mapping according to ASAM XIL

AutomationDesk’s 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.
176
2016

Introduction
Test Automation Software Overview
The modular packaging of dSPACE’s Test Automation Soft-
ware lets you select the packages you need for your auto-
mation tasks, and add other modules later on if necessary.
Application Fields
AutomationDesk
AutomationDesk –
AutomationDesk
Versions Automation Server
Basic Version
Basic Version
Platform
support Platform API Package
Software
Failure Simulation Package
Additional
functionality
Real-Time Testing
Hardware
AutomationDesk Basic (p. 172) NEW: Failure Simulation Package (p. 198)
Full version of AutomationDesk NEW: XIL API EESPort in .NET: Programming interface
to all dSPACE and third-party failure insertion units in
AutomationDesk – Automation Server (p. 189) compliance with the ASAM XIL API EESPort standard
A tool variant of AutomationDesk (without a graphical user Failure simulation API based on tool automation of
interface) for executing implemented AutomationDesk tests: ControlDesk Next Generation
Parameterization and execution of existing tests NEW: ASAM XIL EESPort-compliant access via graphical
For test management applications such as SYNECT Test user interface in ControlDesk Next Generation
Management, batch scripts in Python, and customized
Engineering
operator UI applications Real-Time Testing (p. 190)
Python-based real-time test automation
Platform API Package (p. 196) 100% reproducible real-time tests executed synchro-
XIL API MAPort support in .NET (successor of the HIL API): nously with the simulation model
ASAM XIL API-compliant interface to all dSPACE simu- Easy integration into user-defined test frameworks
lation platforms (AutomationDesk or others)
Platform Management API: Interface for configuring Support of VEOS®, dSPACE’s platform for PC-based
dSPACE platforms offline simulation

HIL API MAPort (Model Access port) implemented in
Python and .NET: Interface to ASAM HIL API-compliant
simulation platforms
RTPLIB2: Proprietary interface to dSPACE's HIL and RCP
platforms
177
2016

Graphical Setup of Test Sequences

Block-Based Test Authoring
AutomationDesk’s Sequence Builder provides a graphical, Python-based test development. Typically, graphical devel-
UML-compliant environment for developing automation opment is used to describe the control flow and to access
sequences. The Sequence Builder and its overview panel devices such as hardware or other software. Python scripts
even help you keep track of very large sequence structures. are used for implementing algorithms or for user-specific
AutomationDesk combines and integrates graphical and extensions.
Editor for
Developing and managing automation Pythonbased
sequences with AutomationDesk. test steps.
Signal-Based Test Authoring

Signal-based test authoring lets to describe tests intuitively
as if on a piece of paper. You can use a set of standard
signals to define real-time stimulation and evaluation rules
for captured signals. Together with the new ‘inside region’
evaluation function, which allows time- and amplitude- toler-
ant signal evaluations, a powerful supplement to the given
‘block-based’ test authoring is now available.
Segment-wise stimuli or evaluation rules can be combined.
Conditions for a transition between signal segments as real-
time observers can be defined to check preconditions for
following segments or as a dynamic wait function for syn-
chronizing segments or for passed/failed evaluations.
178
2016

Introduction
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.
Application Fields
This method speeds up the test development process and
increases efficiency. Different custom libraries can be shared
between various AutomationDesk installations via the file
system or via a version control system.
Create your own custom libraries for

tests and basic test steps.
Software
Advanced Library Concept
The Test Builder is a ready-to-use library to comfortably set Ready-to-use test framework

up test frameworks. It offers a ready-to-use test frame- Test and test step templates

work with test and test step templates, including exception/ Implicit reporting

verdict handling and reporting. The Test Builder elements Standard HTML and PDF style sheets for detailed and

are implemented through the Framework Builder library. brief reports
Hardware
Exception and verdict handling

Based on the Framework Builder

Customizable and transparent

Engineering
179
2016

Test Debugging and Data Comparison

Debugging Test Sequences Breakpoint
If an error occurs during test execution, AutomationDesk’s
Debugger makes it easy to find its source. You can insert
breakpoints into your test sequence and make the test ex- Current position of
ecution stop automatically at these points in debug mode. the Debugger
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 Breakpoint
can be changed during the debugging process to ensure

that the tests run with correct variables. Step-by-step execu- The Debugger lets
tion supports fast, efficient error-finding because you can you go through your
investigate specific potential error sources. test sequence step
by step.
The toolbar of
AutomationDesk’s
Debugger.
Disabling Tests and Test Steps

AutomationDesk makes it considerably easier to verify test
sequences while they are being developed. You can disable
single test steps or sequences by commenting them out.
This is extremely helpful when identifying errors.
Disabling test steps.
180
2016

Introduction
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 de-
fined limits. For example, you can specify upper and lower
bounds to evaluate whether a specific signal is above or
Application Fields
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:

Binary operations (addition, multiplication, less than, etc.)

Calculating gradients and integrals

Shifting, cropping, and resampling signals
The recorded data can be compared with the reference data.
Calculating the minimum value, mean value, minimum

delta x, etc.
Software
Hardware
Engineering
181
2016

Test Project Management in AutomationDesk

Managing Project Data
AutomationDesk’s Project Manager is the ideal way to or-
ganize 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 ar-
ranged 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

AutomationDesk’s libraries can be set to offline mode, so
tests that use them are executable even if the required ex-
ternal software or hardware is not available. The test steps
then use default behavior to enable test execution. For ex-
ample, 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.
Libraries in AutomationDesk.
Automatic Report Generation

AutomationDesk can automatically generate report docu-
mentation 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 The Test Builder report provides a clear and structured
generated with user-defined XML style sheets. overview of all test cases.
Version Control of Projects and Custom Libraries Version control interface.

With the AutomationDesk version control interface, you can
integrate version control systems that have the Microsoft®
Source Code Control (SCC) interface, such as PTC® Integrity,
Apache Subversion (SVN)1), or IBM® Rational® ClearCase®, etc.
182
2016 1)
Requires an installation of the SCC API plug-in from PushOk Software.

Introduction
Automated HIL Testing, Diagnostics & Calibration
from a Single Source
Complies with ASAM MCD-3 D (Version 2.0.2)
Diagnostics and hardware-in-the-loop (HIL) testing are
Complies with ASAM MCD-3 MC
brought together in AutomationDesk. You can use it to
ODX-based diagnostics
remote-control and automate the diagnostics functional-
Calibration and diagnostic functions based on
ity of ControlDesk Next Generation, dSPACE’s universal
Application Fields
ControlDesk Next Generation tool automation experiment software. This means you have a completely
ControlDesk Next Generation Access Library
integrated tool chain for HIL testing, ECU calibration,
Convenient blocks for diagnostics
measurement tasks, and diagnostics from a single source.
Convenient access to fault memory: e.g., Direct Read
Compatibility problems are a thing of the past.
DTCs, Direct Clear DTC, Direct Clear All DTCs
AutomationDesk can be used to automate

and remote-control ControlDesk’s ODX- AutomationDesk
Software
Remote Remote ControlDesk
based diagnostic functionality, and to au- Calibration (COM) Diagnostics (COM) Next Generation
tomate measurement and calibration tasks. Library Library Access
It accesses ControlDesk via the ASAM MCD-

ASAM MCD-3 MC ASAM MCD-3 D Tool Automation
3 automation interface or, far more conve-
MCD-3 Automation Module
niently, via ControlDesk Next Generation's
tool automation library. You can build test ASAM MCD-2 MC Basic ASAM MCD-2 D
(ASAP2) (ODX)
sequences graphically in the familiar way in ECU ECU
Interface Diagnostics
AutomationDesk, using the Remote Diagnos- Database Module Module Database
Hardware
tics (COM) library or the Remote Calibration Measurement and calibration Diagnostic protocol, e.g.
interfaces or protocols, Unified Diagnostic Services (UDS),
(COM) library. These are AutomationDesk e.g., CCP, XCP, ... KWP2000 on CAN,
KWP2000 on K-Line
libraries of test steps for automating access
1)
to ControlDesk’s diagnostics, measurement,

and calibration functionalities. Application example: AutomationDesk and ControlDesk Next Generation with the
Successfully integrating ECU diagnostics into MCD3 Automation Module, the ECU Interface Module, and the ECU Diagnostics
the hardware-in-the-loop (HIL) testing of ECU Module for ECU access via calibration and diagnostic interfaces during test automation.
software is becoming more and more impor-
tant. AutomationDesk is a standard solution for automated measurement and calibration tools which comply with
Engineering
HIL testing that can address a variety of software tools. the ASAM MCD-3 MC standard, like ETAS INCA or Vector
These include ControlDesk Next Generation from dSPACE CANape.
and DTS from Softing (standard AutomationDesk), but also
All Tools from One Source

By using ControlDesk Next Generation and AutomationDesk, diagnostic tools from a single source, with no complica-
you avoid the compatibility problems that often arise when tions. The smooth interaction between AutomationDesk and
tools from different vendors have to be integrated. dSPACE ControlDesk gives you maximum convenience and func-
offers you HIL systems plus measurement, calibration, and tionality for successful HIL testing.
183
1)
It is also possible to access dSPACE hardware (this requires the Standard Platforms Module, 2016
Please see product information "ControlDesk® Next Generation").

Test Automation
Well-Planned Libraries for Reusability
To run HIL test systems efficiently in terms of time and cost, The objective is to create basic test steps, save them to
test automation has to be planned carefully. Usually thou- libraries and reuse them for other tests.
sands of relevant tests have to be defined and handled. 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 a few modifications.
Building a Good Library Concept for Test Automation

dSPACE Engineering Services has years of experience in The services include:
creating library concepts. Defining test processes
So when you build your library concept, you can call on our Implementing projects
Engineering Services to help you get started in test auto- Resident engineers
mation. The dSPACE engineers will help you set up a test Creating the test template
automation infrastructure, including the library concept. Creating the library concept
You will benefit from their knowledge of the hardware and Providing exemplary test implementations
software and from their accumulated project experience. Managing data and results
Integrating third-party software
Connecting the test software to existing tools
Testing
productivity
(number
of tests
performed)
Successful test
automation
Additional test
engineers
New HIL project -> re-organisation
-> adaption of tests Saturation
New ECU variant

-> test variants needed
Working without a library

concept, gives you quick
Start of test
results, but is not efficient
implementation enough in the long run.
and execution
The initial investments for
Development of
systematic test Time
a good library concept pays
automation concept for itself in terms of efficiency
and cost-savings.
184
2016

Introduction
Tool Interfaces
Support of the XIL API Standard
Independent of Specific Simulation Hardware Advantages for Users
The ASAM XIL API V2.0 standard is the next generation The Platform API Package for
of the ASAM HIL API standard. The XIL Model Access port AutomationDesk supports the
(MAPort) supports test bench access at all stages of the new Version 2.0 of the XIL API
Application Fields
function development process: MIL (model-in-the-loop), SIL standard. The dSPACE test auto-
(software-in-the-loop), PIL (processor-in-the-loop) and HIL mation software makes it easier
(hardware-in-the-loop) simulation. The XIL Electrical Error to use tests with any HIL simu-
Simulation port (EESPort) in ASAM XIL controls electrical error lator. This increases test reuse,
simulation hardware. It lets you set different types of errors. helping to protect investments
and reduce development costs
The XIL API standardizes the interface between test hard- and time. Moreover, you only
ware and software. It lets developers reuse test cases and have to buy one program and
decouples test automation software from test hardware. learn how to operate it – even
You can: if you want to access different
Software
Reuse automated tests on test systems from different simulators.
vendors
Reduce training costs for employees
Improve the transfer of know-how from one test bench
to another
Hardware
NEW: XIL API Support in Platform API Package XIL API Support in Failure Simulation API Package
The Platform API Package supports the MAPort implementa- XIL API EESPort (Electrical Error Simulation port) imple-
tion of the XIL API standard to access a simulation platform: mented in .NET, in compliance with the ASAM XIL API
Configure the simulation platform EESPort standard
Read and write to scalar and vectorized variables Access to all dSPACE failure insertion units in automa-
Capture data by using complex trigger conditions tion scenarios from your own test scripts and applica-
Stimulate variables of a real-time application via a signal tions
description set, such as the Signal Editor Module in Con-
trolDesk Next Generation
Engineering
XIL API Vendor Switch XIL API Convenience Library

Easy switching between vendor-specific XIL API imple- Quick, convenient XIL-API-based operations – detailed
mentations XIL API background information not required
Convenient exchange of object models from different Easy handling of read/write/capture/signal generator
vendors actions
Easy to use blocks for failure simulation control
185
2016

Interfaces to dSPACE Tools

ControlDesk Next Generation ModelDesk
Convenient, comprehensive access to all ControlDesk Next ModelDesk tool automation as preparation for ADAS

Generation features for: tests
Measurement and calibration Remote control of ModelDesk to handle parameters,

Diagnostics roads, maneuvers and traffic
Open project/experiment
Real-Time Testing Activate parameter set
Real-Time Testing library for convenient script management Access to parameter handling

Easy integration into AutomationDesk tests Modify parameters
Download parameters
RTI CAN MultiMessage Access to road and maneuver handling

Solution to access RTI CAN MultiMessage Blockset
Activate and download roads
functions from within AutomationDesk Activate and download maneuvers
Convenient access to RTI CAN MultiMessage Blockset Modify road and maneuver parameters (surface
parameters and manipulation options conditions, velocities)
CAN bus configuration via AutomationDesk blocks: save,
restore and manipulate RTI CAN MultiMessage properties NEW: MotionDesk
Remote-control MotionDesk

Support of camera-based ADAS systems tests

Interfaces to Third-Party Tools

AutomationDesk can also integrate third-party tools, such ASAM interface
as CANscope, CANstress, CANoe, and CANalyzer from Access to calibration tools like ControlDesk Next

Vector. Please contact dSPACE for details on supported Generation, ETAS INCA, and Vector CANape, via
third-party tools. dSPACE also has experience in connect- ASAM-compliant interfaces (e.g., ASAM XIL, ASAM
ing AutomationDesk to third-party hardware-in-the-loop MCD-3 D, ASAM MCD-3 MC)
systems, provided the systems support the HIL API standard Access to diagnostics tools like ControlDesk Next

properly, and offers engineering support on request. Generation, and Softing DTS 7 via ASAM MCD-3 D
(Version 2.0.2)
Access to simulation platforms via ASAM XIL MAPort

Access to failure simulation systems via ASAM XIL

EESPort
MATLAB
Access to the MATLAB Command Window

Data exchange between AutomationDesk and MATLAB

Remote execution of MATLAB commands

Use of M files and MAT files

186
2016

Introduction
Integration of AutomationDesk in Typical Tool Chains
Connection to dSPACE SYNECT®
SYNECT is data management and collaboration software test results, etc.) it also handles data dependencies, versions
that focuses on model-based development and ECU testing. and variants, as well as links to the underlying requirements.
Designed to help you manage data throughout the entire SYNECT Test Management is a SYNECT module which gives
development process (models, signals, parameters, tests, you a convenient connection to AutomationDesk.
Application Fields
 Test specification and management
in SYNECT Test Management
Input
Test
Requirements SYNECT Test Management Steps
Software
Execution Results
 Test implementation and execution

in AutomationDesk
Tests
Hardware
AutomationDesk
Off-the-Shelf Integration with AutomationDesk Test Planning and Execution

You can use implemented test cases in AutomationDesk SYNECT Test Management easily integrates with test
projects or libraries as a source for test cases in SYNECT automation tools such as AutomationDesk from dSPACE
Test Management. and BTC EmbeddedTester®. It does this via adapters that
Engineering
control the test automation tool.
Importing Requirements, Specifications, and Tests To carry out tests, you can set up execution plans contain-
You can import existing tests into SYNECT Test Management ing test cases and add tests to them. An execution plan is
to define your tests and collect source data from several a list of tests that have to be executed. It can be based on
tools: various criteria: For example, it can include all your tests for
 Test lists from Microsoft® Excel® one variant or for one ECU function.
 Test implementations from AutomationDesk,
BTC EmbeddedTester®, MATLAB®, or Python
187
2016

RemoteControlled Test Runs

COM/DCOM Interface
AutomationDesk has a COM-based application program- Designing interactive user interfaces: You can create your

ming interface (API) for remote-controlling and automating own test UIs to reduce complexity, for example.
selected AutomationDesk functions. These are some of its Connecting other tools to AutomationDesk: For example,

typical use cases: parameterize your test data, in Microsoft® Excel® and call
Programming batch processes (with Python, Visual Basic, the AutomationDesk test sequences from Excel.
C++, etc.): You can program flexible control structures
which skip single test sequences if necessary or execute
test projects successively.
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, Use Cases
folders, tests, and custom libraries as XML files. Using XML XML files open up numerous new application options, such as:
to import and export test descriptions means that tests can Reading and reviewing tests without AutomationDesk
be exchanged between different test tools. For example, to Converting tests into different file formats
be imported from a third-party tool or from a proprietary Migrating tests that were created with proprietary tools
test description, a test simply needs to be converted into into AutomationDesk
AutomationDesk's XML format. Generating tests from third-party tools, such as Microsoft®
Excel®, and integrating them into AutomationDesk
Excel®
Third-party or
proprietary test
description
AutomationDesk
Converter/XSLT Excel-to-AutomationDesk
style sheet converter
Export
AutomationDesk
Import XML
188
2016

Introduction
AutomationDesk – Automation Server
AutomationDesk – Automation Server is a server variant
without a graphical user interface. The Automation Server
is accessed and remote-controlled via the COM/DCOM in-
terface, 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 wher-
Application Fields
ever the comprehensive functions of the full version are
not required, for example, in automated test execution on
hardware-in-the-loop simulators.
AutomationDesk – Basic Version AutomationDesk – Automation Server
 Development environment for tests  Tool variant without graphical user interface
 Developing libraries  Planning, parameterizing and executing
Software
 Test execution existing tests
 Note: To access dSPACE platforms,  Client applications: batch scripts, Excel,
you need the Platform API Package. operator UI, test management tools like
SYNECT Test Management, etc.
Hardware
AutomationDesk –
Automation Server
Engineering
189
2016

Test Automation Software / RealTime Testing
RealTime Testing
Pythonbased realtime test automation
Highlights
100% reproducible real-time tests executed synchro-

nously with simulation model
Several independent test scripts can be executed

concurrently
No model modification necessary for real-time testing

Easy integration into user-defined test frameworks

(AutomationDesk or others)
Support of VEOS®, dSPACE’s platform for PC-based

offline simulation
Key Benefits
Automated testing is usually performed by executing tests the model, so all test actions are performed on a real-time
on a standard PC connected to the hardware-in-the-loop basis – 100% reproducibly. This opens up expanded test op-
(HIL) system. However, this method often cannot cope where tions with dSPACE Simulator. Reactive tests which respond to
greater timing precision is required – for example, if ECU changes in model variables within the same simulation step
interaction has to be captured and responded to within just can be implemented. Time measurements in tests are also
milliseconds. Real-Time Testing with its Python scripts for real- far more precise, as there are no latencies in communication.
time testing is the answer. The scripts run on the processor Simulation step size is now the only limit to the maximum
board of the HIL system in real time, i.e., synchronously with time resolution of measurements.
Example Use Cases for Real-Time Testing

Testing reactivity in a range of milliseconds

Time-precise stimulation of several model signals

Time-precise measurement of model changes

Reliable determination of minimum and maximum values

of model variables
Python-based CAN restbus simulation

Exact replay of recorded bus communication

MicroAutoBox HIL Simulator
(for example, CAN data replay)
Parallel execution of several ECU tests independently

*.py
*.py
*.py
Realtimecapable Python interpreter Simulation Model Real-Time Scripts

for processor board and MicroAutoBox.
190
2016

Test Automation Software / Real-Time Testing
Introduction
Real-Time Testing Real-time test management via scripting and dedicated graphical user interface

Real-Time Testing library in AutomationDesk for convenient script management

Model variables can be observed and changed in every simulation step

No model modification necessary for real-time testing

100% reproducible real-time tests Executed synchronously with simulation model

Real-time tests implemented in Python 2.5 (user-extensible via libraries)

Application Fields
Several independent test scripts can be executed concurrently

Dynamic test loading during model execution and test execution

Easy integration Easy integration into user-defined test frameworks (AutomationDesk or others)

CAN support of real-time tests (based on RTI CAN MultiMessage Blockset)

Use of MAT file data located on host PC for real-time stimulation of model variables

Python objects can be easily exchanged between real-time tests and the PC Python script

NEW: Available for DS1005 PPC Board and DS1006 Processor Board, DS1007 PPC Processor Board,

SCALEXIO (for single-processor and multiprocessor systems)
Available for MicroAutoBox, and MicroLabBox

NEW: Available for MicroLabBox

Support of VEOS®, dSPACE’s platform for PC-based offline simulation

NEW: Support of multi-model scenarios in VEOS®

Software
NEW: Full support of simulation mode „as-fast-as-possible“ in VEOS

NEW: Support of CAN FD (CAN with flexible data rate)

Real-time testing with Python scripts Python tests executed synchronously to simulation model

Read and write access to model variables in every simulation steptep

Concurrent execution of several independent test scripts

No need to modify the simulation model

Order Information
Hardware
Real-Time Testing RTT

Relevant Software

Optional VEOS See p. 112
AutomationDesk Basic AUD_BASIC

AutomationDesk – Automation Server AUS_BASIC

Platform API Package PLATFORM_API

Engineering
Failure Simulation Package FAILURE_SIM

191
2016

Real-Time-Capable Python Interpreter

A real-time Python interpreter, running on the processor MicroAutoBox and executed regardless of whether another
board along with the model, allows the script to execute real-time test is already running. Even though executing
synchronously with the model. The interpreter can execute the real-time tests requires additional memory capacity and
several real-time tests simultaneously and independently of computing time, it is no problem to implement typical test
one another. The tests can interact with the simulation model scenarios. On HIL processor boards, the tests even run in
in real time via the memory on the processor board. You can parallel to complex engine and vehicle dynamics models,
therefore observe and influence the ECUs connected to the at simulation step sizes of 1 ms.
HIL simulator in each individual simulation step.
The Python interpreter is added to the application during the
translation process via a Simulink Coder (formerly Real-Time
Workshop) build option. You can formulate real-time tests
using standard Python scripts from the real-time testing
libraries (e.g., 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 simulator’s processor board or
Managing real-time tests with the Real-Time Test Manager.
Real-Time Observer
A common test case is to detect an event generated by
velocity
the real-time model. An event is specified by a condition
referencing one or more real-time model variables. As soon 80
as the event has been detected, a test action is triggered in 60
the same sample step. In this example, the real-time script 40
observes the speed of a simulated vehicle and reacts by 20
performing an emergency stop maneuver immediately when 0 t
t detect
the vehicle speed exceeds 80 km/h. This test case can be
brake_pedal
easily implemented by a real-time Python script. The condi-
tion is observed continuously within a While loop. The yield 100
75
command pauses the test execution, which resumes in the
50
next simulation step. This means the script can easily be
25
time-controlled. When the speed exceeds 80 km/h, the While
0 t
loop is left, and the brake maneuver is initiated by setting t detect
the associated model parameter in the same simulation step.
192
2016

Introduction
from rttlib import variable
velocity = variable.Variable(r‘Model Root/Velocity/Out1‘)
brake_pedal = variable.Variable(r‘Model Root/Brake/Value‘)
def MainGenerator():
Application Fields
while(velocity.Value <= 80.0):
yield None
brake_pedal.Value = 100.0
Implementing a real-time test in Python.
Software
Implementing Real-Time Stimulus
In many test scenarios, recorded data for ECU stimulation requires data to be replayed exactly 50 ms after a specific
has to be replayed with correct timing. For this, Python CAN message is received, a simple replay command in the
real-time scripts can perform precisely timed stimulus gen- Python script triggers the real-time-capable data transport
eration on predefined model variables. One example is a from the PC to the real-time hardware so that the data is
sine generator that can be implemented by means of the replayed in time. The automatic load mechanism supports
standard sine functionality of Python’s math module (see the replay of large data volumes, such as test drive log
scripting example below). files that are several hundred MB in size. Several replay
Hardware
Recorded measurement data can also be replayed via an processes can run simultaneously, and they can all be con-
intelligent load mechanism, in which the Python real-time trolled independently of one another. In a multiprocessor
script references a recorded file (MAT file) on the PC's hard system, it is even possible to stimulate on several subnodes
disk. The script links data vectors in the file to the target time-synchronously.
parameters in the model. For example, if the real-time test
Engineering
Example of a real-time script that triggers a sine generation.
193
2016

Implementing CAN Restbus Simulation

To program CAN restbus simulation, Real-Time Testing is An example test scenario (see picture below) is the moni-
conveniently integrated with the RTI CAN MultiMessage toring of an analog input signal. When a defined trigger
Blockset. The blockset contains an option for preparing CAN threshold (e.g., 14.7 V) is exceeded, a predefined CAN mes-
access for Real-Time Testing, so real-time scripts are able to sage is sent cyclically every 50 ms until the value goes below
send and receive CAN messages with freely definable CAN the threshold again. Another application example is taking
IDs and contents. This makes it very easy to test case-specific CAN communication that was recorded during a test drive
restbus simulation. These dynamic restbus parts (like ECU- and replaying it in the laboratory with correct timing.
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.
Input_Voltage [V]
20
15 14.7 V
10
5
50 ms 50 ms
0 t
CAN-Msg #1 CAN-Msg #2 CAN-Msg #3 A real-time script continuously evaluates a model variable

t = 500 ms t = 550 ms t =600 ms
and reacts by sending cyclic CAN TX messages.
1. Import real-time testing libraries (RTI 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.
194
2016

Introduction
Implementing Real-Time Tests for Multiprocessor
Systems
Today, HIL integration tests are executed on multiprocessor by the Python test scripts during model run time, instead
(MP) systems where submodels for the engine, transmission, of being created statically in advance by the modeler. Local
restbus simulation, etc., are distributed across several proces- and remote variables can both be accessed during testing:
sor boards to ensure real-time capability. Real-Time Testing Specifying the unique MP variable path is enough. This en-
provides transparent variable access in the MP system so that sures that the real-time tests can be executed on different
Application Fields
real-time scripts can be implemented independently of the MP nodes without modifications. They are implemented
structure of the HIL model. The communication channels once and run everywhere.
needed between the processor boards are set up dynamically
Real-Time Test Library in AutomationDesk

AutomationDesk includes a block library for convenient
handling of real-time test sequences. The library lets you
Software
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 Real-
Time Testing into your existing graphical test environment.
Hardware
Real-Time Testing library in AutomationDesk.
Engineering
195
2016

Test Automation Software / Platform API Package

Application programming interfaces for connecting to dSPACE platforms
Highlights
Package containing automation libraries for accessing
dSPACE systems
High-level libraries for convenient platform manage-

ment and simulation model access
Access to dSPACE real-time platforms and dSPACE

VEOS®
Support of Python or any .NET-compliant language

NEW: Support of ASAM XIL API standard

Key Benefits
The Platform API Package is a set of libraries to access
Create your own test scripts and test automation applica-

dSPACE real-time platforms and dSPACE VEOS. It provides tions to access parameters and signals in your simulation
a convenient way to download, start and stop models Automation interface to MATLAB, e.g., for data processing
and also grants high-level access to the model variables
for reading, writing, stimulating, capturing, etc.
NEW: XIL API support in .NET Platform Management API

Programming interface that complies with the new Programming interface for downloading, starting and
ASAM XIL API standard for accessing the simulation stopping a model running on a dSPACE real-time platform
model or dSPACE VEOS
MAPort support including read, write, and capture access
plus stimulus support for most dSPACE platforms
Port management: e.g., for loading applications and
setting the simulation state
MATLABLIB2
Remote-control MATLAB to use its powerful mathematical

function: e.g., for signal processing
Automation of 32 and 64-bit MATLAB versions

196
2016

Test Automation Software / Platform API Package
Introduction
Order Information


Application Fields
Relevant Software

Optional AutomationDesk Basic
AUD_BASIC

AutomationDesk – Automation Server
AUS_BASIC

PLATFORM_API

Failure Simulation API Package
FAILURE_SIM

Real-Time Testing
RTT

Software
Hardware
Engineering
197
2016

Test Automation Software / Failure Simulation Package
NEW: Failure Simulation Package

Application programming interfaces for accessing dSPACE Failure Insertion Units
Highlights
Automation libraries for accessing dSPACE Failure

Insertion Units
High-level libraries for convenient failure simulation access
Support of Python, C# and any other .NET-compliant language
ASAM XIL EESPort-compliant access via graphical user

interface in ControlDesk Next Generation or via .NET-
based programming interface
Successor of the Failure Simulation API Package and the
ControlDesk® Next Generation Failure Simulation Package
Key Benefits
The Failure Simulation Package is the state-of-the-art access face is available in ControlDesk Next Generation when
to ASAM XIL-compliant failure simulation units. It provides both products are installed. The package can be used to
API access according to the ASAM XIL Electrical Error Simula- access dSPACE or third-party FIU systems that offer an
tion port (EESPort) and grants uniform access to all dSPACE ASAM XIL-compliant automation interface.
failure simulation systems. In AutomationDesk, the access to Failure Insertion Units
For users of dSPACE ControlDesk Next Generation, the is supported by an extension of the XIL API Convenience
Failure Simulation Package enables an ASAM XIL API Library. Convenient and easy-to-use-blocks support you in
EESPort-compliant interface component. The user inter- defining single-pin and multi-pin failures.
ASAM XIL-Compliant
With the introduction of the Failure Simulation Package,
the improvements brought by the new ASAM XIL standard
will be included in dSPACE products.
The Failure Simulation Package user interface in

198
2016

Introduction
Module Overview
Failure Simulation Package
XIL API EESPort .NET XIL API EESPort XIL API EESPort
GUI in ControlDesk Next Generation AutomationDesk
Application Fields
.NET
Clients Python
C#
Server XIL API EESPort

(Access to ASAM XIL-compliant FIU hardware
Software
Hardware dSPACE dSPACE
SCALEXIO
(dSPACE Simulator Full-Size Simulator Mid-Size
Failure
Insertion
Units)
Hardware
XIL API EESPort in .NET
Programming interface for accessing Failure Insertion Units
Uniform support of all dSPACE Failure Insertion Units

Automated configuration and switching of XIL API

error configurations
Engineering
199
2016

XIL API EESPort GUI in ControlDesk Next Generation

Successor to ControlDesk’s Failure Simulation Module The XIL API EESPort (Electrical Error Simulation port) GUI not
Interactive graphical configuration of error configura- only provides for a convenient control of electrical failure
tions and error sets compliant to ASAM AE XIL API insertion hardware, it also allows for an interactive graphical
standard (EESPort) configuration of error sets and error configurations directly
Requires ControlDesk Next Generation from ControlDesk, which acts as a XIL API EESPort client.
Through compliance with the ASAM XIL API standard, this
solution offers uniform support for all dSPACE SCALEXIO
and PHS Failure Insertion Units (FIU).
Definition of various Error Sets with the XIL API EESPort GUI, visible in ControlDesk Next Generation
200
2016

Introduction
AutomationDesk Client
Convenient and easy-to-use AutomationDesk library
blocks for FIU automation
Uniform function blocks for any FIU that complies with
the ASAM XIL standard
Application Fields
Software
XIL API EESPort server
Uniform access to all dSPACE Failure Insertion Units
Hardware
Order Information

Failure Simulation Package FAILURE_SIM

Relevant Software
Engineering
Optional AutomationDesk AUD_BASIC

ControlDesk Next Generation See p. 120

201
2016

Production Code Generation Software / TargetLink
TargetLink®
Automatic production code generator
Highlights
 High-quality production code generation directly
from Simulink®/Stateflow®
 Powerful software design and testing features
 High-performance, native AUTOSAR support
 Certified for IEC 61508 and ISO 26262
 Numerous third-party tools for highly efficient model-
based development

Model-based design has become the established devel- Converting graphical models directly into production code
opment method across many industries, and production ensures perfect consistency between model and code. With
code generation is the logical step for turning models deterministic code generation by TargetLink, the same model
into efficient, production-ready code. TargetLink gener- always results in the same proven code to guarantee the
ates production code (C code) straight from the MATLAB®/ highest software quality. Every step can be tested against the
Simulink/Stateflow graphical development environment. specification via the built-in simulation features. This allows
The C code generation options range from plain ANSI C early verification and translates directly into cost savings,
code to optimized fixed- or floating-point code for AUTO- for example, by avoiding expensive ECU software errors.
SAR platforms. Versatile code configuration options ensure
that the production code copes with processor constraints.
Efficient Coding Seamless Tool Chain

Efficiency is the key to production-quality code. Efficient code TargetLink seamlessly connects function development
requires a minimum of execution time and resources to run and code generation for the control unit or prototyping
on a cost-efficient embedded processor. Code generated by hardware. It also automatically closes the gap between
TargetLink is proven to be as efficient as handwritten code. the design and verification phases. The result: transparent,
Other factors also make TargetLink such a useful tool: code well-defined development processes for conventional and
readability, traceable model/code dependency, and last but AUTOSAR ECUs. Calibration files, AUTOSAR software com-
not least, the ability to configure the code generation to ponent descriptions, and comprehensive documentation are
produce exactly the kind of code that is required. generated in addition to the production code.
202
2016

Introduction
Code efficiency Efficient fixed-point or floating-point production code
Your specifications – models and diagrams –

directly from MATLAB/Simulink/Stateflow are directly translated into efficient C code
Code reliability Consistent, deterministic translations of models into
Errors such as typing mistakes, oversights,

Application Fields
stress-tested C code misunderstandings are avoided
Human readability Concise, yet readable code
Code reviews are easy to perform

Automatic scaling Intelligent scaling based on worst-case propagation of
Shortens the time-consuming and error-prone scaling

signal ranges and simulation-based scaling process
Test mechanisms Various test levels to test the production code against
Malfunctions are found at earliest stage

the specification (MIL, SIL, PIL)
Code coverage analyses Dynamic analyses of program execution to find areas
Untested code and untested model parts are detected

that have not been run through
Incremental code generation Modular code generation, i.e., for specific subsystems
Faster code generation, preserving approved code

Model referencing support Developing models on a modular/component basis
Distributed development by large teams is much easier,

and large models can be handled more efficiently.
Multirate code Full support of multirate systems with intertask You can already define tasks at block level
Software

communication
TargetLink Data Dictionary Central container to handle variables, data structures,
You can manage complex data to plan and structure

scaling formulas, tasks, functions your projects
Code generation straight from the Generation of code files and A2L files for Data
Simplified software integration and integration testing

Data Dictionary Dictionary variables independently of their use in for code from multiple TargetLink models/subsystems
TargetLink models and legacy variables
TargetLink Blockset The free TargetLink Blockset Stand-Alone can be used
Large workgroups can work with TargetLink models

without having the Base Suite installed without the need for additional TargetLink licenses
Compliance with standards Compliance with relevant standards such as ASAM-
Quality and interoperability guaranteed

MCD 2MC (ASAP2), AUTOSAR, MISRA, and OSEK
Hardware
AUTOSAR support Support for modeling and code generation for
TargetLink bridges the gap between model-based

AUTOSAR software components (SWC), and generation design and AUTOSAR-compliant software development
of SWC descriptions
Support of OSEK/VDX-compliant Support for the standardized OSEK/VDX interface and
You can design multirate software that is compliant

operating systems features with OSEK operating systems
Calibration data generation Calibration data exported as ASAM-MCD 2MC (ASAP2)
Automated and complete process with perfect

file for calibration tools consistency between model and calibration data
Documentation Automatic model and code documentation
Your projects are transparent and trackable

AUTOSAR software component Exchanging AUTOSAR SWC containers between
Safe and convenient round trips for AUTOSAR software

(SWC) container exchange TargetLink and SystemDesk® (p. 40) development
Engineering
Access to SystemDesk simulation for proper software

integration testing
Modular development Innovative interface concept for ports, measurement
Easily increase software reuse across different projects

signals and calibration parameters
Connection to dSPACE VEOS® Export virtual ECUs from TargetLink and run them in
Easy testing and experimentation with TargetLink code

VEOS (p. 112) in combination with other virtual ECUs
and standard dSPACE tools like ControlDesk® Next
Generation (p. 120).
FMI support Export of Functional Mock-up Units (FMUs) from
Execution of TargetLink-generated code with offline and

TargetLink models based on the Functional Mock-up real-time simulators from third parties and dSPACE
Interface (FMI) standard
203
2016

Order Information
Classification Type Order Number

TargetLink Base Suite1) Base Suite TBS

Target Optimization Modules Infineon C16x Tasking TOM_C16x/Tasking

for certain processors/compilers Infineon TriCore Tasking TOM_TriCore/Tasking

(further details see p. 223, p. 224)
Renesas SH-2/Renesas TOM_SH2/SHC

Other modules Target Simulation Module (for all supported processors) TSM

TargetLink Module for Operating Systems – OSEK TMOS_OSEK

TargetLink AUTOSAR Module TAS

TargetLink Data Dictionary Manager (included with DSDD_MANAGER

TargetLink Base Suite)
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 Stand-alone blockset for free model exchange TargetLink Blockset Stand-Alone

Data dictionary TargetLink Data Dictionary

Required Integrated development environment MathWorks MATLAB®/Simulink®/Stateflow®

Compiler for host simulation included in MATLAB

Operating system www.dspace.com/go/os_compatibility

Optional Compilers for processor-in-the-loop tests Target-specific compiler for processor-in-the-loop tests

with Target Simulation Module
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 utili-
ties, TargetLink Known Problem Reports, etc. The address is
www.dspace.com/tlpsc
204
2016

Introduction
NEW: TargetLink 4.1
Feature Area Improvement

Modeling in Simulink/Stateflow Multiple
instantiation of referenced models, including support for model parameters, e.g., to use
instance-specific parameter sets
Support of Simulink’s simplified initialization mode and improved support for the classic initialization

mode
Application Fields
Support of initial condition (IC) structures for simplified initialization for Simulink buses

Simulink Signal Conversion block with TargetLink extensions, e.g., to specify structured variables

Bus Assignment block for simplified modeling with buses, e.g., reading and writing from/to individual

bus signals
Buses at the Simulink/Stateflow interface and structured Stateflow variables

Support of structures in the Stateflow action language for simplified modeling and access to structured

signals
Update and check capability of the subsystem frame generation in TargetLink to synchronize TargetLink

ports in subsystems based on Data Dictionary signature objects
AUTOSAR Support of AUTOSAR 4.2.1, including ARXML import/export, AUTOSAR-compliant code generation, etc.

Activation of Runtime Environment (RTE) events that let runnables detect the reasons for their activation

Support of port-defined argument values for more efficient server modeling

Software
Support of AUTOSAR NvData (nonvolatile data) interfaces in combination with require ports, provide

ports and combined provide-require ports as well as efficient mechanisms for writing to NVRAM
Support of AUTOSAR transformers in combination with sender-receiver communication for end-to-end

communication protection and SOME/IP (Ethernet)
Code generation core capability Incremental code generation for reused systems (either for incrementally generated subsystems or model

referencing)
More efficient code for function reuse via signal inheritance from predecessor/successor blocks of reused

systems
MISRA C compliance improvements, particularly for MISRA-C 2004 rule 10.1, MISRA-C 2004 rule 12.9,

MISRA-C 2004 rule 14.3
Code efficiency improvements, including:

Hardware
Dimension downgrade for vector/matrix auxiliary variables

Improved moving into conditionally executed branches

Improved copy propagation

Generation of default keyword: “void” instead of “Void”

Consolidated Data Dictionary XML import to increase robustness against XML files with minor defects

and support for XML file import from older TargetLink versions
Data Dictionary and data management Extension of the Data Dictionary’s embedded help to provide instant information on objects and properties

improvements Data Dictionary views for standard TargetLink users in AUTOSAR and non-AUTOSAR use cases to hide

irrelevant Data Dictionary objects and properties
Improved comparison of Data Dictionaries in the DD Comparison pane via filter rule sets

Improved Data Dictionary Message Browser for a clear indication of warnings and errors

Engineering
Referencing code generation option sets from the TargetLink Main dialog in the Data Dictionary to use

them in various models at the same time
Miscellaneous Export of Functional Mock-up Units (FMI standard) from TargetLink to execute TargetLink code in third-

party environments
Storing requirement information in the Data Dictionary to use at model elements and include in the

production code as code comments
Separate specification of compilers for production code or MEX compilers

Block context menus to transfer incrementally generated subsystems into referenced models and vice versa

Improved MIL simulation speed for scaling-invariant systems and models with many workspace parameters

New TargetLink demo models for:

Code with variable vector sizes (vector width)

Generating reusable code by means of direct and indirect function reuse

Multiple instantiation of referenced models

AUTOSAR NVData interfaces and AUTOSAR transformers

Data Dictionary views and Data Dictionary API

205
2016

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 TargetLink TargetLink Data Document Autoscaling ASAM-MCD 2MC
TargetLink coder Blockset
1)
Dictionary
2)
Generator file generation
Base Suite
TargetLink Base Suite License
Freescale Infineon Infineon Renesas STMicroelectronics

Target Simulation MPC55xx C16x XC2000 SH-2 ARM Cortex M3
Module
3)
Freescale Freescale Infineon Renesas Renesas
MC56F83xx S12X TriCore RH850 V850
Target Optimization Infineon Infineon Renesas

Modules C16x TriCore SH-2
Automotive-
Specific OSEK /VDX module AUTOSAR module
Modules
1)
Usable in stand-alone mode without license.
2)
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/go/tlpil
TargetLink Base Suite Target Simulation Module (optional)

Highly efficient ANSI C code generation from Simulink/ Test your generated code on the target microcon-
Stateflow troller (for supported processors and evaluation boards
For all microcontrollers with ANSI C compiler see p. 207)
Fixed-point code, floating-point code or a mixture of both
TargetLink Data Dictionary (p. 231) TargetLink AUTOSAR Module (optional)
TargetLink Blockset (p. 211) Support for the development of AUTOSAR software
Autoscaling (p. 219) components (SWC) (p. 227)
Code coverage analysis (p. 220)
Modular development and code generation (p. 221)
TargetLink Module for Operating Systems (optional) Target Optimization Modules (optional)
Support of OSEK/VDX-compliant operating systems For target-specific, optimized code generation
Uses compiler-specific language extensions and assembly
macros
206
2016

Introduction
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.
Application Fields
Compiler Supported by Target Evaluation Boards
Processor Family
Simulation Module Supported by TargetLink
Freescale MC56F83xx Freescale CodeWarrior compilers Freescale MC56F8367EVM
Freescale MPC55xx Green Hills, Freescale CodeWarrior, GNU Axiom MPC5554DEMO,
and Wind River compilers Freescale MPC5561EVB,
Freescale MPC5604BEVB and
Freescale MPC5748GEVB
Freescale S12X Cosmic and Freescale CodeWarrior Freescale EVB9S12XEP100
compilers
Infineon C16x Tasking compilers i+ME eCAN C167 CR
Infineon TriCore Tasking and GNU1) compilers Infineon TriBoard TC1766,
Software
Infineon TriBoard TC1767,
Infineon TriBoard TC1796 and
Infineon TriBoard TC275
Infineon XC2000 Tasking compilers Infineon SK-EB XC2287
Renesas RH850 Green Hills compilers Renesas YRH850F1L
Renesas SH-2 Renesas compilers Renesas SDK7058 and
SDK72513
Renesas V850 Green Hills compilers Renesas AB_050_
Fx4_70F4012
STMicroelectronics ARM Keil compilers Emerge-Engineering MEDKit
Hardware
Cortex M3 on ARM
Only for TC275.
1)
Some of the evaluation boards need to be modified (loader, For more information on software compatibility with
external RAM, etc.). Please order them through dSPACE to target compilers and evaluation boards, please refer to:
ensure a correct board setup. www.dspace.com/go/tlpil
Engineering
TargetLink Engineering Services
Our engineering portfolio includes special TargetLink Model analysis and advice

customer services, for example: Support for developing and integrating AUTOSAR-

Hands-on support during introduction of TargetLink compliant software components
Support during evaluations and pilot projects Support for integrating the generated code in the ECU’s

Customer-specific TargetLink training software environment

Integrating TargetLink into your development Tool chain development and maintenance

processes Process consulting

207
2016

How Do I Work with TargetLink?

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

Model Exchange via
Code Specification
Reference
TargetLink Blockset
Analyzing Simulation Behavior and Optimizing Production Code
Typical Task Simulink

 Behavior Validity Checks
 Code Generation Settings Model Exchange
 Scaling1) in Workgroups
MIL
Achieving Production Quality
Model-in-the-Loop Validation / Verification
Production Code
Host Simulation
Precision
Typical Task Host-PC

 Scaling/Discretization Analysis1)
 Saturation and Overflow Detection 1)
 Code Coverage Analysis SIL

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

for OSEK RTOS Written Code Code
Operating Systems Code
ECU
1)
valid only for fixed point software
208
2016

Introduction
Workflow
Control Design and Function Prototyping Using the TargetLink Block Library
Control design starts with creating a control model in the To implement the control algorithms in C code, you need the
integrated design environment MATLAB/Simulink/Stateflow. TargetLink block library. TargetLink blocks contain additional
Before production code generation with TargetLink, you data for code generation, such as the scaling information
can use dSPACE prototyping systems to carry out conve- for fixed-point variables, variable classes, variable names,
nient function prototyping and validation of your new ECU etc. A utility automatically replaces your Simulink controller
Application Fields
control algorithms. 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 Software

Hardware
Engineering
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.
209
2016

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. 218) 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 Verification on Target Processor via

Software-in-the-Loop Simulation Processor-in-the-Loop Simulation
By means of software-in-the-loop simulation on a host PC, Using the optional Target Simulation Module (p. 207),
you can compare the behavior of the generated code with you can execute processor-in-the-loop simulation to verify
the reference data obtained in model-in-the-loop simulation. the generated code on an evaluation board equipped with
TargetLink offers a graphical user interface, where you can the same target processor as your final ECU. Successful verifi-
select the signal histories of blocks for detailed analysis. cation of processor-in-the-loop simulation with model-in-the-
loop 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.
210
2016

Introduction
TargetLink Block Library for Implementation
Extended Block Functionality
Implementation-Specific Information
The Simulink® block library is very powerful in simulation
tasks, providing all necessary specification features. When
it comes to code generation, however, more information
Application Fields
is needed for each block. The blocks need additional ca-
pabilities for fixed-point simulation. That is why there is a
TargetLink block for each supported Simulink block. The
TargetLink blocks significantly enhance the functionality
of the supported Simulink blocks and have an extended
dialog that allows you to enter the implementation-specific
information necessary for code generation.
Each block also provides a means of data logging and over-
flow detection. A special routine automatically prepares
Simulink models for code generation with TargetLink by TargetLink block dialog for entering implementationspecific
Software
enhancing the Simulink blocks to TargetLink blocks. information like the data type, variable name, scaling data, etc.
TargetLink Blockset StandAlone

Function Development with TargetLink Blocks
Hardware
The TargetLink Blockset Stand-Alone is a license-free version Its features include:
of the TargetLink blockset which allows function developers Free TargetLink model exchange in workgroups
to design their controller models directly with TargetLink. It Controller design and simulation in Simulink
can be used on any computer that has MATLAB/Simulink Prototyping with MathWorks® Simulink Coder™
installed. With the TargetLink Blockset Stand-Alone,
TargetLink models can be exchanged freely without the
need for extra TargetLink licenses.
Engineering
Linking Control Design, Prototyping, and
Implementation
You can use the free TargetLink Blockset Stand-Alone able in that case, the TargetLink Blockset Stand-Alone allows
to design and prototype your controller without a full you to use the same models for rapid control prototyping
TargetLink installation. The TargetLink blocks can be used for and production code generation. Development iterations
rapid control prototyping on dSPACE hardware. Although are thus easier to perform and less prone to error.
the added functionality of the TargetLink blocks is not avail-
211
2016

Function Development Software Development

1 1
in
= in
same model
pictrl plant model pictrl plant model
Simulink Coder™ TargetLink
MicroAutoBox Real-time hardware 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.
212
2016

Introduction
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 genera-
Application Fields
tion options to translate the modelings into efficient, read-
able 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.
TargetLink directly supports

these Simulink blocks.
Software
TargetLink Utility Blocks
Hardware
TargetLink utility blocks provide access to specific features
of TargetLink or further specify the code generation process
for the model.
Multirate Blocks
The TargetLink multirate blocks make multirate operating
system objects available in block diagrams. There are even
Engineering
OSEK-specific blocks like the CounterAlarm.
AUTOSAR Blocks
Model-based design for AUTOSAR ECUs (p. 227) is suppor-
ted by blocks for structural elements such as runnables,
ports, and certain communication elements.
213
2016

Block Configurations
Handling Large Models with the Property
Manager
If you need to change the properties of a large
model, TargetLink’s 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 simulta-
neously. For Stateflow objects this includes charts,
events, states and data. The Property Manager
provides a tree view of the model’s subsystem The Property Manager for handling models with numerous blocks.
hierarchy, a list of blocks in each subsystem, and
a configurable list of properties for each block.
Three Simulation Modes for Testing

Confirmation by Simulation
Comparing Simulation Results Test Against Specification
Although code generators produce virtually flawless results Verification means checking the implementation against the
when compared to manual programming, the generated specification. The specification is the simulation model, as
code still needs to be tested as well as the underlying spe- executed by Simulink and Stateflow. The executable and
cification. TargetLink provides powerful and easy-to-use approved specification is used as a reference. The implemen-
means to verify the generated code. The code tests are tation is the generated and compiled C code, as executed by
performed in the same simulation environment that was the target processor. TargetLink provides a 3-step verification
used to specify the underlying simulation model. Functional process which shows at a click whether the specification and
identity has been achieved when simulation results match. implementation are functionally identical. On the basis of
The comprehensiveness of tests can be assessed using code a controller model, TargetLink performs simulations of the
coverage analysis. model, the generated code on the host, and the generated
code on the target, without additional model modifications
or preparations.
214
2016

Introduction
ThreeStep Verification Process
Model-in-the-Loop Simulation
The first step is to record data for reference plots from the sim- plots act as the reference for the next verification steps.
ulation model. Signals from selected blocks and state variables Model-in-the-loop simulation also serves other purposes.
are automatically logged by TargetLink. The model-in-the-loop It is used for detecting overflows of integer variables, and
simulation captures the specified behavior of the model that its results are used for simulation-based autoscaling.
is to be implemented in C code later on. The recorded signal
Application Fields
Model-in-the-Loop Software-in-the-Loop Processor-in-the-Loop
Controller model C code on host PC C code on target processor
Evaluation
board
Software
Plant model or stimulus signals Plant model or stimulus signals Plant model or stimulus signals
TargetLink performs the three different simulation modes without any changes to the model or the generated code.
Hardware
Software-in-the-Loop Simulation
Software-in-the-loop means the code is generated and the host PC instead.The signal plots should be largely iden-
replaces the controller blocks in the simulation model (for tical when compared to the results of model-in-the-loop
example, the same plant and stimulus signals). TargetLink simulation. If they are not, they can be analyzed to get a
does this automatically in the background. You still set the better understanding of the cause of the deviation and to
controller blocks, though it is the code that is executed on fine-tune the fixed-point settings.
Engineering
Processor-in-the-Loop Simulation
Finally, the generated code runs on an embedded proces- piler and downloaded to the evaluation board. TargetLink
sor. Code that runs correctly on the host PC can still cause manages the communication between the host PC and the
trouble on the target processor. To check that this does not evaluation board. All these activities are automated and need
happen, TargetLink offers processor-in-the-loop simulation. no user interaction. Simulation on an evaluation board just
An off-the-shelf evaluation board is connected to the host takes two mouse clicks.
PC, and the generated code is compiled with the target com-
215
2016

Features and Benefits of the Simulation Concept

MIL/SIL/PIL simulation at a click Switching from MIL to SIL or PIL simulation requires just a Powerful simulation environment

click No need for separate test models, generation of

Sfunctions or manual insertions into test harness
models
Integrated data logging Builtin data logging and result plotting for all simulation No model modifications necessary

modes Available for all simulation modes

Direct comparison of MIL/SIL/PIL Automatical plotting of all simulation results in the same Display results of simulations in different modes directly

results plot window and analyze deviations
Direct feedback whether code matches model

simulation
Detailed signal analysis and Zoom signals to visually inspect deviations, display Get clear picture of signal behavior

deviation plots constraints (e.g., defined ranges), use cursor to scroll Especially useful for conversion from floatingpoint to

through signal histories, display signal values numerically fixedpoint
or plot signal deviation
The TargetLink block dialog lets you specify whether to log

signal histories – regardless of the simulation mode.
In Brief
Easy to use, intuitive, fast and frequent tests increase
the software quality
Unmatched simulation flexibility
216
2016

Introduction
Run-Time Analysis
Profiling the Code
Processor-in-the-loop simulation can also be used to profile and ROM usage for each function. These features allow you
the generated code. During simulation, TargetLink auto- to evaluate design alternatives, such as selecting different
matically measures execution time and stack consumption search routines of a look-up table block. You can immedia-
directly on the target processor. A code summary lists RAM tely measure the impact of the change on code efficiency.
Sound implementation decisions based on accurate bench-
Application Fields
marks become a matter of a few clicks.
Software
The results of code profiling: execution time measurement, stack
size measurement, and code summary of generated code.
Hardware
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.
Engineering
217
2016

Scaling Variables
Fixed-Point Accuracy
Quick and Accurate Scaling Overflow Detection
If TargetLink is to generate only floating-point code, scaling is Another big advantage: fixed-point overflows no longer
not necessary. However, when fixed-point code is generated, entail hours-long debugging sessions. With TargetLink, sca-
autoscaling can be a huge time-saver. It takes away the te- ling can be checked during simulation. If an overflow occurs,
dious and error-prone task of manually scaling each variable TargetLink shows the exact location in the block diagram.
and each operation in the software. What took days and The problem can be corrected right away.
weeks in the past can now be done in minutes and hours.
Plot overview window indicating an overflow of an outport block.
Scaling Choices
Scaling Properties Automatic Scaling
TargetLink offers a two-coefficient linear scaling method, which These scaling properties give ample choices to fine-tune
is widely used in embedded control applications. The properties fixed-point code to the conflicting requirements of low
for specifying fixed-point scalings in TargetLink are: execution time, high computational precision, and overflow
Data type avoidance. Fixed-point scaling can be done manually by a
Power-of-two scaling factor or arbitrary scaling factor software engineer, but in most instances it is left to the
Offset value autoscaling tools from TargetLink.
Constraint values
Bit safety margins
Saturation options
218
2016

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

Using scaling formulas is not actually an autoscaling the TargetLink Data Dictionary, you can select them in block
method, but it is a way of scaling a model quickly. After defi- dialogs or in the Property Manager to quickly scale signals of
ning a complete set of scaling properties under one name in one kind or subsystems with the same scaling parameters.
219
2016

Code Coverage Analysis

Run-Time Analyses
TargetLink offers C0 and C1 coverage analysis, also Code branches that have never been executed are easily
called ‘statement coverage’ and ‘decision coverage’. identified, and test strategies can be adjusted accordingly.
During simulation on host or target systems, counters record Thus, coverage analysis increases software quality.
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.
Code Coverage Total Branches Reached Branches Unreached Branches

Fuel system 61.87% 139 86 53
Fuel rate controller 58.91% 129 76 53
Fuel rate calculator 56.56% 122 69 53
Correction redundancy 100% 7 7 0
Airflow controller 100% 10 10 0
Airflow calculation 100% 9 9 0
Airflow subsystem 100% 1 1 0
Example of the information provided by code coverage.
Annotated code listing with execution count for each code block.
220
2016

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

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

for referenced models. 221
2016

Simplified Software Integration

TargetLink code from separate (incrementally generated) Dictionary. Variables with global relevance that are shared
subsystems and (referenced) models can be easily integrated by separate models and subsystems are specified and gener-
and tested by means of code generation from the Data ated from the Data Dictionary.
Code Generation Straight from the TargetLink

Data Dictionary
The Data Dictionary supports the generation of both code code files with definitions and declarations, and also A2L
and A2L files for Data Dictionary variables independently files for variables from the Data Dictionary, makes software
of their use in TargetLink models. Variables with global integration and software integration testing easy. Moreover,
relevance that are shared between different models, sub- all the calibration parameters for an entire ECU project can
systems and referenced models should be specified in the be created in one file, no matter whether they are from
Data Dictionary and implemented from there. Generating legacy code or used in TargetLink models.
Diff&Merge mechanisms via TargetLink

Data Dictionary
TargetLink Data Dictionary has the mechanisms needed to their effects on it. Diff&merge mechanisms let you update
compare different versions and display changes, e.g. old/new. interface definitions simultaneously to ensure consistency
You can then trace modifications back to the model to analyze when changes are made – making your work much easier.
222
2016

Introduction
Code Optimization
Highly efficient production code
Optimized ANSI C Code Standard Optimizations
TargetLink generates highly efficient ANSI C code. This is TargetLink uses many of the optimization techniques that are
achieved by various optimization techniques, which roughly also used by C compilers: constant folding, algebraic trans-
fall into 3 categories: formations, dead code elimination, and lifespan analysis of
Application Fields
Standard optimizations variables, to name just a few. They are standard optimization
Interblock optimization techniques and are used by TargetLink whenever applicable.
Code pattern libraries
Interblock Optimization
Interblock optimization combines the code of several blocks for calculating the inputs of a switch block is moved inside
in one C code line. TargetLink’s interblock optimization gives the If-Else instruction.
Software
the generated code a human touch, because it combines The example shows interblock optimization at work. This
code in a very similar way to what a skilled software engineer technique saves execution time and ROM size, but most
would do. For instance, a string of arithmetical, logical, and importantly, it reduces stack size significantly and enhances
relational blocks is usually combined in one expression. Code code readability considerably.
Hardware
Engineering
Example of interblock optimization.
Code Pattern Libraries

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

TargetOptimized Code
Optimized Assembly Code
With the optional target optimization modules (p. 223), specific instructions and even inline assembly macros are
processor- and compiler-specific language extensions can used to deliver top-notch code performance. Some features
also be used for code optimizations. This further increases of a processor core can be used only by applying these
the efficiency of the generated code. There is a library con- coding techniques. This sometimes makes the difference in
taining highly optimized code patterns for every processor/ meeting hard real-time requirements and ROM size limits.
compiler combination supported by TargetLink. Compiler-
ANSI-C Optimized Assembly Code

Cycles 1232 45
Code size 100 byte 54 byte
64tap FIR filter, measured with Infineon TriCore/Tasking Compiler:

Optimized code is 27 times faster than ANSIC.
Customized Code
Code According to Customer Standards
Readability Variable Classes
TargetLink code is easily readable and has many comments. You also have full control of how TargetLink generates vari-
Unnecessary macros, function calls, cryptic naming, etc. are ables and and therefore of how the RAM and processor stack
avoided. Comprehensive configuration options give you full are utilized. You can specify the scope and storage class
control over variable, function, and file naming, as well as of a variable, as well as other C attributes like ‘volatile’ or
the flexibility to partition the code into functions and files ‘const’. Even PRAGMA directives can be generated before
to keep the structure logical and manageable. 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.
224
2016

Introduction
External Code Integration Code Output Formatting
TargetLink offers a wide variety of specification options on TargetLink can generate code in a format that exactly matches
the block diagram level for easy interfacing with external company-specific C code templates. Code output can be
code such as device drivers, or with any other routine writ- formatted via an XML configuration file and an XSL style
Application Fields
ten in C or assembler. sheet. You can define the format of file and function head-
These are: ers, the format of code comments, and the inclusion of
Including external header files specific header files. Comments can even contain Unicode,
Using external global variables for example, for Japanese characters.
Using externally defined macros
Calling imported functions
Calling access functions or macros
Defining a Custom Code block containing handwritten
C code
Software
Documentation Generated Automatically
Consistent Documentation and Model
TargetLink not only generates code, it also documents more. Screenshots of models, subsystems, and simulation
Hardware
what it does – keeping perfect consistency with the model plots can also be included. Links to the generated C code
and the code. An automatically generated document pro- are provided. You can specify the documentation you require,
vides information about function interfaces and global for example, the level of detail. Documentation can be
variables, and a list of all measurable and adjustable varia- generated in the HTML, RTF (for word processing) and PDF
bles, scaling parameters, code generator options and much formats.
Engineering
Production code documentation in HTML.
225
2016

Automation and Process Integration

Full Access to TargetLink
Comprehensive TargetLink API
TargetLink is easy to integrate into existing development mated, while at the same time providing options for inter-
environments, because it comes with a comprehensive and vention in the individual process phases. For example, ‘hook
fully documented API. This grants full access to all TargetLink functions’ allow user tasks to be performed at all stages of
properties and settings and allows processes to be auto- the build process.
Calibration File Generation

ASAM MCD-2 MC File Format
Another important requirement for a code generator is close Since the C code and the ASAM MCD-2 MC file are gener-
links with calibration systems. ECU code must be prepared ated with the same data basis, they are always consistent.
for parameter fine-tuning by making calibratable or measur- This eliminates another error source, and streamlines the
able variables accessible to a calibration system. TargetLink development process.
supports the generation of the standardized ASAM MCD-2 TargetLink offers several predefined variable classes for
MC file format (formerly ASAP2) via the Data Dictionary to calibratable and measurable variables. You can also specify
make the variables and parameters available for ECU cali- your own classes, ensuring that each class holds suitable
bration. All major calibration tools support this standard. attributes for calibration and/or measurement.
TargetLink
TargetLink External
ASAM MCD-2 MC file ASAM MCD-2 MC files
/beginn MODULE
/begin CHARACTERISTIC
...
/begin MESUREMENT
...
/begin RECORD_LAYOUT
controller(vod) ...
{ Code files
...
}
*.a2l *.a2l
*.C
Calibration /include module

System
ECU ASAM MCD-2 MC Project File
226
2016

Introduction
Model-Based Design for AUTOSAR Software Components
The TargetLink AUTOSAR Module
The optional TargetLink AUTOSAR Module makes TargetLink’s as runnables, ports, and communication interfaces, simply
modeling, simulation and code generation features available at model level. Hence model-based designs are directly
for designing AUTOSAR software components (SWCs). implemented in the form of AUTOSAR-compliant produc-
Developers can specify AUTOSAR structure elements, such tion code.
Application Fields
Functionality Benefits
Model-based design for AUTOSAR software components Efficient and easy modeling using proven workflows
(SWCs) for AUTOSAR
Code generation for AUTOSAR SWCs AUTOSAR-compliant code generation
Importing, exporting and merging software component Easy migration of existing TargetLink models to
descriptions AUTOSAR
Simulating and testing SWCs Testing and verifying SWCs in early design phases
Software
AUTOSAR frame model generation No tedious manual creation of software component
Round trips with other AUTOSAR tools based on description files
SWC description files Easy integration of TargetLink in an AUTOSAR tool chain
Convenient round trips with SystemDesk based on (p. 230)
SWC container exchange In brief: You go from model to AUTOSAR-compliant code
faster.
Hardware
TargetLink AUTOSAR Block Library
To design AUTOSAR SWCs, TargetLink offers the TargetLink
AUTOSAR library:
AUTOSAR runnables and operation calls are modeled
using the TargetLink Function/Runnable block.
AUTOSAR communication mechanisms like sender/
receiver or client/server communication are specified in
Engineering
TargetLink Inport and Outport blocks.
Specific AUTOSAR features like signal acknowledgement,
signal invalidation and status signals are modeled using
special ComSpec blocks.
Optional SWC sender/receiver blocks can be used to rep-
resent AUTOSAR ports in a Simulink/TargetLink model. TargetLink blocks for modeling AUTOSAR SWCs.
227
2016

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 syn-
chronous client-server communication. Property specifica-
tions 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. Modeling AUTOSAR SWCs
Referencing AUTOSAR objects specified in the Data

Dictionary from dedicated block dialogs
228
2016

Introduction
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
Application Fields
as run-time environment (RTE) macros according to the
AUTOSAR standard.
Software
The generated C code
for a runnable with
three included RTE
macro calls.
Hardware
Simulating and Testing AUTOSAR SWCs
With TargetLink, SWCs can be simulated in all three simu-
lation modes:
Model-in-the-loop (MIL)
Software-in-the-loop (SIL)
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 exam-
Engineering
ple, there is no asynchronous client-server communication.
229
2016

Importing and Exporting SWC Descriptions

To integrate the code generated for SWCs in the overall work, TargetLink creates the component descriptions and
AUTOSAR software architecture, software component exports the descriptions in AUTOSAR XML format. The
description files are required. These describe the struc- TargetLink Data Dictionary also lets you import and merge
tural elements such as runnables or ports that are used existing component descriptions to achieve a seamless
in an SWC. To save function designers tedious manual AUTOSAR development process with a tool like SystemDesk.
AUTOSAR Frame Model Generation

Using a software component description, TargetLink auto- a complete AUTOSAR software component. This procedure
matically generates a frame model containing the relevant makes it much easier to migrate existing models to AUTOSAR
AUTOSAR ports and runnables. The developer can then or to start modeling from scratch.
insert the control algorithm into this model frame to obtain
Migrating Standard TargetLink Models to AUTOSAR

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

For AUTOSAR software development, TargetLink is typically exchange data on the basis of AUTOSAR XML files. A top-
combined with an AUTOSAR architecture tool like System- down approach (starting with the software architecture) and
Desk. A software architecture with multiple components is a bottom-up approach (starting with a TargetLink function
specified in the architecture tool, while TargetLink is used model) can both be used for AUTOSAR round trips.
to “fill“ and implement the individual SWCs. The two tools
230
2016

Introduction
Managing Data with the TargetLink Data Dictionary
Central Data Container
Key Features
Central container for managing all data required for de- Tight integration with TargetLink

signing a model and implementing it on an ECU Full access to code specifics

Convenient administration of parameters, constants, Various import and export formats

Application Fields
signals, variables, structures, variable classes, typedefs, Full access to all TargetLink Data Dictionary objects via

scaling formulas, etc. powerful MATLAB API
Description
The TargetLink Data Dictionary is a central data container can specify structured data types and use them for variable
holding the relevant information for a model’s design, code declarations. Scaling formulas can be entered and used to
generation, and implementation on an ECU. Data dictionary uniformly scale fixed-point signals and parameters in the
Software
objects can be referenced from TargetLink models. You can model. You can import and export standardized or propri-
define and manage variables and their properties, and you etary data and share the data with the calibration system.
Hardware
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.
Engineering
231
2016

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

OIL
Data
Dictionary
AUTOSAR SWC
descriptions
API .....
The data and the model are kept
separate.
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 search-
ing 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 Data Dictionary Manager with tree view and Property Value List.
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.
232
2016

Introduction
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 applica-
tion data (post-code generation data). Selected branches of
the Data Dictionary can be loaded from separate include
Application Fields
files, which are maintained centrally for a whole workgroup.
Share Data
Import and Export Data Dictionary API
The TargetLink Data Dictionary supports various import/ The TargetLink Data Dictionary MATLAB API gives you full
Software
export formats, including access to the TargetLink Data Dictionary via MATLAB. All
Variables and Simulink data objects from/to MATLAB the functions necessary for managing data are available, for
workspace and files example, for creating Data Dictionary objects and defining
XML (Extensible Markup Language) their properties. Open API interfaces make it easy to inte-
ASAM MCD-2 MC (Standardized Description Data, grate the TargetLink Data Dictionary into your company’s
formerly ASAP2) environment. To connect your own database to the Data
AUTOSAR software component descriptions Dictionary, you can develop your own export or import
OIL (OSEK Implementation Language) functionality.
Hardware
Engineering
Exporting Data Dictionary variables into the MATLAB

workspace.
233
2016

Prepare for Calibration

After generating code, TargetLink writes a detailed descrip-
tion 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 Tool Integration

SYNECT®

SystemDesk®

VEOS®

FMI standard

TargetLink Data Dictionary Connection to SYNECT

 Define project global data
The file-based TargetLink Data Dictionary is easy to con-  Manage and reuse data across projects
 Share data in your development team
nect to SYNECT, dSPACE’s data management software
(p. 292), which acts as a central data base with multi-user
support and integrated variant management.
SYNECT
Project 1: Project 2: Project N:
 Parameters  Parameters  Parameters
 Signals  Signals  Signals
 Data types  Data types  Data types
 Scalings  Scalings  Scalings
TL DD TL DD TL DD
Fcn1.dd Fcn2.dd FcnN.dd
Fcn1.mdl Fcn2.mdl FcnN.mdl

Connecting the TargetLink Data Dictionary to SYNECT
for signal and parameter management.
234
2016

Introduction
TargetLink and SystemDesk
TargetLink and SystemDesk are the ideal combination for In addition, TargetLink users have convenient, direct access to
developing AUTOSAR-compliant software. The two tools SystemDesk’s V-ECU generation (p. 46) and VEOS’ simulation
exchange SWC containers that hold not only ARXML files, but capabilities (p. 112) for evaluating and testing the behavior of
also source files for implementation, A2L files, and other help- TargetLink components as parts of complex systems in early
ful meta information. This is a reliable, transparent way to per- development stages with constant interfaces during the
Application Fields
form AUTOSAR round trips with minimum user intervention. different development stages.
SWC Container
SWC Container Export ... SWC Container Import
.arxml .doc
Software
Container
Manager
SystemDesk TargetLink
SWC Container
Developing AUTOSAR
SWC Container Import .arxml .doc .a2l SWC Container Export software with SystemDesk
... and TargetLink based on
Hardware
.c .h the exchange of SWC
containers.
Engineering
235
2016

TargetLink Connection to VEOS®

TargetLink code can run not only in SIL/PIL simulations in This provides the following benefits for TargetLink users:
the Simulink environment, but also on dSPACE’s PC-based Early simulation of TargetLink code in large systems con-
simulator VEOS® (p. 112 and figure below). This is done by sisting of multiple virtual ECUs and plant models, includ-
wrapping code in an executable unit called a virtual ECU (V- ing buses if required
ECU), which is generated from TargetLink models. TargetLink Convenient experimentation and testing with
code can then be executed along with other V-ECUs as well ControlDesk Next Generation and other dSPACE Tools
as plant models on VEOS. To capture signals and adjust or
test parameters, A2L files exported from TargetLink are used The approach shown in the figure below is intended for Tar-
with dSPACE ControlDesk Next Generation, which provides getLink users who do not work on AUTOSAR projects. For
access to VEOS. Thus, the standard dSPACE tools used for AUTOSAR projects, it is recommended to exchange AUTOSAR
real-time simulation are also used for offline simulation and software components between SystemDesk and TargetLink,
experimentation with TargetLink-generated code. and generate the V-ECU from SystemDesk (p. 40).
Plant Model
TargetLink Model
AutomationDesk
V-ECU build Virtual ECU wraps
code generated ControlDesk
from a TargetLink
V-ECU subsystem Next Generation
Connection of TargetLink to VEOS for nonAUTOSAR users.
236
2016

Introduction
TargetLink FMI Support
As of TargetLink 4.1, FMUs based on the FMI 2.0 for Co-
Simulation standard can be exported directly from Simulink/
TargetLink models. These FMUs encapsulate the TargetLink-
generated production code and can therefore be integrated
and simulated in all environments that suitably support the
Application Fields
FMI standard. This can be done for real-time and non-real-
time simulation platforms. As a result, software developers
can create production code software in a familiar develop-
ment environment and then import and reuse it in different
environments without any manual effort.
Software
3rd-party real-time/
non-real-time
simulation environment
FMU
XML
Code
generation C Code
Libs
Hardware
Functional Mock-up
Units
Engineering
Exporting Functional Mockup Units from TargetLink to simulation environments that support FMI.
237
2016

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 TÜV SÜD (German certification
authority) for use in the development of safety-related
systems. TÜV confirmed that TargetLink is suitable for soft-
ware 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:
Software development process and software modification
process of TargetLink
Problem handling procedures
Fitness for purpose in safety-related development
according to IEC 61508 and ISO 26262 IEC 61508 is the internationally recognized generic standard
for the development of safety-related electronic systems.
TÜV SÜD also approved a reference workflow providing The automotive standard ISO 26262, which is derived from
guidance for the model-based development of safety-related IEC 61508, is the new standard for the development of
software with TargetLink. 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 develop-
ment process. dSPACE has dedicated itself to an ISO/IEC
15504-compliant development process.
Internal Software Quality Management

An internal quality department, the dSPACE quality man- provides consultation services to all software groups. It acts
agement team, proactively manages software quality at independently and ensures that the highest product quality
dSPACE. The team leads software improvement activities, goals are consistently achieved and sustained.
sets internal standards, conducts internal assessments, and
SPICE: Software Process Improvement and Capability Determination

1)
238
2016

Introduction
MISRA C
The British MISRA1) C standard is a widely accepted C subset TargetLink-generated code respects the vast majority of
for projects in the automotive industry. Its aim is to define MISRA C rules. If deviations from the MISRA C standard are a
rules for avoiding common software errors that can occur technical necessity, they are identified and well documented.
when software engineers write software by hand. Most of dSPACE makes this document available to all TargetLink
these rules also make sense for machine-generated code. customers.
Application Fields
MISRA Modeling Guidelines for TargetLink
MISRA has published official MISRA modeling guidelines for formulate requirements for modeling in TargetLink with
TargetLink. TargetLink is the first production code genera- regard to functional safety and are particularly relevant
tor for which such guidelines have been issued. With these to safety-critical projects. The MISRA TargetLink modeling
guidelines, function and production code developers have guidelines (MISRA AC TL) can be obtained from the official
an official standard that gives them support for the design MISRA website www.misra.org.uk
and implementation of vehicle functions. The guidelines
Software
Certified Code Facts About TargetLink and DO-178C/DO-331 in Brief
With the DO-178C as the future relevant standard for the Simulink/TargetLink models for specifying high-level
development of software in aviation, model-based design requirements
and automatic code generation will have a solid base for TargetLink design models for specifying low-level
use in the aerospace sector. The document DO-331, Model- requirements
Hardware
Based Development and Verification Supplement to DO- Generation of high-quality, easy-to-read, and traceable
178C and DO-278A, which is also part of the standard, was source code from TargetLink models
written specifically for this. dSPACE takes this into account Comprehensive simulation support for models and
by providing a workflow document that explains how to code according to the established MIL/SIL/PIL verifica-
use TargetLink in a model-based tool chain for DO-178C- tion concept
compliant projects. The workflow document describes how Powerful tool chain with tools from BTC Embedded
to meet the individual requirements or “objectives” of Systems for requirements specification, automatic test
DO-178C/DO-331. It focuses not just on TargetLink itself vector generation, requirements verification and
but also on a complete model-based tool chain that can formal verification via model checking
Engineering
contain further third-party tools, for example, from Target-
Link cooperation partners such as BTC Embedded Systems,
AbsInt and Model Engineering Solutions. The workflow
document is thus an important contribution towards sim-
plifying 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.
MISRA: Motor Industry Software Reliability Association

1)
(www.misra.org.uk)
239
2016

TargetLink Partner Program

The TargetLink® Partner Program was designed for compa-
nies that develop and promote products for complement-
ing and expanding TargetLink’s 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 List of TargetLink Partners:

A TargetLink Strategic Partner is a company or organization www.dspace.com/go/tlpartnerprogram
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.
Current TargetLink Partners
TargetLink Strategic Partners

BTC Embedded Systems AG www.btc-es.de
Model Engineering Solutions GmbH www.model-engineers.de
TargetLink Partners
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
240
2016

Introduction
Third-Party Tools and Services for TargetLink
This page provides an overview of complementary products List of Third-Party Tools
and services that support you in establishing a model-based www.dspace.com/go/tlpartnertools
development process and tool chain built around TargetLink.
Topic Product Company
Application Fields
Requirements tracing TargetLink
®
in combination with Simulink Verification and Validation
®
www.dspace.de

www.mathworks.de

Guideline checking MES
Model Examiner® (MXAM) www.model-engineers.de

Model analysis and review MES M-XRAY®
www.model-engineers.de

Model coverage analysis BTC EmbeddedTester®
www.btc-es.de

Simulink Verification and Validation
www.mathworks.de

Test vector generation BTC
EmbeddedTester www.btc-es.de

Reactis
®
www.reactive-systems.com

Model-based testing BTC
EmbeddedTester www.btc-es.de

MES Test
Manager® (MTest) www.model-engineers.de

Software
TPT
www.piketec.com

Formal verification BTC
EmbeddedSpecifier® www.btc-es.de

BTC EmbeddedValidator®

Code coverage analysis BTC EmbeddedTester
www.btc-es.de

Run-time error analysis Astrée
www.absint.com

Polyspace Code Prover
www.mathworks.de

Timing analysis aiT WCET Analyzer
www.absint.com

TimingProfiler

Stack usage analysis StackAnalyzer

www.absint.com

Requirements coverage analysis BTC EmbeddedTester
www.btc-es.de

Hardware
Training and development platform MEDKit on ARM – Motor Control Education Kit
www.emerge-engineering.de

ISO 26262 consulting services MES ISO 26262 Consulting Services
www.model-engineers.de

Engineering
241
2016

Production Code Generation Software / Model Compare
Model Compare1)
Comparing of Simulink®, Stateflow®, and TargetLink® models
Highlights
Graphical display of differences

Generation of difference reports

Built-in support for TargetLink

Flexible difference filters

Review support

Merge support for models

Command line interface for tool automation

32-/64-bit MATLAB® support


Automatic comparison is a must whenever you work with Model Compare finds all the changes in a model. Even large
multiple versions of a model. Model Compare from dSPACE models can be compared in minutes, which would be practi-
can be used with any TargetLink, MathWorks® Simulink cally impossible without tool support. You can use filters to
or Stateflow model, and also supports libraries. There is a focus on relevant differences and ignore unimportant ones,
broad range of use cases for Model Compare, for example: such as layout changes or simulation settings. The support
for review sessions also enables reliable, safe, and controlled
Managing different model versions or model variants
reviews of model changes. The merge support simplifies the
Merging parallel development branches
synchronization of changes in different versions of a model.
Verifying and reviewing model changes

TargetLink Support Review Sessions and Merge Support

Model Compare has built-in support for all TargetLink blocks You can associate review comments to block and property
and properties. They are displayed and handled like ordinary differences found by the tool, including date/author tracing.
Simulink/Stateflow elements, so you do not have to bother Complex reviews with multiple participants are supported.
with TargetLink implementation details. Since the semantics Detected changes can be transferred from one model to
of TargetLink properties are known, they are also intelligently another to merge parallel development branches or man-
handled by the predefined filter options. age 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.
242
2016 1)
Limited availability outside of Europe and Asia, please contact dSPACE.

Introduction
Support for TargetLink Model Compare recognizes TargetLink blocks and
There is no need to bother with TargetLink

properties, and handles them just like built-in blocks. implementation details.
Powerful comparison algorithm Models from different MATLAB versions are compared;
Conversion and upgrade problems can be addressed.

Application Fields
block correspondences are detected even if the names You get concise comparison results even if blocks were
of the blocks have changed; parameter values are renamed. Different workspace settings can be taken
compared either in unevaluated form (e.g., “Kp”) or into account.
in evaluated form (e.g., “5.4”).
Flexible filter configuration Model
Compare can be configured to filter out You can focus on the differences and model parts that

unimportant differences, e.g., layout changes or are relevant to you. This greatly improves the efficiency
simulation options, according to a variety of criteria. of a comparison.
A comparison can be restricted to selected subsystems.
Convenient result display The comparison results are displayed in synchronized
You can easily see which elements correspond to each

tree views, with differences indicated by customizable other. Added, removed and modified elements as well
color schemes. A statistics window displays the number as the number and type of changes can be seen at
of changed, added and removed elements. a glance.
Review support Comments can be associated with individual blocks and Reviews are performed in a reliable, controlled and
Software

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 You
can easily highlight Simulink and Stateflow It is easy to view the context of a change and all the

to model elements by selecting them in Model Compare, and differences in a subsystem.
show any differences directly in the compared models.
Traceability from model back to You
can trace model elements in Simulink back to This
is helpful to identify blocks and lines in Model
Model Compare Model Compare. Compare.
Merge support The
commands Copy to Right, Copy to Left, and You can merge parallel development branches and

Delete can be used to transfer changes from one transfer changes between different model variants.
model to another.
Hardware
Report generation You can save comparison results and associated
The information can be archived and published.

comments as HTML, PDF and XML reports, model
screenshots can be integrated in the difference reports.
Tool automation You
can start the comparison via the command line, You can process multiple models automatically and

and reports can be generated automatically. Reports incorporate Model Compare into your own tool chain.
can be saved in XML format for easy processing by
external tools.
Order Information
Engineering
Model Compare1) MOC

Relevant Software
Software
Required Operating system www.dspace.com/goto?os_compatibility

Integrated development environment MathWorks® MATLAB®/Simulink®/Stateflow®

Optional Production code generator TargetLink See p. 202

243
1)
Limited availability outside of Europe and Asia, please contact dSPACE. 2016

NEW: Model Compare 2.6
Improvement Detailed Description

Hook functionality for customizing block comparison Clear and accurate representation of differences also for models from other domains (HIL, RCP, etc.)
Improved search functionality The
search can also be applied to property values and provides advanced find options (e.g. regular
expressions)
Faster opening of model elements by doubleclick Faster traceability to model elements (in addition to context menu command)

Save Model Copy command Manually backing up models directly from within Model Compare, e.g. before performing merge actions

New Quick Guide and demo models Quick access to Model Compare and the frequently used features

Graphical Display of Differences

Model Compare shows all model differences clearly arranged Differences can be traced from Model Compare directly to
in two synchronized tree views, where changed, added and the Simulink/TargetLink models, where the corresponding
removed elements are indicated by customizable colors. elements are indicated by customizable colors. Thus, the dif-
While navigating through the model hierarchy, all prop- ferences can be easily inspected in the context of the models.
erty differences can be inspected in the Property Inspector. In addition, elements of Simulink/TargetLink models can
Predefined and flexible filter configurations improve the ef- also be traced back to Model Compare to inspect all their
ficiency of the comparison and let you adjust the view to differences at a glance.
your individual needs.
Graphical display of differences in Model Compare and directly in Simulink/TargetLink models.
244
2016

Introduction
Merge Support
With Model Compare you can eliminate differences be-
tween 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 these
Application Fields
changes exist in only one model.
A smart line handling mechanism automatically adjusts signal
lines of copied or deleted blocks. If a block is copied, the re-
lated 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.
Software
Report Generation
Comparison results and associated comments can be saved As of Model Compare 2.4, there are advanced configuration
as difference reports in HTML, PDF and XML format. The options for customizing the report according to individual
generated reports also include all the comments that were preferences. You can specify the subsystem level up to which
created during a review. Thus, Model Compare´s difference screenshots are provided and the level of detail of the report.
Hardware
reports are also a means of filing review results.
Engineering
Difference reports in different

file formats for publishing and/or
archiving the comparison results.
245
2016

Review Support
With Model Compare you can associate review comments
with the found block and property differences or even with
the complete comparison session. Time stamps as well as
author information are added automatically by the tool.
Thus, Model Compare supports even complex reviews with
multiple participants.
Review comments even from different users are supported.
Advanced Filter Options

To make your work as efficient as possible, Model Compare or filter out unimportant ones such as layout changes or
provides several filter options. Thus, you can focus on the simulation settings. You can also define your own filters to
differences and model parts that are relevant to you and exclude element properties or even entire model elements
your current work: Via display filters you can specify which from the comparison. To reuse the defined filter settings
model elements to show in the hierarchy display. You can in other projects, you can save them as favorites or export
use predefined filters to focus on a specific kind of difference them as XML files.
Display Filter, Block type and Property Filter as well

as predefined Basic Filters for ensuring efficient
model comparisons.
246
2016

Introduction
Customizing Block Comparison
In order to make the comparison as efficient as possible can therefore be displayed immediately, a method that
also for models from other domains, Model Compare 2.6 has already been established for TargetLink models. Thus,
provides a new add-on mechanism. This mechanism lets you Model Compare now provides a concise and efficient model
use hook scripts to integrate block-specific knowledge in comparison also for models from other domains, such as
the comparison of any number of Simulink-based models. rapid control prototyping (RCP) and hardware-in-the-loop
Application Fields
Differences in mask variables or block dialog parameters (HIL) simulation.
Software
Hardware
Engineering
Via hooks, you can format the display of differences of any block dialog parameters or mask values individually. This gives
you a concise and efficient model comparison for any Simulinkbased models, e.g., for RCP or HIL models.
247
2016

ECU Interface Software / ECU Interface Manager
ECU Interface Manager

Bypassing without ECU source code modifications
Highlights
Quickly integrates bypass hooks in ECU HEX file

Visualizes function calls, read/write accesses to ECU

variables and conditional branches in ECU code
Supports internal and external bypassing

NEW: Support of ECUs with an integrated XCP service

for bypassing via CAN/CAN FD and Ethernet
Application Areas
Service-based bypassing with the dSPACE RTI Bypass Block- of a bypass project, which might result in project delays and
set is an established model-based approach for developing increased costs.
new controller strategies for ECUs. Once the bypass service This is where the ECU Interface Manager comes into play. It
and bypass hooks are integrated in the ECU code, control allows control engineers to implement bypass hooks
engineers can flexibly choose the hooks for triggering their directly in the ECU HEX code themselves without requiring
new control strategy and select the ECU variables to be read the ECU supplier to deliver a special ECU software version.
and written by their new functions. Service-based bypassing Thus, external and internal bypass projects can be set up
also provides mechanisms to ensure data consistency and from scratch without access to the source code or build
safe operation.The integration of bypass hooks in the ECU environment. Moreover, the ECU Interface Manager can add
software typically requires iterative discussions between the service calls to an XCP service that is already integrated in
automobile manufacturer (OEM) and the ECU supplier. Often the ECU. This way, bypassing via CAN, CAN FD or Ethernet
multiple software versions have to be provided in the course can be supported as well.
Key Benefits
The ECU Interface Manager is an easy-to-use tool for quickly in the ECU code without needing to know ECU software
integrating bypass services and hooks directly into the ECU details. To minimize the influence of internal bypass functions
software. You can individually prepare the ECU HEX and on the ECU’s run-time behavior, you can deactivate the execu-
A2L files for controller strategy development by means of the tion of original ECU functions by means of a dedicated control
RTI Bypass Blockset and internal or external bypassing via the logic. You can even delete entire ECU functions and reuse
DCI-GSIs. This does not require ECU source code modifications their memory for new control functions that you are develop-
by the ECU supplier or access to the ECU build environment. ing. All this can also be done automatically through an m-API
Bypass projects can be implemented quickly and development from within MATLAB/Simulink. The ECU Interface Manager
costs are minimized. The ECU Interface Manager graphically is based on a configuration file which allows ECU suppliers
visualizes the positions of function calls, read/write accesses to configure what ECU software details are to display. The
to ECU variables and conditional branches in the ECU program configuration file can be encrypted so that ECU suppliers keep
flow. This lets you insert bypass hooks at appropriate positions full control of the information provided to the end user.
248
2016

Introduction
Order Information

ECU Interface Manager EIM_BASIC

ECU Interface Manager option for TriCore microcontrollers and internal bypass EIM_TRICORE_INT

ECU Interface Manager option for TriCore microcontrollers and external bypass EIM_TRICORE_EXT

Application Fields
ECU Interface Manager option for Freescale MPC5xxx and ST Microelectronics SPC56/57 microcontrollers and internal bypass EIM_MPC5xxx_INT

ECU Interface Manager option for Freescale MPC5xxx and ST Microelectronics SPC56/57 microcontrollers and external bypass EIM_MPC5xxx_EXT

ECU Interface Manager option for Renesas V850 and RH850 and internal bypass EIM_V850X_INT

ECU Interface Manager option for Renesas V850 and RH850 and external bypass EIM_V850X_EXT

For support for further microcontroller families, please inquire.
Software
Optional RTI Bypass Blockset
RTIBYPASS_BS

Internal Bypass Plug-In for RTI Bypass Blockset supporting the Infineon TriCore microcontroller families RTIBYPASS_BS_INT_TRICORE

Internal Bypass Plug-In for RTI Bypass Blockset supporting the Freescale MPC5xxx and
RTIBYPASS_BS_INT_MPC5XXX

ST Microelectronics SPC56 and SPC57 microcontroller families
Internal Bypass Plug-In for RTI Bypass Blockset supporting the Renesas V850 and RH850
RTIBYPASS_BS_INT_ V850X

microcontroller families
dSPACE ECU Flash Programming Tool
DSPACE_ECU_FLASH

Hardware
Optional Generic Serial Interfaces DCI-GSI1 and DCI-GSI2
See p. 601/p. 603

Workflow with the ECU Interface Manager

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

Software Engineers (ECU Supplier) Control Engineers (OEM)
ECU software development Bypass configuration Controller development
A2L  A2L file Integration of: ECU

 HEX file  Bypass services
HEX  Configuration file  Bypass hooks
(encrypted)  Control logics
Config.
encrypted
ECU Interface Manager RTI Bypass Blockset
for MATLAB®/Simulink®
MAP/ Bypass
ELF service
Bypass Service
Workflow with the ECU Interface Manager.
The bypass service is provided by dSPACE. It has to be patched bypass project, users of the ECU Interface Manager just
into the original ECU HEX file by means of the ECU Interface have to import the configuration file and the binary code
Manager, so it is supplied as binary code which is specific to of the bypass service.
certain microcontroller families (p. 249) such as Infineon During import, the ECU Interface Manager parses the ECU
TriCore, Freescale MPC5xxx, ST Microelectronics SPC5xx, or HEX file and the A2L file and determines and visualizes the
Renesas RH850 and V850. dSPACE offers bypass services for program flow with respect to the sequence of function calls,
internal and external bypassing. read/write accesses to ECU variables and conditional branch-
The configuration file usually contains a link to the associ- es in the ECU software.
ated ECU HEX and A2L files. Thus, when starting a new
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.
250
2016

Introduction
After importing the configuration file and the bypass service, that you are developing. When you have developed the new
you are ready to insert bypass hooks. You can simply insert function, you can generate a new ECU HEX and A2L file at
service calls (bypass hooks) at any appropriate position in the push of a button. If you do not want to merge the
the ECU software. To reduce run-time overhead, the execu- contents of the original A2L file and the bypass-related
tion of individual ECU functions can be deactivated by information in a single new file, you can also specify output
adding a control logic. In order to have as much free ECU a separate A2L file with information on bypass hooks. Fi-
Application Fields
memory as possible, you can also delete ECU functions that nally, the new ECU HEX file has to be flashed onto the ECU,
you do not need for a specific development task. You can and control engineers can continue developing new control-
then use the freed memory for the new control function ler strategies with the RTI Bypass Blockset.
Automation with the ECU Interface Manager

The ECU Interface Manager provides two options for auto- neers or tool experts can use a command line interface to
mation: function developers working with the RTI Bypass automate workflows and integrate the ECU Interface Man-
Software
Blockset can stay in the MATLAB®/Simulink® development ager into an existing tool chain, all without the need for an
environment and easily integrate bypass services and hooks additional MATLAB license.
in the ECU software via a MATLAB® m-API. Software engi-
Automation interface of
the ECU Interface Manager
Hardware
Remote control Integrate
via MATLAB m-API bypass service
and hooks
MATLAB®/Simulink® ECU Interface Manager
Engineering
MATLAB automation interface of the ECU Interface Manager
251
2016

ECU Interface Software / dSPACE Calibration and Bypassing Service
dSPACE Calibration and Bypassing Service

ECU service for measurement, calibration, bypassing, and ECU flash programming
Highlights
Measurement, calibration, ECU flash programming via

DCI-GSIs
Function bypassing via DCI-GSIs and DPMEM PODs

Security and data consistency mechanisms for bypassing

Application Areas
ECU calibration based on on-chip debug interfaces typi- Using the dSPACE Calibration and Bypassing Service, you
cally requires a special service implementation on the ECU can run measurement, calibration, and ECU flash program-
to measure data consistently and synchronously according ming tasks via DCI-GSIs. The service is also designed for
to given ECU rasters. In addition, for function bypassing it bypassing ECU functions by means of the RTI Bypass Block-
is usually necessary to implement service calls (bypass set in connection with DPMEM PODs and the DCI-GSIs.
hooks) in the ECU code to establish synchronized commu-
nication between the ECU and the prototyping system.
Key Benefits
The dSPACE Calibration and Bypassing Service allows you consistency and automatic failure checking. The dSPACE
to perform measurement, calibration, and bypassing tasks Calibration and Bypassing Service can be integrated into
in parallel. Flexible configuration options make it possible the ECU software either by inserting it into the source code
to tailor the service implementation on the ECU with regard manually or by using the ECU Interface Manager. dSPACE
to functionality and resource consumption. Special mech- provides consulting and engineering services to help you
anisms for bypassing guarantee minimal latencies, data integrate the service into your ECU.

Optional dSPACE ECU Flash Programming Tool (p. 257)
DSPACE_ECU_FLASH

ECU Interface Manager (p. 248)
See p. 249

RTIBYPASS_BS


Optional Generic Serial Interfaces (DCI-GSIs)
See p. 601/p. 603
Customer-specific DPMEM PODs
See p. 604
252
2016

ECU Interface Software / dSPACE Internal Bypassing Service
dSPACE Internal Bypassing Service
Introduction
Using an existing ECU for function development
Highlights
Application Fields
ECU service for internal bypassing and on-target

prototyping
Compatible with Internal Bypass Plug-In for

RTI Bypass Blockset
Only tiny footprint in the ECU RAM and flash

Software
Application Areas
Internal or on-target bypassing allows new functions to be source code and referenced later on during function devel-
prototyped and tested directly on the ECU. The ideal tool opment in the Simulink® model. Free areas in the ECU RAM
for this is the Internal Bypass Plug-In for the RTI Bypass and flash memory are used to implement internal bypass
Blockset, which is based on the dSPACE Internal Bypassing functions.
Service. Associated bypass hooks can be placed in the ECU
Hardware
Key Benefits
The dSPACE Internal Bypassing Service supports service- also provides mechanisms to ensure data consistency and
based bypassing on the target ECU. Once the bypass service safe operation. The dSPACE Internal Bypassing Service
and the associated bypass hooks are integrated in the ECU requires a few bytes in the ECU RAM, and with typical
code, control engineers can perform controller design in applications, only about 2 kB in the ECU flash. The dSPACE
the Simulink model, flexibly defining which ECU variables Internal Bypassing Service can be integrated into the ECU
are to be read or written as input or output variables for software either by inserting it into the source code manu-
the internal bypass functions and which bypass functions ally or by using the ECU Interface Manager.
are to be triggered by the hooks. Service-based bypassing
Engineering
Order Information

dSPACE Internal Bypassing Service Please inquire

Relevant Software

Optional ECU Interface Manager (p. 248)
See p. 249

RTIBYPASS_BS

Internal Bypass Plug-In for RTI Bypass Blockset
RTIBYPASS_BS_INT

253
2016

ECU Interface Software / dSPACE XCP Service
dSPACE XCP Service

ECU service for measurement, calibration, bypassing, and ECU flash programming via XCP
Highlights
Support of transport layers for CAN/CAN FD and Ethernet

Calibration, measurement and bypassing in parallel

Safety and data consistency mechanisms for bypassing

Application Areas
The Universal Measurement and Calibration Protocol (XCP) various use cases during ECU development such as measur-
is the successor to the well established CAN Calibration ing ECU variables and calibration, and also for ECU flash
Protocol (CCP). XCP is standardized by the Association for programming in connection with CAN/CAN FD.
Standardisation of Automation and Measuring Systems The dSPACE XCP Service implementation is also dedicated
(ASAM). to bypassing ECU functions using the dSPACE real-time
The dSPACE XCP Service supports transport layers for CAN/ prototyping platforms MicroAutoBox II1) and AutoBox.
CAN FD and Ethernet (UDP/IP and TCP/IP). It is designed for
Key Benefits
Depending on the transport layer, the dSPACE XCP Service For bypassing, dedicated mechanisms are provided to guar-
covers various aspects of XCP, from measurement and ECU antee minimal latencies, data consistency, and automatic
calibration to bypassing and ECU flash programming. failure checking. In addition, you can run measurement,
Flexible conﬁguration options make it possible to tailor the calibration, and bypassing tasks in parallel on the same ECU.
service implementation with regard to functionality and dSPACE provides consulting and engineering services to help
resource consumption in the ECU. you integrate the dSPACE XCP service into your ECU.
Order Information

dSPACE XCP Service DSPACE_XCP_SERVICE

254
2016 The former MicroAutoBox can also be used.
1)

ECU Interface Software / Variable Editor
Variable Editor
Introduction
Visualize, edit, and create ECU description files
Highlights
Application Fields
Create and edit ECU description files (A2L files)

Update address information of ECU variables from map

files
Automate address update and A2L file generation

via a command line
Software
Application Areas
An A2L file according to the ASAM MCD-2 MC standard widely adopted the A2L file format as a de-facto standard.
(formerly ASAP2) contains all the information about mea- The dSPACE Variable Editor is a stand-alone tool especially
surement and calibration variables in the ECU. This includes tailored to the ECU software development phase. New A2L
information on the variables’ memory addresses and conver- files can be created from scratch or existing ones can be
sion methods, the memory layout and data structures in the imported and modified. The editor is fully compatible with
ECU and communication parameters for the measurement the ASAM MCD-2 MC standard.
and calibration interface. The automotive industry has
Hardware
Key Benefits
The Variable Editor serves to visualize, edit, and create ECU In addition, the Variable Editor allows selected variables to
description files. Any number of A2L files can be imported be exported and imported and new or modified variables
into the editor, making it easy to copy and paste selected to be exchanged between users.
variables and groups into an existing or new description file.
Engineering
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.
255
2016

ECU Interface Software / Variable Editor
Main Features
Import of any number of A2L files
Option to automatically create variables from symbols

Export of ECU description files according to the
in map files
ASAM MCD-2 MC standard Address updates from map files at a click

Visualization, editing, and creation of A2L files
Dialog-based configuration of variables

Export and import of selected variables
Convenient filter and search mechanisms

Option to copy and paste variables and groups
Command line interface to automate address update

between A2L files and to create subsets and ECU description file generation
Map file manager to assign any number of map files to

a variable description
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

Variable Editor DSPACE_VAR

256
2016

ECU Interface Software / dSPACE ECU Flash Programming Tool
dSPACE ECU Flash Programming Tool
Introduction
ECU flash programming via measurement and calibration interfaces
Highlights
Application Fields
Fast ECU flash programming during development

Stand-alone tool or integrated in ControlDesk®

Next Generation
Safety mechanisms against operation

and programming errors

Software
The ECU development process frequently requires new The dSPACE ECU Flash Programming Tool can be seam-
software versions and data sets to be programmed for the lessly integrated into ControlDesk Next Generation (p. 120)
ECU. This can be done conveniently via the existing mea- or used as a stand-alone device. The tool lets you configure
surement and calibration interface. With the ECU Flash user rights for different roles, such as calibration engineer
Programming Tool you can program control units via XCP on or flash programming expert. Reliable ECU flash program-
CAN, XCP on Ethernet, or via the dSPACE devices DCI-GSI1 ming is guaranteed by flash data identification and consis-
and DCI-GSI2. tency mechanisms. Very fast ECU flash programming can
Hardware
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
ECU Flash Programming Tool.

Order Information

dSPACE ECU Flash Programming Tool DSPACE_ECU_FLASH

257
2016

RealTime Models / Automotive Simulation Models
Automotive Simulation Models

Simulating the engine, vehicle dynamics, electrical system, and traffic
Highlights
Open MATLAB®/Simulink® models

For ECU testing and function development

Intuitive graphical parameterization, and road,

maneuver, and traffic creation in ModelDesk

The Automotive Simulation Models (ASM) are open Simulink All the Simulink blocks in the models are visible, so it is easy
models for the real-time simulation of passenger cars and to add or replace components with custom models to adapt
trucks as well as their components. They are used as plant the properties of modeled components perfectly to indi-
models for the development and testing of engine controls, vidual requirements. The ASMs’ standardized interfaces
vehicle dynamics controls, on-board power electronics and make it easy to expand a single model such as an engine
driver assistance systems. or body, or even create a whole virtual vehicle. Roads and
The ASMs typically run on a dSPACE Simulator/SCALEXIO® driving maneuvers can be easily and intuitively created using
for hardware-in-the-loop (HIL) testing of electronic control graphical tools with preview and clear visualization.
units (ECUs) or during the design phase of controller algo-
rithms for early validation by offline simulation.
Modular Concept Offline and Online Simulation

The ASM concept consists of coordinated, combinable models The ASMs can be used in combination with real controllers
of automotive components. There is a vehicle model with in a hardware-in-the-loop environment (HIL or online mode),
a trailer, plus other ASMs for gasoline, diesel and hybrid or for model-in-the-loop simulations (PC or offline mode).
engines, exhaust systems, turbochargers, brake hydraulics, The same model configurations and parameters can be used
electrical systems, electric motors, environment sensors, seamlessly throughout all the steps from function develop-
roads and traffic. The ASMs support a whole range of ment to ECU testing.
simulations from individual components to complex virtual
traffic scenarios.
258
2016

Real-Time Models / Automotive Simulation Models
Introduction
Open Simulink models Almost all models are open down to the Simulink block level
Custom models can easily be added or used to replace

model components
ModelDesk Graphical user interface with parameter and simulation
Easy, intuitive parameterization and seamless simulation

management handling
Online simulation Real-time simulation on real-time hardware
Hardware-in-the-loop simulations with ECUs

Offline simulation Simulations as early as the design phase
Controller validation in early development stages

Application Fields
ASMSignalBus Simulation signals are part of a structured Simulink signal bus
Standardized and fast access to model variables

Online tunable parameters Direct parameter access during real-time simulations
Online parameter optimizations and behavior studies

Model interoperability ASM models are easy to combine to create a virtual vehicle
An entire virtual vehicle can be simulated

Order Information
Classification Type Order Number

Packages ASM – Gasoline Engine Basic Simulation Package Please inquire

ASM – Gasoline Engine Simulation Package Please inquire

ASM – Diesel Engine Simulation Package Please inquire

ASM – Gasoline Engine InCylinder Simulation Package Please inquire

Software
ASM – Diesel Engine InCylinder Simulation Package Please inquire

ASM – Vehicle Dynamics Simulation Package for VEOS® Please inquire

ASM – Vehicle Dynamics Simulation Package Please inquire

ASM – Truck and Trailer Simulation Package Please inquire

Libraries ASM – Turbocharger ASM_L_TC

ASM – Electric Components ASM_L_EC

XSG – Electric Component XSG_EC_LIB

ASM – Brake Hydraulics ASM_L_BH

ASM – Diesel Exhaust System ASM_L_DEXH

ASM – Traffic ASM_L_TRF

Hardware
ASM – Pneumatics ASM_L_PNEU

ASM – KnC ASM_L_KNC

Software
Required Integrated development environment MATLAB/Simulink from MathWorks

Simulink® Coder™ (formerly Real-Time Workshop®) 2)

Simulink Accelerator1)

dSPACE implementation software Real-Time Interface (RTI) 2)

Engineering
dSPACE experiment software ControlDesk® 2) Next Generation

Additional software Microsoft® Excel®

Operating system www.dspace.com/goto?os_compatibility

Hardware
Required Minimum system Pentium® 4 processor, 1.4 GHz or higher

Memory = 2 GB RAM

Graphics accelerator card matching the requirements of MotionDesk3)

Recommended system Intel® Core™ i5 Processor, 3 GHz or higher

Memory ≥ 4 GB RAM

Dual-head graphics accelerator card matching the requirements
of MotionDesk3)
SCALEXIO or dSPACE Simulator (equipped with DS1005 PPC Board, DS1006 Processor Board or DS1007 PPC
Processor Board)4), MicroLabBox
1)
Offline simulations only 2) Online simulations only
3)
Graphics accelerator required for MotionDesk which is part of the ASM Vehicle Dynamics Simulation Package.
259
More details on graphics card requirements and compatibility at www.dspace.com/go/mdhwrequ 2016
4)
ASM Traffic, ASM Truck, ASM Trailer, and ASM Engine InCylinder Models do not support the DS1005.

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 simu-
lated 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 de-
vices. 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 soft-
ware-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.
260
2016

Philosophy
Introduction
Supports Model-Based Design
Real-time-capable Simulink models
Provides access to internal modeling details, down to
block level
Supports all stages of controller software development
(MIL, SIL, HIL)
Application Fields
Soft-ECU network
Signal interfaces for automotive applications
Ready-to-use Off-the-Shelf (OTS) Models

One integrated tool chain for parameterization,

validation and test automation
Open documentation, including mathematical equations
Supports migration, including between MATLAB releases
Software
Worldwide customer base and mature models

Complete ASM Product Portfolio

Supports all automotive-relevant modeling areas

Hardware
Easily combinable models for building virtual vehicles

Different levels of model complexity (e.g. mean value,

physical) for all controller design and test use cases
Engineering
Comprehensive Engineering and HIL Knowledge

The one-stop supplier for all HIL-relevant tasks
Customer training and worldwide support
Combination of OTS models and custom specific
model engineering
261
2016

Combustion Engine Simulation

Real-time models for diesel and gasoline engine simulation
Simulation Packages and Models
Diesel and gasoline engines

Mean-value and InCylinder plant models

Physical turbocharger

Diesel aftertreatment system

Graphical parameterization of the

engine model for precise simulations.
Example Use Case: Gas Engines

The Task
Validating ECUs for stationary gas engines in power genera-
tion plants in a crank-angle-based simulation environment.
The Challenge
To create a flexible test environment for a combination of
engine and plant control.
The Solution
The ASM Gasoline Engine InCylinder Model enables a seam-
less transition from MIL to HIL simulation and provides a
flexible parameterization process with tool-supported para-
meter variant handling. Engine-specific features can easily
be modified due to the open model design.
262
2016

ASM Gasoline Engine Basic
Introduction
Basic mean-value engine model with combustion torque modulation
Main Model Components Features at a Glance
Air system
Unrestricted number of cylinders

Fuel system
Intake manifold with calculation of intake manifold

Piston engine
pressure and temperature
Application Fields
Turbocharger
Map-based turbocharger for boost pressure

Drivetrain (basic)
calculation
Vehicle dynamics (longitudinal)
Fuel injection system with fuel tank model

Environment (basic)
Wall film evaporation taken into account

Longitudinal driver for standard cycles (FTP75, NEDC,

J10-15, …)
Graphical preprocessing support in ModelDesk

Simulation with real ECU in hardware-in-the-loop (HIL)

system and simulated soft ECU in model-in-the-loop
simulation
Software
Start/stop system support
Simulation Model Characteristics

The actual physical engine characteristics are represented
AirPath TurboCharger Throttle IntakeManifold FuelSystem
by a mean-value engine model with crank-angle-based
Hardware
torque generation, dynamic manifold pressure, temperature
calculation, and an injection model. To simulate the engine
qinj
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 Engine- Engine-
Cooling Combustion
starter, and a test bench mode. Models for the environment nEngine
and driver complement the virtual powertrain. Trqeng
More detailed information available
Engineering
www.dspace.com/asm

Schematic of the air system.

263
2016

ASM Diesel/Gasoline Engine

Mean-value engine models with combustion torque modulation
Main Model Components
Air system
Turbocharger

Fuel system
Drivetrain (basic)

Piston engine

Environment (basic)

Features at a Glance
Up to 20-cylinder diesel/gasoline applications Exhaust-gas recirculation (EGR) of exhaust and unburned
Map-based turbocharger for boost pressure air with EGR cooler
calculation Low pressure EGR

Gasoline fuel injection system: common-rail system Longitudinal driver for standard cycles (FTP75, NEDC,

including direct injector, intake-manifold injector and J10-15, …)
tank model Simulation with real ECU in hardware-in-the-loop (HIL)

Gasoline engine with homogenous and stratified systems and simulated soft ECU in model-in-the-loop
combustion modes simulation
Diesel fuel injection systems: common rail injector, Graphical preprocessing support in ModelDesk
unit injector, unit pump and tank model Start/stop system support
Diesel exhaust system including diesel oxidation cata-
lyst (DOC) and diesel particulate filter (DPF)

The physical engine characteristics are represented by a More detailed information available
mean-value engine model with crank-angle-based torque www.dspace.com/asm
modulation, dynamic manifold pressure, temperature cal-
culation, and several fuel injection models. A soft ECU is
included for scenarios where a real ECU is not available, for
example, in offline simulation.
To simulate the engine in an AirPath Intercooler Throttle IntakeManifold FuelSystem
q
inj Manifold
automotive system (car or truck), Injection
the engine model incorporates PosThr FuelSystem

a longitudinal drivetrain model TurboCharger Direct
Injection
with manual and automatic Compressor EGR
qinj
Pos
transmission, a clutch, a torque EGR EGR
Valve
n Pos
TC VTG
Engine- Engine-
converter, a starter, and a test VTG
Cooling Combustion
neng
bench mode. Models for the Turbine Trqeng

EGR
environment and driver comple- Cooler
ment the virtual powertrain.

PosWGT
Wastegate ExhaustManifold

264
2016

ASM Diesel/Gasoline Engine In-Cylinder
Introduction
Real-time engine models with in-cylinder pressure and temperature simulation
Main Model Components Diesel applications with up to 12 cylinders with common
Air system
rail and turbocharger for real-time simulation. Unlimited
Fuel system
number of cylinders for offline simulation
Valve system
Gasoline applications with up to 12 cylinders with direct
Application Fields
Piston engine
or port injection and turbocharger for real-time simulation.
Unlimited number of cylinders for offline simulation
Turbocharger
Diesel: multiple injection patterns such as pre-, main
Drivetrain (basic)
and post-injection
Gas exchange simulation related to the lift of the intake
Environment (basic)
and exhaust valves
Fuel injection systems: common rail injector (Diesel),
Features at a Glance direct or port injection (Gasoline)
Simulation of in-cylinder pressure and temperature in
Exhaust-gas recirculation (EGR) of exhaust and fresh air
real time: for example, in response to injection or with EGR cooler
Software
variable valve timing Start/stop system support

The ASM Diesel Engine In-Cylinder Simulation Package and main and post-injection. In the combustion process, gas
the Gasoline Engine In-Cylinder Simulation Package are exchange simulation is related to the lift of the intake and
open Simulink models for developing and testing elec- exhaust valves. The gas-dynamical behavior of the air path
Hardware
tronic control units (ECUs) with engine management based and exhaust path is implemented as a mean value system
on the in-cylinder pressure. The models simulate in-cylinder with manifold pressure, temperature, and mass calculation.
pressure in real time by means of a zero-dimensional ther- The inlet and exhaust valves are modeled as isentropic orifices.
modynamic approach. The diesel combustion process sim- They can handle variable valve timing (VVT), variable valve
ulation can handle multiple injection patterns such as pre-, lift (VVL), and the simulation of engines without a camshaft.
To simulate the engine within
Air path Intercooler Throttle Intake manifold FuelSystem an automotive system (car or
q Manifold
truck), the engine model incor-
inj
Injection
porates a basic longitudinal
Engineering
PosThr Intake valve FuelSystem
Turbo charger Direct drivetrain model. Models for
Injection
Compressor EGR the environment and driver

q
PosEGR EGR
inj
complement the virtual power
Valve Engine Engine
nTC PosVTG cooling combustion train.
VTG neng
Turbine Trqeng
EGR More detailed information
Cooler
Exhaust valve
available
Wastegate
PosWGT
Exhaust manifold
www.dspace.com/asm
265
2016

ASM Turbocharger
Physical turbocharger model
Compressor
Calculates air path with the precision of a physical model
Turbine
Wastegate valve and variable turbine geometry (VTG)

Wastegate valve
Turbine power and turbine output temperature

Temperature calculated according to isentropic

efficiency
Turbine mass flow and efficiency in maps

Compressor power and output temperature

Compressor pressure ratio and efficiency in maps

Alternative to map-based model

Switching between the two models

Support of diesel and gasoline engine models

Support of SAE J922 turbine model data format

Double stage turbocharger

Heat loss calculation


The Turbocharger Model is an extension for the diesel and
gasoline engine models. It provides a more realistic model TurboCharger
of turbocharger components and the engine air path
than the map-based turbochargers models. It simulates an Compressor
exhaust gas turbocharger that consists of a compressor, a
turbine, and a turbocharger shaft. Turbochargers with
variable turbine geometry (VTG) and wastegate can be nTC PosVTG
simulated. VTG
The turbine model calculates the mass flow, the output
temperature, and the resulting power output according to
Turbine
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 PosWGT
for compressor power and compressor output temperature. Wastegate

www.dspace.com/asm
Schematic of the turbocharger system.
266
2016

ASM Diesel Exhaust System
Introduction
Real-time diesel aftertreatment system
Main Model Components Diesel Aftertreatment System
Diesel oxidation catalyst (DOC)
The diesel aftertreatment system is a combination of
Diesel particulate filter (DPF)
models of an oxidation catalyst, a particulate filter, and a
Selective catalytic reduction (SCR)
selective reduction catalyst. The system assumes an ideal
Application Fields
Support of all ASM engine diesel models
gas with a steady gas constant. The different catalyst and
filter models can be combined in any order. During simula-
tion 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.
Diesel Particulate Filter Model Components and Characteristics

The diesel particulate filter model is designed to remove Lumped parameter model
diesel particulate matter (DPM) from the exhaust gas. One-layer approach
Filter regeneration support
Software
Diesel Oxygen Catalyst Model Components and Characteristics
The diesel oxygen catalyst model simulates the physical Pressure drop over DOC/DPF
effects of an oxidation process on the exhaust gas. Temperature before and after DOC/DPF
The underlying but unmodeled chemical process can be Lambda before and after DOC/DPF
described by using excess O2 (oxygen) in the exhaust gas Particulate mass in DPF
stream to oxidize CO (carbon monoxide) to CO2 (carbon DPF regeneration by post-injection or additional injection
dioxide) and HC (hydrocarbons) to H2O (water) and CO2.
Hardware
Selective Catalytic Reduction (SCR) Model Components and Characteristics
For NOx reduction, a model with selective catalytic reduction Zero-dimensional approach
(SCR) is included. The model calculates the physical and Series connection of identical cells
chemical processes of AdBlue injection into the exhaust gas. Number of cells represents the sectional discretization
Outputs of one cell are inputs of the following cell
Adblue dosing system with and without air supply
Urea decomposition upstream of the SCR catalyst
More detailed information available Engineering

www.dspace.com/asm

Schematic of the diesel exhaust system with DOC, DPF and SCR models.
267
2016

Electric Components Simulation

Realtime models for vehicle electrics and traction system simulation
Electric components including drives and batteries

FPGA-based plant models

Parameterization of vehicle electric systems,

drives, and further electric components.
Example Use Case: Air Condition for Electric Vehicles

The Task The Solution
Evaluating the electrical energy consumption of an air con- ASM Electric Components supports the simulation of a
ditioning system in an electric vehicle. complete air conditioning system with a compressor and
fan that are driven by an electric motor. The model for the
The Challenge thermal simulation of the vehicle interior is used to deter-
To simulate the complete air conditioning system with a mine the temperature in the vehicle cabin. This value de-
focus on the electrically driven components, such as the pends on the ambient temperature, the manipulation via
compressor and fan. the air conditioning system, the fan, and the vehicle’s mate-
rial parameters. A soft ECU is used to control the vehicle’s
cabin temperature.
Expansion valve
Cabin Air mass

flow
Air channel
Tempered Fan
air
Compressor
Refrigerant circuit
268
2016

ASM Electric Components
Introduction
Automotive electrical system and electrical drives simulation
Battery
Ready-to-use components with automotive features

Multi cell battery
Prepared for testing battery management controllers

Starter
Simulation of a complete automotive electrical system

Application Fields
Alternator
Simulation of electric drive components and power

Loads
electronics in a closed loop with ECU
Electric motors (DC, BLDC, PMSM,
Demo models for simulating a hybrid vehicle or power-

asynchronous AC induction motor) train with ASM Vehicle Dynamics or ASM Engine simula-
Controllers tion models (support from dSPACE Release 2015-A).
Various auxiliary blocks Variable sample times for pulse width modulated
Three level inverter (PWM)-synchronous calculation
Discontinuous conduction mode (DCM) inverter PMSM machines with current-dependent differential

inductances
NEW: Delta-star connection configurable for threephase

Software
motor models

ASM Electric Components provides models for the real-time features. These models are also optimized for real-time HIL
simulation of a vehicle’s electrical system. Applications can simulation. The closed-loop components are ideal for HIL
range from electric drives and inverters for closed-loop simulation of electric devices such as drives or inverters in
simulation with an electric drive controller to a complete a closed control loop. The models offer variable sample
Hardware
automotive electrical system including battery, starter, times for pulse width modulated (PWM)-synchronous mod-
alternator, and loads. Typical use cases are the simulation el calculation and optimized solvers for real-time simulation.
of realistic battery behavior during starter activation, electric ASM Electric Components can be combined with other ASM
drives that are integrated into a hybrid electrical vehicle products such as the engine models and the vehicle dynam-
(HEV) power train, etc. ASM Electric Components consists ics model and is equipped with demo models.
of automotive electrical system simulation components and
closed-loop simulation components. The former can be used More detailed information available
directly to create the electric circuits of an automotive sys- Product Brochure: ASM Electric Components Model

tem, since they already have all the necessary automotive www.dspace.com/asm

Engineering
Electric Trans-
Motor mission
AC/DC
3-Phase Battery
Power
Converter
Schematic of a basic electrical system. Schematic of a hybrid powertrain system.

269
2016

ASM Multi Cell Model

To simulate high voltage batteries like Li-ion consisting of as internal resistance, diffusion and double-layer capacity
series of multiple battery cells the ASM Electric Component can be parameterized. The charge state model deals with
Model features a cell simulation model. The ASM cell model the cell‘s charge and discharge currents, and also with leak-
consists of a cell voltage model and a charge state model. age currents such as those caused by gassing effects in the
With the cell voltage model, individual physical effects such charging of NiMH cells.
Reference and Delta Models Components and Characteristics

The approach used in ASM is to connect single cells of Real-time capable simulation of multiple battery cells
identical design to create a series string of cells. This consists Complexity of the model is independent of the number
of a reference cell model that describes the basic behavior of cells
of the cell type used, and a delta model that computes the Parameterization for Li-Ion, NiMH, Pb, etc.
deviation of each individual cell‘s voltage from the reference Individual physical effects such as internal resistance,
voltage. The capacity, initial charge state and deviation from diffusion and double-layer capacity
the reference value of the internal resistance can be specified Supports charge, discharge, and leakage currents
for each cell. Online and offline simulation
Supports dSPACE‘s cell voltage emulation hardware
Graphical parameterization in ModelDesk
Supports simulation of serial and parallel connected
battery modules
Terminal current Terminal voltage

of battery Reference cell of reference cell EV1077 Vcell
model provides
ECU
reference terminal battery I bal C1
voltage manage-
ment
C2
Reference values
Terminal
voltages of
C3
cells
Delta model
for calculating C4
deviations in cell
voltage based on Voltage differences
individual parameters
CAN EV1077
of cells bus
Balancing current C5
ASM Multi Cell Model
C6
The ASM cell model consists of a reference cell model, and a delta
model that computes the deviation of each individual cell’s voltage
Cell module
C7
from the reference voltage.
C8
Vehicle ECUs Simulator
Cell voltage emulation with high precision voltage amplifiers

(EV1077) controlled by the ASM Multi Cell Model.
270
2016

XSG Electric Components
Introduction
Plant models for FPGA-based simulations
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).
Application Fields
To support identical workflows for controller development
and testing, the XSG Electric Component Models (closed-
loop simulation components) are implemented as Xilinx®
System Generator (XSG)1) models that run on a dSPACE
DS5203 (PHS Systems) or DS2655 (for SCALEXIO) FPGA
Boards. Closed-loop simulations of electric devices and their
controls are supported at very high sample rates in real time.
Direct FPGA I/O Access Components and Characteristics2):
Software
In addition to the plant models, the XSG Electric Compo- Permanent magnet synchronous motor (PMSM)
nent Library is supplemented by enhanced I/O functions Brushless DC motor (BLDC)
from the contained XSG Utils Library on the DS5203/DS2655 Advanced inverter model supporting DCM
FPGA Boards, e.g., for timing analysis and capturing digital (Discontinuous Conduction Mode)
input sources. Asynchronous Squirrel cage induction motor
The XSG Electric Components Library and the DS5203/ Resolver, Sine, TTL, and Hall encoder
DS2655 FPGA Boards can be used together for E-motor XSG EC Lib contains XSG utlis offering further
simulation both on signal and on power level. Functionality
Hardware
NEW: Delta-star connection configurable for three-
phase motor models
Example of a Simple Electric Drive Application Benefits

The FPGA carries High precision and stability
The motor model Very high oversampling rate corresponding to
The model for the three-phase inverter the PWM switching frequency
No PWM synchronization necessary
Engineering
The processor carries Current ripple (PWM effects) can be simulated
The mechanics model Better precision in simulating higher fundamental
Parameterization for the FPGA models frequencies
Open models – can be modified or partly replaced
by users
Run-time license available
Highly Nonlinear Electric Motor Models Continuous integrated parameterization workflow

Inductance and flux depending on stator current
from FEA tool JMAG®-RT to FPGA model
Spatial harmonics
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 271
in combination with the ISE Design Suite after MathWorks® MATLAB® and Simulink® Release R2013b. 2016
2)
In rapid control prototyping projects you can use the XSG Utils Library to implement ready-to-use function blocks in
FGPA models.
Vehicle Dynamics Simulation

Realtime models for ground vehicle simulation
Passenger cars

Trucks

Trailers

Brake hydraulics and pneumatics

Parameterization of the vehicle

dynamics model.
Example Use Case: Virtual Suspension Test Bench

The Task
Efficiently designing and analyzing different suspension
setups.
The Challenge
To frontload the development and tests of suspension sys-
tems by means of simulation.
The Solution
ASM KnC (Kinematics & Compliance) lets users design and
simulate wheel suspensions on a virtual test bench. Users
can run virtual tests for numerous vehicle variants and driv-
ing maneuvers to optimize vehicle suspensions and prepare
them for hardware-in-the-loop (HIL) applications.
272
2016

ASM Vehicle Dynamics
Introduction
Vehicle multibody system plus drivetrain, roads, maneuvers, and driver
Main Model Components Application Software
Engine (table based)
ModelDesk

Drivetrain
MotionDesk

Vehicle dynamics

Application Fields
Environment

Brake hydraulics and pneumatics

3DoF steering model

Engine Model Components and Characteristics

Included table-based engine that supports ECU interven- Several strategies (injection, throttle) for reducing and
tions. It can be easily replaced by a full-featured gasoline or increasing torque as requested by an ESP/TCS ECU
Software
diesel engine model. Starter to accelerate the engine to idle speed
Drivetrain Model Components and Characteristics

The drivetrain model has manual and automatic transmis- Clutch with elasticity (torsion spring)
sion, and front-, rear-, and all-wheel-drive. The shaft drives Elastic shafts included
Hardware
are modeled as elastic components. Front-, rear-, and all-wheel drive including differentials
Manual and automatic transmission with torque
converter
Model stabilized by semi-implicit Euler integration
method
Drivetrain with 13 degrees of freedom (DoFs)
Engineering
Overview of the drivetrain model configured

with allwheel drive. Modes for rear and
frontwheel drive are also available.
273
2016


Vehicle Multibody System Model Components and Characteristics
The system is modeled as a nonlinear vehicle multibody Multibody system (MBS) consisting of car body

system with geometrical or table-based suspension kinemat- and four wheels
ics and table-based compliances. It supports the simulation 10 degrees of freedom (DoF)

of vertical, longitudinal, and lateral dynamics. Table-based kinematics and compliances for suspensions
Suspension with nonlinear spring and damper

ASM Kinematics and Compliance (KnC) Testbench characteristics
ASM Kinematics and Compliance (ASM KnC) is an add-on Aerodynamics forces and torques included

to the ASM Vehicle Dynamics model that provides functions Brake model incl. physical brake booster model

for designing and simulating wheel suspensions on a vir- Additional masses (fixed on vehicle body)

tual test bench. Users can run virtual tests for numerous Sophisticated steering model with 3DoF,

vehicle variants and driving maneuvers to optimize vehicle friction elements and rack and pinion based EPS support.
suspensions and make them available for hardware-in-the- Tire models: Magic Formula and TMEasy

loop (HIL) applications. Data import from suspension design tools like ADAMS

available on request
Item DoF
Elastic powertrain 13
Body 6
Virtual kinematics and Steering system 3
compliance (KnC) test bench. Wheels 41)

1)
One independent degree of freedom per wheel for wheel vertical
displacement. The wheel kinematics are included via the MBS
algorithm.
Environment More detailed information

The environment features models for road, maneuver and available
driver. Roads and maneuvers are generated in ModelDesk. Product Brochure:
Components and Characteristics www.dspace.com/asm
Driver with lateral and longitudinal control

Roads consisting of segments with slope, inclination

and individual profiles
Driving maneuvers from ModelDesk or manual driving

A road consists of segments that can be configured individually:
bumps, a longitudinal and lateral inclination, etc.
274
2016

ASM Truck
Introduction
Truck Model for Tractor and Trailer Simulation
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
Application Fields
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.
Software
Components and Characteristics
Multibody dynamics with up to 36 DoF
Table-based axles with 3 DoF

(depends on truck configuration) Twin tires as an option on all axles

Powertrain with 25 DoF (depends on truck configuration) Axles can be activated and deactivated during simulation
Truck body based on a torsional frame Trailers can be hitched and unhitched during simulation

Tractor with up to 4 steerable axles plus trailer with up Dolly extension for road train simulation

to 4 steerable axles Vehicle configurations with arbitrary numbers of axles

Hydraulic or pneumatic brake system (ASM Brake available on request
Hardware
Hydraulics, ASM Pneumatics) Truck cabin with additional DoFs

Each wheel can be equipped with a brake
Engineering
Examples of trailer and axle variants supported by ASM Truck and ASM Trailer.
275
2016

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.

Modular multibody system (MBS) Ball-joint hitch (including mechanical stops)

Trailer body Brakes

Up to 4 axles (all axles steerable) Aerodynamics

Dolly extension for full trailer simulation Additional loads

Tire models TMEasy and Magic Formula Graphical parameterization in ModelDesk

Table-based suspension
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.
276
2016

Introduction
Application Fields
The trailer model can be configured for different trailer types,
Software
and it can be used with various towing vehicles.
Hardware
Engineering
Trailer coupling/uncoupling 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.
277
2016

ASM Pneumatics
Air Brake and Air Suspension Models
Application Areas
Air brakes

Air suspensions

Supports ABS/EBS and suspensions (car, bus, truck,

truck dolly, tractor trailer, road train)

Complete model including compressor, tanks, valves,

and brake chambers
Ready to use ABS/EBS and suspension configurations

Support for mechanical/pneumatic backup functions

Support for trailer brake systems

Graphical user interface for parameterization

Offline and online simulation

Real-time capable
Pneumatics Model Concept
Modular, library-based implementation
The pneumatics model provides ready-to-use configurations
Easy variable access
for air brake and air suspension simulations. Handling and
Add-on library for ASM Vehicle Dynamics, ASM Truck
parameterization are done via a comfortable graphical user
and ASM Trailer 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 state-
of-the-art ESP braking system.

Linear and physical master brake cylinder model

Valves with continuously controllable cross-sections

Nonlinear, look-up-table based wheel brake cylinder

Graphical parameterization in ModelDesk
Active brake booster
Product Brochure: ASM Vehicle Dynamics

Simulation of X- and II-brake system structures
www.dspace.com/asm

278
2016

Traffic Simulation
Introduction
Realtime models for traffic and environment simulation
Simulation Package
Traffic

Application Fields
Software
Graphical definition of an intersection.
Hardware
Example Use Case: Scenarios for Complex Surrounding Traffic
The Task
Defining complex traffic scenarios to analyze and test ADAS
algorithms on electronic control units (ECUs).
The Challenge
To plan and create complex traffic scenarios with several
Engineering
traffic participants and objects. The participants’ and objects’
positions on the road network and timing have to be exact.
The Solution
The Traffic Editor in ModelDesk provides a clearly structured
user interface for defining traffic scenarios conveniently. Via
graphical methods, fellow vehicles, pedestrians, traffic signs,
and other objects can easily be combined into a scenario

that can be executed in real time with ASM Traffic.
279
2016

ASM Traffic
Real-time environment simulation with traffic and objects
Features at a glance
Simulation of complex traffic scenarios

Road network simulation

Static and moving objects like traffic signs and

vulnerable road users
Multiple traffic sensor types supported

Graphical definition of roads, maneuvers,

and environment
(For information on defining traffic scenarios, please see the

Traffic Editor which is part of ModelDesk, p. 287)

ASM Traffic adds traffic and environment simulation to ASM Traffic is so flexible that any kind of traffic scenario
dSPACE’s Automotive Simulation Models (ASM). It supports can be created to ensure thorough testing of ADAS control-
you in developing and testing advanced driver assistance lers. It supports the creation of complex road networks, and
systems (ADAS) that react to other vehicles or objects, like you can define sophisticated traffic maneuvers on the roads.
adaptive cruise control (ACC) and intersection assistants. The simulated environment can consist of static and movable
The model simulates a road network, the vehicle under test, objects, like traffic signs and pedestrians. Various sensor
a multitude of fellow vehicles and the necessary environment. models and user-definable sensors are available to detect
The test vehicle can be equipped with multiple sensors for these objects. To test pre-crash functionalities, you can
object detection and recognition (ego-vehicle). ASM Traffic define traffic scenarios that in real life could result in an
is typically used for hardware-in-the-loop testing of elec- accident, and observe system behavior under challenging
tronic control units (ECUs) or for early function validation conditions. Traffic scenarios can be modified and immedi-
by offline simulation during the design phase of controller ately simulated without having to generate code again.
algorithms.

ASM Traffic consists of a graphical user interface (GUI) and trians are calculated in real time according to the defined
a set of simulation models that perform in real time. The traffic maneuvers. ASM Traffic supports specific scenarios
GUI provides several interfaces to define the necessary such as oncoming traffic, stop and go, and pedestrians. The
components like road networks, traffic signs, traffic vehicles, Traffic Editor is the user interface for very flexible and easy
and sensors. Trajectories for all vehicles, objects and pedes- traffic scenario definition.
280
2016

Introduction
Road Networks
Features
Road networks with roads and intersections for vehicle
dynamics and ADAS use cases
Segment- and coordinate-based road definition
Lanes with smooth transitions and specific line
definitions
Application Fields
Up to 5 lanes per lane segment
Support for lane detection sensors
GPS coordinate exchange with turn-by-turn navigation
development tools
Simulation of tire characteristics and road surface
conditions like split-μ surfaces, bumps, potholes
Software
Define roads and junctions graphically.
Maneuvers
Hardware
Features
Movement control of vehicle under test (ego-vehicle)

Maneuver segments defined by distance or time

Event-based segment changes

Lane driving and lane transition/change definitions

Trigger events for specific maneuver activities

Open- and closed-loop maneuvers

Velocity, steering, and pedal actuation can be set by

Engineering
using measurement data.
User output signals programmable via time and

distance
External velocity and pedal access for man-in-the-loop

use cases
Define where and how the egovehicle drives on the road network.
281
2016

Traffic
Features
Simulation of objects around ego-vehicle
Definition of various traffic situations and complex
scenarios
Lane driving and lane change definition
Support for intersections with oncoming and crossing
traffic
Maneuvers based on distance, velocity and acceleration
Independent and interdependent movements
Time- and road-based trigger events
Direct link between model and animation update
Define where and how the surrounding fellow vehicles drive on the
road network.
Objects and Sensors

Features
Definition of any number of traffic objects
Road- and intersection-based positioning
Graphical representation in MotionDesk
Moving objects like pedestrians
Static objects like traffic signs, traffic lights,
parked vehicles, houses
2-D object sensor
3-D object sensor
Custom sensor
Traffic sign sensor
Define sensors on the vehicle and traffic signs, obstacles and
scenery along the road.
Overview of Objects
Sensor Type Object Sensor Output
and Sensors
Traffic Signs
80 Speed limit, 80
2-D
More detailed
information available: Custom
Product Brochure: Adult / Child
ASM Traffic
www.dspace.com/asm
3-D
282
2016

ModelDesk
Introduction
The graphical user interface
ModelDesk Concept Main Features
ModelDesk is a graphical user interface for simulation, Offline and online simulations

intuitive model parameterization and parameter set man- Graphical user interface

agement. It also provides project handling and allows Parameter set management

Application Fields
parameter sets to be downloaded to offline and online Road Generator

simulations. It supports tool automation via Python scripts. Maneuver Editor

ModelDesk can be used seamlessly from parameterization Traffic Editor

to offline and online simulation, and finally to parameter Tool automation

and result management. Preprocessing for engine models

Custom model parameterization

Benefits
Seamless simulation process from MIL to HIL

Intuitive, graphically supported parameterization

Software
Parameters changed online and offline

Managing parameter sets and entire projects

Hardware
Engineering
ModelDesk’s user interface for selecting model subsystems for configuration, parameterization, and simulation on platforms like a PC,
dSPACE VEOS, and dSPACE Simulator.
Graphical Parameterization Parameter Management

The model components and their subsystems are repre- ModelDesk’s Project Navigator provides a means of organiz-
sented by a hierarchical graphical structure. The model ing and managing large-scale model parameterization
components to be parameterized can be selected from the projects. Parameter files can be created and assigned to
top level. Users have the vehicle model before them and each model component (differential, tires, road, etc.), and
can browse through its systems, guided by graphical repre- complete vehicle parameter sets can be created and man-
sentations of the modeled components. aged. Existing parameter files can be selected from a
parameter pool and applied by drag & drop.
283
2016

Simulation Management
ModelDesk includes powerful functions for directly executing
and displaying simulations, and managing their results:
Starting and stopping a simulation
Plotters for visualization
Saving, comparing and managing simulation and
measurement data
Saving simulation experiments
(driving maneuvers, roads, traffic, etc.) Configuration of a simulation experiment consisting of a vehicle
model, road, maneuver and vehicle parameters.
Plotter
ModelDesk features an integrated plotter which displays simulations). A configuration includes the following data:
signals from the ASMSignalBus. The signals have the same simulation results, measurements, and parameter sets con-
structure as in the Simulink model. The bus can include sisting of vehicle parameters, roads, maneuvers, and/or
user-defined signals. Plotter configurations can be defined traffic. A configuration collects together all the sources and
and stored, and the same single configuration can be used conditions that the plotted results are based on.
seamlessly online (HIL simulations) and offline (Simulink
Features
Plots of ASM signal buses
Plots of user-defined signals
Plotter configurations can be saved
The same configuration to be used online and offline
Plot printouts
Configuration comprises measurements, simulation
and parameters
ModelDesk’s plotter displaying various vehicle dynamics signals.
Visualization with MotionDesk

ModelDesk and MotionDesk work seamlessly together. In ate objects like buildings, trees, borders, reflector posts, and
ModelDesk, users can define scene types such as country street lamps. These can also be modified as required in
roads, tree-lined roads, and urban areas. The scenes are MotionDesk’s integrated Scene Editor.
then automatically generated in MotionDesk with appropri-
284
2016

Introduction
Road Networks
Road Generator Features
The Road Generator is the graphical user interface for defin- Support for vehicle dynamics and advanced driver
ing road networks and sophisticated road features. Roads assistance traffic scenarios
can be assembled from geometric segments or imported. Segment and coordinate-based road definition
Features such as lanes, intersections, height, inclination, Intersections and junctions
surface condition, etc., can easily be added to a road by Lane, line and traffic sign definition
Application Fields
editing attributes that are displayed in 1-D diagrams. The Height, inclination, and surface condition applied via
whole road network is visualized in a 2-D view. The road segment-independent road coordinates
design also interacts closely with the 3-D animation software Easy definition of bumps, profiles, split-μ areas, etc.
MotionDesk to define the environment. The Road Generator Dedicated 1-D and 2-D views of road features
gives ideal support to complex traffic scenario creation in Road import: map data (like OpenStreetMap, Google
the development and testing of advanced driver assistance Maps, etc.), ADAS RP (Nokia HERE), and OpenDRIVE®
systems (ADAS). format
Road networks and predefined sceneries are automa-
tically imported into MotionDesk (city center, country
road, highways)
Software
Definition of driving routes
Hardware
Engineering
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).
285
2016

Maneuver
Maneuver Editor Features
The Maneuver Editor is used to define how and where a Definition of driving maneuvers based on road network

vehicle moves on the road network. Maneuvers consist of routes
several segments with their own individual properties. There Maneuver segment definition by distance or time

can be simple maneuvers that just follow the road or very Lane driving and lane change definitions

sophisticated ones based on several stimuli, or user inputs. Definition of steering and pedal stimuli or driver-based

A maneuver also defines the driving lane and the lane maneuvers
changes of the test vehicle. The road or road network the Standard maneuvers included (lane change, µ-split,

maneuver relates to is visualized for intuitive maneuver steady-state cornering, fish hook, etc.)
creation. Lateral and longitudinal stimuli can be imported

from measured data (MAT files).
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.
286
2016

Introduction
Traffic
Traffic Editor Features
The Traffic Editor is the graphical user interface for defining Definition of traffic fellow movement based on road

the movements of the fellow vehicles on a road network. network routes
The Traffic Object Manager (TOM) is used to give fellow Segment-based definition of fellow vehicle movement

Application Fields
vehicles additional characteristics. Traffic objects like signs All vehicles on one page

or construction barriers can also be defined and placed in Overview and detailed view

road networks. Convenient graphical editing

Traffic scenarios are defined on a single page that can be Definition of fellow and traffic object parameters in

completely customized from complete overview to maxi- Traffic Object Manager
mum detail. Easy-to-use fellow vehicle activity definitions

Example of the traffic definition page. Software

Hardware
Engineering
287
2016

Processing
Parameter Processing
ModelDesk provides a fully integrated parameterization MATLAB programming environment. In addition to this
workflow. Users can include initial data, such as measure- customizable parameter calculation, sophisticated error
ments, functions, and settings, flexibly and process it into handling procedures have been integrated to support the
parameters optimized for simulation models. Users can write users during parameterization.
the processing routines for parameters in the well-known
Import
Process
Measurement data ModelDesk
Download
Parameter
dSPACE VEOS® dSPACE SCALEXIO® MATLAB®/Simulink®

(offline simulation) (real-time simulation) (offline simulation)
The processing feature transfers measurements, settings, and functions into parameters optimized for simulation.
Features Custom Models and Demo Projects

Read and process measurement data This feature can also be used in combination with custom
Function administration components to parameterize own libraries with ModelDesk.
Settings administration A demo projects for the ASM engine models provide pre-
Execute functions with appropriate error handling defined parameterization routines, to deliver a semi-auto-
Adapt parameter as a result of a processing function mated calculation of all model parameters.
Use Cases
Engine parameterization based on testbench

measurement
Battery parameterization based on impedance

spectroscopy
Suspension kinematic parameterization based on

kinematic and compliance testbench data
288
2016

Introduction
Tool Automation
Remote Control and Batch Processing for ModelDesk Features
To perform long-term tests or parameter studies, ModelDesk Script-based tool automation

provides script-based tool automation. This gives you max- Integrated Python interpreter

imum flexibility to define custom simulation scenarios. Tool Direct access to project and experiment management

Application Fields
automation can be performed by means of scripting lan- Direct alteration of all vehicle model parameters

guages like Python and MATLAB M scripts. Direct alteration of maneuver segments

The scripts can be executed either externally to remote- Direct alteration of road features

control ModelDesk or internally when ModelDesk’s batch
mode is used. The batch mode functionality is realized by Benefits
a Python interpreter that supports Python 2.5.1. Direct alteration of traffic maneuvers

Simulation-based parameter studies

Automated marginal condition analyses/detection

Long-term behavior studies

Sequential maneuver executions

Software
Functionality
All ModelDesk’s functions for experiment management and ization projects and activate predefined experiments. All the
model parameterization that are available via its GUI can vehicle parameters such as vehicle mass, suspension kine-
now also be accessed via its COM (Component Object matics, engine torque, additional loads, and similarly also
Model of Microsoft® Windows®) interface (except road and environment or maneuver settings like road friction or
Hardware
maneuver creation). You can load existing model parameter- vehicle velocity, can be controlled from within scripts.
ModelDesk
Script
Project handling
Parameterization
Engineering
Parameter download
The scriptbased tool automation for

ModelDesk provides functionality for

parameter set management and for direct
model parameterization. The parameters
dSPACE VEOS® dSPACE SCALEXIO® MATLAB®/Simulink®
(offline simulation) (online simulation) (offline simulation) of online and offline simulations can be
changed during a simulation run.
289
2016

Custom Model Parameterization

Graphical Parameterization of Features
Custom Models Automatic generation of new parameter pages based

ModelDesk supports the graphical parameterization of on custom models
model parts that were replaced by custom models or custom Controls provided according to parameter dimension

extensions to ASMs. This allows you to manage all the (scalar, vector, table)
parameters of a project from a single source. Original ASM and customized model parts displayed as

one system
Benefits
Centralized parameter management

Graphical parameterization without detailed modeling

knowledge
Model Preparation Custom Library Registration

For use in ASM, custom model libraries have to be prepared ModelDesk’s registration function lets you select new librar-
according to ASM guidelines in order to parameterize them ies to parse them and make their parameters available
in ModelDesk. The guidelines mainly define how parameters graphically. During registration one or more parameter
are declared with masked variables and a fixed declaration pages are created automatically, depending on the number
structure. Libraries can have multiple masked subsystems, of masked subsystems. Each page lists the controls of de-
and each subsystem has its own parameter page for sepa- clared parameters. Controls can be single entry fields for
rate parameterization. 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.
290
2016

ASM Versions and License Concept
Introduction
The ASM License Concept
The ASM models come with different license types: Devel- Mutual Parameterization – With all license types, all

oper License, Runtime License. This lets users apply the models can be parameterized with ModelDesk’s para-
models in various kinds of applications, without losing any meterization options for simulation on a PC (offline) or
of the characteristic ASM flexibility. on dSPACE real-time hardware (online).
Exchangeability – You can switch the license types Seamless 3-D Animation – The vehicle dynamics

Application Fields
for your models from Operator License to Developer models provide access to MotionDesk with all license
License and vice versa if you have both these types. types. The model must include the MotionDesk block-
set.
The Benefits
A simulation environment that seamlessly covers Cost-efficient license types for offline and online (real-

the offline and online (real-time) worlds. time) simulation
Software
ModelDesk is the parameterization tool throughout the Simulation models parameterized and reconfigured

entire process, which means that the parameterizations in ModelDesk with the Runtime License. This enables
can be reused. real-time simulation on a dSPACE HIL system without
an additional MATLAB license.
Hardware
ASM Developer License Properties
The Developer License offers all of the available model Open, modular models, viewable right down to
options and supports all development steps and types of the Simulink block level
applications. Customer-specific model parts can easily replace or ex-
tend ASM modules.
Real-time code generation support
Simulation on a PC (offline) or on dSPACE real-time
hardware (online)
Engineering
ASM Runtime License Properties

The Runtime License is designed specifically for simulation Real-time code for simulation on dSPACE real-
on real-time hardware (online). time hardware
Code for simulation on dSPACE VEOS
Code already generated from the models via

the Developer License
Customer-specific modifications are not supported
291
2016

Data Management Software / SYNECT
SYNECT®
Data management software for modelbased development and ECU testing
Highlights
For model-based development and ECU testing

Integrated variant management

Direct connection to engineering tools

Traceability between requirements, models,

parameters, and test cases
Open API for integration into existing IT infrastructure

and workflows
High scalability to variably-sized, distributed teams


SYNECT is a data management and collaboration software SYNECT integrates all your development data into one
tool with a special focus on model-based development and single environment.
ECU testing. The software is designed to help you manage Directly store and reuse the data objects found in your
data throughout the entire development process. This data model-based development and ECU testing processes.
can include models, signals, parameters, tests, test results, Work with your preferred tools in every development
and more. SYNECT also handles data dependencies, versions phase and benefit from easy data flow, because
and variants, as well as links to the underlying require- SYNECT integrates with engineering tools and supports
ments. One key aspect of SYNECT is direct connection to standards commonly used in model-based development.
engineering tools, e.g., MATLAB®, Simulink®, TargetLink®, or Stay on top of the escalating number of variants with
AutomationDesk, and application/product lifecycle manage- SYNECT’s built-in variant management.
ment systems (ALM/PLM) so that you can work with your Benefit from fast deployment due to the modular
preferred tools and seamlessly exchange data. SYNECT is and scalable product architecture.
ideal for automotives, aerospace, industrial automation and Customize SYNECT to your needs and integrate it into
medical engineering – and wherever embedded systems are your IT architecture thanks to SYNECT’s open structure.
developed through model-based design. Benefit from SYNECT´s open architecture to implement com-
pany-wide processes via connections to ALM/PLM tools
Modular, Scalable, and Secure

SYNECT focuses on the efficient, integrated management ment teams, and scale your system to the team size. From
of all your design and development data throughout the local to global, SYNECT grows with your needs. The platform
model-based development process, yet it can also be scaled supports access control and easy sign on, for example via
to fit specific use cases. SYNECT has modules for individual Windows® authentification, and offers secure communica-
areas such as test management, model management, signal tion (e.g., automatic transaction protection for server scripts
and parameter management, and variant management. This via SYNECT API), version control, and automation. Further
means that you can introduce SYNECT step-by-step and in secure mechanisms come with the easy integration in Win-
specific teams such as testing groups or function develop- dows® Server Systems (Internet Information Services, IIS).
292
2016

Introduction
Module Overview
Module Description
SYNECT Test Management (p. 294) SYNECT module for the intuitive management, planning, monitoring and evaluation of

all test activities
SYNECT Signal & Parameter Management (p. 299) SYNECT module for managing signals, parameters and parameter sets for controller

Application Fields
functions, ECU software and also plant models throughout the entire development process
SYNECT Model Management (p. 302) SYNECT module for managing models together with their interfaces, parameters and related files

SYNECT Variant Management (p. 306) SYNECT
module for defining and managing variants and their impact on design and
development data
SYNECT Base SYNECT module for working with multiple clients on a common server, for user and rights

management, and for fine-grained version and configuration management
Order Information
Software
SYNECT Test Management SYNECT_TEST_MGMT

SYNECT Signal & Parameter Management SYNECT_PAR_MGMT

SYNECT Model Management SYNECT_MODEL_MGMT

SYNECT Variant Management SYNECT_VARIANT_MGMT

SYNECT Base SYNECT_BASE

Additionally, dSPACE offers the SYNECT-based Workflow Management solution (p. 312), which lets you handle complex, variant-based workflows,
especially for HIL and modeling use cases.
Hardware
arameter M
al & P
Sign ana
ge
ECT m
N e
Y Variant Manag
nt
T em
S
C
NE e
SY
nt
NECT Base
SY
Engineering
SYNE CT M o
Data
ement
Base
anag
de
tM
lM
s
Te
ag
an
C
T
em
en NE
t SY
SYNECT has a modular and scalable structure, providing several functional modules.
293
2016


Highlights
Manage MIL/SIL/PIL/HIL tests and test data
Off-the-shelf integration with AutomationDesk
and BTC EmbeddedTester®
Connection to MATLAB® and Python
Monitore, analyze and visualize test results
Interface to requirements management
Test case parameterization
Integrated variant support
Application Areas
SYNECT Test Management supports the intuitive manage- in-the-loop (HIL) testing by directly connecting to test
ment, planning, monitoring and evaluation of all test activi- automation tools. Your whole team’s tests, test data and
ties in ECU development projects. The software provides test results are stored centrally and made available for
special support for model-in-the-loop (MIL), software-in- analysis and status monitoring independently of the test
the-loop (SIL), processor-in-the-loop (PIL) and hardware- 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: Test efficiently:

Centrally manage all test activities across different test
Systematically plan and control test execution.
levels and tools in your development project. Check the requirement coverage and assess the ma-
Trace your requirements up to test results by interfac-
turity of your system under test at any time.
ing to requirements management tools. Use existing test authoring and execution tools such
Monitor your test results, archive your test result history,
as AutomationDesk, BTC EmbeddedTester®, Python
and generate reports for a comprehensive overview. scripting or MATLAB® scripting as a basis for test
Let all users work on the same, consistent set of tests,
cases in SYNECT Test Management.
test data, and test results with multi-user support. Manage test execution on different platforms:
dSPACE HIL systems, Simulink®, TargetLink®, VEOS®,
MicroAutoBox II, etc.
Adapt the system to your small or even large, globally
distributed teams with advanced, scalable client-server
architecture.
294
2016

Introduction
Working with SYNECT Test Management
Test Test Planning Evaluation

Specification and Execution and Reporting
Application Fields
Import
Test cases
Requirements
Test automation adapters
Software
Test platforms
Manage all test activities with SYNECT Test Management.
Supported Tools and Interfaces for SYNECT Test Management
Hardware
Requirements Test Authoring and

Management Execution Tools
Tool / Interface: Tool / Interface:

 IBM® Rational® DOORS®  AutomationDesk
Engineering
 PTC® Integrity  BTC EmbeddedTester®
 Microsoft® Excel®  Python scripting
 Microsoft® Team Foundation  MATLAB® scripting
Server  Microsoft® Excel®
 ...
 Vector CANoe
 Vector vTESTstudio
 ...
295
2016

Importing Test Cases

When you define your tests, you can reuse existing tests SYNECT come with a standard set of attributes (e.g., test
by importing them to SYNECT Test Management. You can priority, test platform, test manager, date last executed),
source data from several tools: test lists from Microsoft® but you can also define your own attributes, of course.
Excel®, and test implementations from AutomationDesk, And you can define your own test adapters, so you can use
BTC EmbeddedTester®, MATLAB®, or Python. Tests in virtually any of your testing tools or simulation platforms.
Traceability to Requirements and Test Specifications

Thanks to the requirements handling support (p. 311), 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 SYNECT’s
automation features by automatically resynchronizing re-
quirements 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. the test data for different variants, you can specify variant
For example, test cases can be released so that they can no dependencies and select which variant configurations will be
longer be modified. This lets you reuse existing test cases supported. You can work with variants by using this module
in new test plans (see Versioning on p. 288). To manage in combination with SYNECT Variant Management (p. 310).
You can use filters and conveniently group or sort

your tests for an optimal overview.
296
2016

Introduction
Test Planning and Execution
SYNECT Test Management easily integrates with test auto various criteria: for example, it can include all your tests for
mation tools such as dSPACE AutomationDesk and BTC one variant or for one ECU function. Execution plans can
EmbeddedTester®. It does this via adapters that control the also be defined using queries that will select test cases which
test automation tool. fulfill a defined criterion. Your test tools use the execution
To carry out tests, you set up execution plans and add previ- plan to run the tests and return the results to SYNECT Test
Application Fields
ously defined tests to them. An execution plan is a collection Management, where you can view the overall tests results
of tests that have to be executed, and it can be based on and assess the progress of the test.
Software
Dialog for defining
test execution plans.
Hardware
Engineering
297
2016

Test Result, Test Report and Requirements

Coverage Views
Monitoring testing activities and test progress can be a chal- display selected test attributes and use them for actions
lenge, especially when many people are involved. SYNECT such as creating an error burndown chart for your project.
Test Management helps you keep track of all tests, whether A requirements coverage view is available at a mouse click,
planned or already executed. An interactive evaluation func- so you can see which requirements were already tested and
tionality and the ability to generate and export reports lets what the associated verdicts were. Requirements coverage
you evaluate results systematically. For example, you can results can also be exported in a customized report.
Example of a result evaluation, showing test

progress over several calendar weeks.
Requirements coverage view.
298
2016

SYNECT Signal & Parameter Management
Introduction
Highlights
Manage signals, parameters, and parameter sets
For controller software development and plant models
Interface to Simulink® and TargetLink®
Support of standards and standard file formats
Interface to calibration and experiment tools
Application Fields
Integrated variant support
Software
Hardware
SYNECT Signal & Parameter Management is used for the Use the same tool for parameters in all development
central management of signals, parameters and parameter phases – from early M files to ECU calibration
sets throughout the entire model-based development pro- Work in collaboration on large parameter sets
cess. It can handle the signals and parameters of controller Keep track of the history of signals and parameter
Engineering
functions, ECU software and also plant models. It supports values
commonly used file formats and standards and provides Master variant complexity by automatic synchronization
direct connections to engineering tools, so you can easily of variant-dependent parameters across all variants
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.
Moreover, SYNECT Signal & Parameter Management extends

SYNECT Model Management for interface specification
and parameter definition, and complements SYNECT Test
Management for test case parameter management.
299
2016

Working with SYNECT Signal & Parameter

Management
So that you can work with your signals, parameters and from the option to exchange variables, type definitions and
parameter sets efficiently and communicate with the “out- scalings between the file-based TargetLink Data Dictionary
side world”, there are several import/export filters that let and SYNECT, the central database with multi-user support.
you exchange and use data during the development pro- To manage parameter sets for different variants, you can
cess. Simulink® users benefit from the import and export specify variant dependencies and select which variant con-
of MATLAB® M files to flexibly exchange parameter values figurations will be supported. You can work with variants
and signal and parameter definitions between the mod- by using this module in combination with SYNECT Variant
eling environment and SYNECT. TargetLink users benefit Management (p. 306).
Exchange variables, type definitions and scalings easily between

TargetLink Data Dictionary and SYNECT.
300
2016

Introduction
Plain variables, Signal and para-
Simulink® data objects meter definitions
.m files .xls, .xlsx,
Application Fields
Parameter Variant 1 Variant 2 Variant 3 .xml, .csv
A 1 1 1.5
Variables, scalings, B 2 2 1 Parameter A=1;
TargetLink typedefs C 7.9 7.7 8.0 values B=2;

C=7,9;
Data Ki 3 3.0 - Ki=3,0;
Dictionary K1 - 1.1 1.1

.cdfx, .dcm, .m,
K2 - 14.1 -
.par, .xml
.dd files K3 - - 5.1
ECU image files

AUTOSAR
.arxml Signal & Parameter Management
.hex, .mot,
.s19
Customer-specific
Software
import/export filters
Open plug-in concept (e.g., Python adapter scripts)
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.
Hardware
Version Version Version
1 1 1
A=1; A=1; A=1,5; 2
B=2;
A=1; 2 B=2;A=1; 4 A=1,5;
B=1; A=1,5; 3
C=7,9;
B=2; 3 C=7,7; B=1;
C=8,0;B=1;
A=1;
...
B=2;
Ki=3,0;
C=7,9; Ki=3,0; C=8,0;
Ki=3,0;
1 A=1;
B=2; 4 C=7,7; C=8,0;
Ki=3,0;
C=7,9;
B=2;
K1 =1,1;
Ki=3,0; K1 Ki=3,0;
=1,1;
Ki=3,0;
K2 =K1
14,1; K1 =1,1;
K3 = 5,1;
Ki=3,0;
C=7,9; =1,1; K1 =1,1;
K3 = 5,1;
Ki=3,0; K2 = 14,1; K3 = 5,1;
Variant 1 Variant 2 Variant n
Engineering
Parameter Variant 1 Variant 2 Variant 3
A 1 1 1.5
B 2 2 1
Software Developer C 7.9 7.7 8.0
Ki 3 3.0 -
K1 - 1.1 1.1 Calibration Engineer
K2 - 14.1 -
Function Developer
K3 - - 5.1
File-based parameter management generates a large number of files. SYNECT centrally manages parameter sets for different variants.
301
2016

SYNECT Model Management

Highlights
Manage models together with their interfaces, param- Supports Simulink® models, TargetLink models and FMUs

eters and related files Provides open interfaces to support further modeling

For distributed development and for sharing and reus- environments
ing models Comprehensive model categorization through custom-

For controller models and simulation models from vari- izable metadata
ous modeling environments Integrated variant support


SYNECT Model Management lets you manage your prime Share and reuse models within an organization
asset in a model-based development process – your models. by managing them in one central location
It combines model file management, model metadata man- Make it easy to find the right models by organizing
agement and model interface management1) – all in one tool, them in libraries, projects, together with alternative
all accessable from one GUI. You can organize your models implementation variants, and in relation to other
in libraries with dedicated user and rights permissions and models
according to their variant dependencies. The modeling of Increase model transparency with comprehensive,
hierarchical dependencies between models and submodels customizable metadata
allows building and configuring model compositions from Keep track of model evolution with fine-grained ver-
different libraries or work projects. Defining and inspecting sioning of models, interfaces, parameters and model
the model architecture directly in SYNECT not only increases files
the transparency of the models directly in the data man- Implement top-down model development processes
agement solution, it also supports implementing top-down by defining the model architecture and interfaces
development processes for new models. before implementation
302
2016 1)
Requires SYNECT Signal & Parameter Management (p. 299).

Introduction
Models
SYNECT Model Management manages both the model struc- when you start to actively manage model structure and
ture and the actual model implementations by using model interfaces directly in SYNECT. By linking signals and param-
files of the supported modeling environments. eters from SYNECT Signal & Parameter Management data
Model structure information can be used as a purely pools to your models, you can easily implement central
descriptive feature, increasing transparency and model signal and parameter management for your models. This
Application Fields
understanding directly in the data management solution, enables top-down model development and makes it easier
without accessing the actual modeling environment. to keep model interface consistency for smoother model
You will get the most out of SYNECT Model Management integration.
Par Par Par Par Par Par
In Sub Out In Sub Out

Model Model
In Out In Out
Software
Sub
In Model Out In Out
Model
Sub
In Model Out
Model
Par Par Par
Par Par Signal & Parameter Par Par Par
Management
In Sub Out In Sub Out
Model Model
Hardware
In Out In Out
Sub Sub
Model In Model Out
Model Model
Model Implementations
Engineering
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 man-
agement systems, link them with your models in SYNECT,
and manage them directly from SYNECT.
303
2016

Model Variants:
One Model, Multiple Implementations
Model
SYNECT lets you manage multiple implementations
with the same model and its structural properties. As
an organizational feature it helps you group alternative
Implementation Implementation Implementation
implementations, called implementation variants. You can Variant A Variant B Variant C
declare the variant dependencies of the individual implemen- Version (17) Version (12) Version (19)
tations according to the variant models defined in SYNECT Version (16) Version ... Version ...
(see SYNECT Variant Management module, p. 306). Version ... Version (1) Version (1)
Version (1)
Model Metadata
The SYNECT metadata model contains standard metadata information such as the modeling environment, fidelity level
and can also be extended with user-specific metadata at- for simulation models, or implementation detail level for
tributes. Metadata is handled both on the model level as controller models can be handled at the implementation
well as on the model implementation level. Properties that level. A well thought-out set of metadata will make it easy
are valid for all implementations of a model can be managed to find, sort and categorize the models you are managing
at model level, such as the categorization of models as con- in SYNECT.
troller models, plant models, etc.. Implementation-specific
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 cover-
age reports.
304
2016

Introduction
Workflows
Bottom-Up
With this workflow, existing models are imported into & Parameter Management functionality. Import adapters are
SYNECT Model Management via tool adapters that are spe- currently available for Simulink models, TargetLink models,
cific to the modeling environment. During import, the essen- and for FMUs (Functional Mock-up Units). The XML import
tial structural information of the model is collected, such as adapter offers a generic way to import model structure
its inputs, outputs and parameters. After the import these information into SYNECT. The XML file can be provided
Application Fields
items can be managed individually with the SYNECT Signal directly by a modeling tool or a custom tool adapter.
Top-Down
In this workflow, new models can be defined by structure for Simulink models and for TargetLink models. The existing
in SYNECT and then exported as structural frame models to adapters are open implementations that can be adapted to
supported modeling environments for the subsequent imple- customer-specific conditions. The XML export adapter can
mentation of behavior. The same procedure can be applied if be used to implement completely new tool adapters for
structural changes (such as interface changes) will be made additional modeling environments.
Software
in existing models. Export adapters are currently available
Define new Configure

models models
Simulink®
Simulink®
Hardware
TargetLink
Import TargetLink Export
models models
FMI
Custom (XML)
Custom (XML)
Manage models
Engineering
Modeling/simulation in external modeling tool
Model Configuration
You can define new composite models by combining exist- with the respective model files of the specified submodels
ing models as submodels of the new composite model. in the correct version and variant for further use. Custom
To configure the composite model, just select the specific export adapters can be used to create or configure inte-
implementation variants and versions to be used for each of gration frame models according to your own integration
its submodels. By default, SYNECT provides the file system mechanisms.
305
2016

SYNECT Variant Management

Highlights
Define variant models containing variants, variation
points and constraints
Centrally model and manage variant configurations
Define relationships between variants and develop-
ment data
Import and export variant models
Application Areas
SYNECT Variant Management lets you create variant models, modules, e.g., SYNECT Test Management, SYNECT Signal
specify constraints between variants, and define variant & Parameter Management or SYNECT Model Management,
configurations that need to be supported in subsequent you can specify relationships between your data and variants,
development phases. When working with other SYNECT and manage different variants of your data.
Working with SYNECT Variant Management

To manage your variants systematically, you explicitly define The variant model is the basis for defining variant configura-
a variant model which you can use throughout the entire tions, in other words concrete combinations of variants that
development process. This variant model consists of variation need to be supported in your development project.
points, variants, and constraints between variants.
Example of a SYNECT variant model consisting of

variation points, variants, and constraints between
variants.
306
2016

Introduction
Application Fields
User-defined list of variant configurations to be supported in the current project.
Dependencies Between Data and Variants

When working with other SYNECT modules, such as SYNECT is valid for a certain variant only, that a parameter exists
Software
Test Management or SYNECT Signal & Parameter Manage- for a certain variant only, that a parameter has different
ment, you can specify dependencies between your data values for selected variants, or that a model has different
and variants. For example, you can specify that a test case implementations for different variants.
Managing Variants in SYNECT Test Management
Hardware
Variant dependencies in SYNECT Test Management can be to use an existing execution plan to test a specific variant
used when defining test execution plans for a specific vari- configuration, it is easy to identify and exclude tests that
ant configuration. By default, only test cases that apply to are invalid or that do not apply.
the selected variant configuration are displayed. If you want
Engineering
You can specify variant dependencies for your test

cases. For example, to define that a specific test
case applies only to a specific variant.
307
2016

Managing Variants in SYNECT Signal &

Parameter Management
To manage parameters and parameter sets for different different variants. You can then specify and manage different
variants, in SYNECT you can define variant dependencies for parameter values for your variant configurations, and also
parameters. You can specify that a parameter exists only for import and export values for selected variant configurations.
a certain variant or that a parameter has different values for
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 imple-
mentations of a model in SYNECT. Besides documenting the
variant dependencies of implementations, these dependen-
cies can be accessed via the tool automation API to facilitate
variant-dependent configuration of composite models.
Workflow Management
dSPACE offers a SYNECT-based Workflow Management
solution (p. 312) for integrating complex workflows with
a large number of variants (such as in HIL and modeling
scenarios) into the dSPACE tool chain and for automating
them. The solution requires SYNECT Base, SYNECT Variant
Management, and additional software from dSPACE.
308 Workflow Management (see p. 312)

2016

General SYNECT Functionalities
Introduction
Highlights
Database support
Data model customization
User and rights managements
Version management
Automation and openness
Application Fields
Traceability to requirements
Working with configuration management systems
Database Support Data Model Customization

SYNECT supports SQL Server® and Oracle®. For a quick start, SYNECT makes it easy to extend the data model by adding
you can use the free SQL Server Express Edition. custom attributes (which you can also deactivate optionally,
if required). For example, you can define additional attributes
Software
for your test cases: supplier or customer lists, test system
IDs, etc. SYNECT also has convenient functions for import-
ing and exporting data with this customized data model.
User and Rights Management
Hardware
SYNECT provides user and rights management functionality. can restrict access to test project plans according to your
As an administrator, you can define who has what kind of supplier or customer, or provide read-only and export-only
access to a specific project or specific item types. Data access access to specific parameter sets. Authentification can be
can be organized efficiently and securely. For example, you granted based on standard Windows® authentification.
Engineering
Comprehensive user and rights

management.
309
2016

Fine-Grained Version Management

SYNECT gives you the ability to manage different versions A compare functionality enables you to compare different
of items such as test cases, parameters or models. There is versions of the same item, or even of a complete project
also a branching mechanism for creating a new develop- or workspace.
ment branch from an already released version of an item. Comments to element versions can be annotated.
The trunk, branches and versions are displayed graphically.
Example of a version history.
Version compare window.
310
2016

Introduction
Automation and Openness
SYNECT provides an open COM API that enables you to created for different integration scenarios. The languages
automate actions that are usually manual, and also to define currently supported are Python, MATLAB®, Visual Basic for
specific actions such as data imports and exports, report Applications, C++, C#, and Visual Basic.
generation or consistency checks. These actions can also be To enable convenient use of customer-developed features,
accessed by extending the SYNECT user interface, and they it is also possible to extend the SYNECT GUI. You can create
Application Fields
can be triggered by client or server events. Interaction with new ribbons and controls, or extend the context menus
external tools is also possible with this API, via connections of SYNECT items such as test cases, test plans, or models.
Internal interpreter *.py
Programs written Access Run

in C#, Python,
Software
MATLAB®, Access
M scripts,... COM API External interpreter
Traceability to Requirements and Specifications

With SYNECT you can link your data (e.g., test cases, pa- SYNECT helps you analyze the impact of changes in require-
rameters, or models) to requirements. SYNECT is flexible ments by providing an overview of linked objects that might
Hardware
and provides various options for importing requirements. be affected. To navigate between requirements and linked
Excel® and the Requirements Interchange Format (RIF, ReqIf) data, all you need is a mouse click. A special requirements
enable you to import requirements e.g., for IBM Rational® coverage view is available to check if a requirement is cov-
DOORS®, PTC® Integrity, or Microsoft® Team Foundation ered by a test case and if this test case has been executed
Server (TFS). An open Python API lets you build custom- successfully.
ized importers for other requirements formats and tools.
Engineering
Working with Configuration Management Systems
SYNECT supports file-based configuration management
systems like Apache™ Subversion®, PTC® Integrity, or
Microsoft® TFS. You can browse file repositories from within
SYNECT and compare two file versions located in the re-
pository. 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
311
2016

Data Management Software / Workflow Management
Workflow Management
Handling complex workflows including variants
Highlights
SYNECT®-based workflow management solution

Mastering complex systems with multiple variants (HIL,

modeling) by workflow automation and
simple user interactions
Reproduceable and reliable workflows

Easy configuration

Single-user and multi-user scenarios


Workflow Management (WFM), which is based on the data By using Workflow Management, you can achieve repro-
management software SYNECT (p. 292), makes it easy to duceable and reliable workflows even in highly complex
integrate your complex workflows (like the common hard- use cases, and save a great amount of time by workflow
ware-in-the-loop (HIL) scenarios for modeling and control, automation that exactly matches your needs.
including variants) into the dSPACE tool chain and automate Centrally configure all the information necessary to
them. support your workflows in SYNECT
Manage large, highly complex HIL systems with a large
number of variants and multiple software interactions
Quickly and safely adapt your modeling environment
to changes caused by variant configurations
Speed up the reliable configuration of your HIL envi-
ronment for subsequent HIL tests
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.
312
2016

Introduction
Module Overview
Module Description
Workflow Management Configurator SYNECT component for resource management that allows to specify any kind of information

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.
Use of the SYNECT variant model

Application Fields
Management of different variant configurations in variant model subsets

Management of resources in a customized tree

Inheritance of resource values in the variants tree to avoid redundancy

Macro mechanism for easier resource definition

Working directory mechanism to support multiple workstations, multiple user and handling

relative paths
Fine-grained rights management

Special support of configuration management systems

Definition of custom workflows

Starter Select a variant configuration with a very simple graphical user interface and start a custom

workflow (see also p. 314), e.g., to start and set up dSPACE ControlDesk® (p. 120) with the
appropriate experiment for the selected variant configuration.
Software
Modeling Connector Special toolbox in MATLAB® with high-level API

Support
of variants inside ConfigurationDesk such as switch of imported/exported
working views
Connection to the WFM database (SYNECT) to get project, variant and resource information

Support of any kind of Simulink® variant change mechanism such as libraries, configurable

subsystems and replacing placeholder subsystems
Support of the Real-Time Interface (RTI) and ConfigurationDesk® build workflow

Hardware
Order Information

Workflow Management Configurator VBWM_CONFIG_SOL

Starter and Command Line Interface (CLI) APPL_VBWM_WF_SOL

Starter and Command Line Interface (CLI); (local) APPL_VBWM_WF_SOL_LOCAL

Modeling Connector VBWM_MLCON_SOL

Modeling Connector (local) VBWM_MLCON_SOL_LOCAL

Engineering
Relevant Software
Software1) Order Number

Required SYNECT Base (p. 293)
SYNECT_BASE

SYNECT Variant Management1) (p. 306)
SYNECT_VARIANT_MGMT

Optional SYNECT Signal & Parameter Management (p. 299)

SYNECT_PAR_MGMT

SYNECT Model Management (p. 302)
SYNECT_MODEL_MGMT

1)
For editing, it is necessary to have a variant model in SYNECT. 313
2016

Workflow Example
HIL Control and Modeling
Workflow Management (WFM) ideally suits HIL testing sce- easily handle such scenarios. Starting a complete experiment
narios and modeling activities. After configuring complex, is simple: just select the appropriate variant configurations
variant-dependent workflows you can run them with just a in the user interface of Workflow Management and start
few clicks, including automatic overnight preparation of large the workflow. The necessary items such as software tools, ex-
real-time testing applications. As an example: a powertrain periments, models, and parameters – user-specified via API or via
HIL environment with six ECUs and several variants each can Modeling Connector – are then loaded automatically.
lead to more than a million combinations. Now you can
Select variant configuration

Start workflow
Workflow example 1 Workflow example 2
HIL Control Modeling
Workflow Workflow
 Start dSPACE products  Start dSPACE products
Variant Configurations
 Configure products  Configure products

 Load settings  Load settings
Data Data
 Real-time application  Simulink® model
 Configuration files  Parameterization
 Configuration files
File System Configuration Management
Handling complex workflows with Workflow Management.
The workflow to be executed can be chosen

and activated quickly with the Starter module
(p. 313).
314
2016

Variant Handling
Introduction
Variants in SYNECT and Workflow Management
In the HIL and modeling workflows, numerous variants taken into account when executing a workflow.
occur, for example, simulator hardware variants, ECU hard- SYNECT Variant Management (p. 306) provides the vari-
ware variants, model parameters and model parts, HIL con- ant model, while the resource information, i.e., informa-
trol parameters, ECU software parameters and many more. tion connected to the variants, is supplied by Workflow
All these variants can affect the workflows and need to be Management.
Application Fields
Variant Model Resources
Information linked to variants
Information linked to variant
configurations
Information Types
Software
Text
Link to file
Link to folder
Variant Configuration
Definition of valid combinations Flag
Etc.
Hardware
SYNECT Variant Management Workflow Management
Relation between SYNECT Variant Management and Workflow Management.
Engineering
315
2016

Hardware
SCALEXIO Hardware __________________ 318
Single-Board Hardware ________________ 356
Modular Hardware ___________________ 372
Accessories _________________________ 504
Simulator Hardware __________________ 520
MicroLabBox Hardware ________________ 540
MicroAutoBox Hardware _______________ 548
RapidPro Hardware ___________________ 568
ECU Interface Hardware _______________ 592

SCALEXIO / Introduction
SCALEXIO®
Versatile system for HIL simulation
Highlights
High processing power

Maximum flexibility due to extensive I/O features

Unlimited application range

Completely software-configurable

Integrated signal conditioning and FIU

Model integration via Simulink or FMI

Smooth extension of existing HIL systems

Use of virtual ECUs for HIL tests


dSPACE SCALEXIO1) is a very versatile hardware-in-the-loop Support of different workflows and user roles by sepa-
(HIL) simulator that provides highly flexible channels, can be rating I/O configuration, modeling and code generation
extended to any required size and is completely software- Test of different ECU variants and types on a single system
configurable. Its application range covers all test domains, with minimal configuration effort
including the test of electronic control units (ECU) of electric Easily resizable to fit specific test tasks because compo-
drives (p. 327). nent test systems and network systems are both built
Thanks to the SCALEXIO multiprocessing feature, the simula- with the same standardized hardware components and
tor can be coupled with existing SCALEXIO-based or DS100x- connections
processor-board-based systems, allowing users to expand Graphical configuration of channels
their existing test setups to meet growing project needs. Use of virtual ECUs (V-ECUs) (p. 327) for HIL tests if the
real ECU prototype is not available yet
Support of Functional Mock-up Interface (FMI)
Hardware Concept
The SCALEXIO system is standardized and can be reused in The SCALEXIO I/O units are specifically designed for typical
all SCALEXIO system variations. ECU signals and offer:
The core of a SCALEXIO system, the SCALEXIO Process- Local signal preprocessing on I/O boards to relieve the
ing Unit, is based on commercially available components load on the real-time processor
so that the processing technology is always up-to-date. Integrated signal conditioning, as well as converters and
IOCNET, the scalable serial I/O network (p. 323), provides parts of the electrical failure simulation
the internal communication between the real-time proces- Similar installation and configuration processes for all
sor and the I/O boards. units, so very little time is spent on learning
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
318 death. Under all circumstances, you must observe all the safety precautions described in the documentation. Please contact
2016 dSPACE for additional safety-related equipment, such as electrically safe interface cables.

Introduction
System Configuration
Due to the standardized SCALEXIO hardware, the system is retrofitted if required. Hypertac connectors at the front can
easily resizable to fit its test tasks. Additional boards can be be wired according to individual project needs.
FIU & Power Switch Board Digital I/O Board Exchangeable load board
Application Fields
of the MultiCompact I/O unit
Signal Measurement Board
I/O subrack with HighFlex

boards (left) and
MultiCompact unit (right)
Software
Signal Generation Board
SCALEXIO Processing Unit

with IOCNET Link Board
Battery simulation power

supply unit
Bus Board
Hypertac Connector
Hardware
FPGA Board Digital I/O Board Multi-I/O Board
I/O Modul
Engineering
The SCALEXIO system can be equipped with only HighFlex
I/O boards for maximal flexibility (left) or can even be used as
a pure I/O device that is connected to an external processing
unit via IOCNET (below, engineering is needed).
319
2016

Hardware-in-the-Loop Function
In
Number of channels
Digital Pulse Capture

Hardware Function and
Triggered Current In
Injection/Ignition
Injection/Ignition
Injection/Ignition
I/O Channel Overview
Voltage Signal
Current Signal
PWM/PFM In
Multi Bit In
Voltage In
Voltage In
Current In
Current In
Extension
Capture
Capture
SENT In
The table on this and
DS2680 Analog In 1 20   
the following page
provides an overview (p. 330) Analog In 2 2
In
of the input and Digital In 1 30    
output functions each
Flexible In 2 18          
SCALEXIO hardware
offers. Analog Out 1 15
Analog Out 2 2
Analog Out 3 7
Out
Analog Out 4 8
Digital Out 1 28
Resistance Out 1 12
Power Switch 2 6 Power Switch
DS2672 Bus 6 CAN, LIN, FlexRay (2 channels each)
DS2690 Digital In 2 10  
In
(p. 333)
Out Out
Digital Out 2 10
Hardware-in-the-Loop Channel
Digital In/Out 1 10  
In/
DS2601
(p. 342)
Flexible In 1 10            
In
DS2621
(p. 344)
Out
Flexible Out 1 10
DS2671
(p. 348) Bus 1 4 CAN, LIN, FlexRay, UART
DS2642
(p. 346) Power Switch 1 10 Power Switch
DS6101 Analog In 4 10   
(p. 338) Analog In 5 1
In
Digital In 3 12    
Flexible In 3 10        
Analog Out 6 8
Analog Out 7 1
Analog Out 8 3
Out
Analog Out 9 4
Digital Out 3 14
Resistance Out 2 6
320 DS6201
In/Out
2016 (p. 340) Digital In/Out 3 96  



Current Sink



Voltage Out
 





Multi Bit Out


Power Switch
Power Switch


Potentiometer Out



Resistance Out

CAN, LIN, FlexRay, UART




PWM/PFM Out


Wavetable Current



Sink
CAN, LIN, FlexRay (2 channels each)



Wavetable Digital Out
Wavetable Voltage







Out
Digital Incremental



Encoder Out


Wheel Speed Out
Out
Waveform Current
 


Sink
Waveform Voltage







Out



Waveform Digital Out
Hardware-in-the-Loop Function
Crank/Cam Current



Sink
Crank/Cam Digital



Out
Crank/Cam Voltage







Out


Knock Signal Out




Lambda DCR



Lambda NCCR



Lambda ADCR




SENT Out

2016
321
Support and Maintenance Engineering Hardware Software Application Fields Introduction
SCALEXIO I/O Hardware

The SCALEXIO I/O hardware comprises three hardware types, They have the following in common:
each specially designed for typical application needs. Local signal preprocessing on I/O boards to relieve the
MultiCompact, HighFlex and SCALEXIO I/O hardware can load on the real-time processor
be combined and extended to produce whatever system Connection to the processing unit via an IOCNET interface
configuration you want. Completely software-configurable
Similar installation and configuration processes, so very
little time is spent on learning
MultiCompact
Large number of I/O channels for specific applications

Each channel has a fixed channel type, so the costs per channel are low.

Integrated signal conditioning and converters

Onboard failure insertion unit (FIU)

Connection of real and substitute loads is possible.

DS2680 I/O Unit (p. 330)

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

DS2690 Digital I/O Board (p. 333)

Standardized connector for slot independence and easy assembly

Digital channels with dedicated I/O functions

HighFlex
Universal input/output/bus channels with freely assignable channel types

Very versatile and finely scalable with 10 channels per I/O board, 4 channels per bus board

Each channel is individually galvanically isolated.

Integrated signal conditioning, as well as converters

Onboard failure insertion unit (FIU)

Connection of real and substitute loads is possible.

Standardized connector concept for all boards

Boards are slot-independent and easy to assemble.

DS2601 Signal Measurement Board (p. 342)

DS2621 Signal Generation Board (p. 344)

DS2642 FIU & Power Switch Board (p. 346)

DS2671 Bus Board (p. 348)

SCALEXIO I/O Boards

Large number of I/O channels with dedicated channel types

Focus on I/O functions without current-related functionality

No onboard failure insertion unit (FIU)

No connection of real or substitute loads

Connection to I/O via Sub-D connector

Boards are slot-independent and easy to assemble

DS6101 Multi-I/O Board (p. 338)

DS6201 Digital I/O Board (p. 340)

DS2655 FPGA Base Board (p. 335)

322
2016

Introduction
IOCNET (I/O Carrier Network)
IOCNET is a network technology developed by dSPACE for Coupling Several Processors
internal simulator communication based on the Gigabit IOCNET also couples processors, and no additional hard-
Ethernet physical layer. A SCALEXIO system with IOCNET ware is necessary.
comprises more than 100 device nodes, which can be
located up to 100 meters apart. The transmission rate is Coupling SCALEXIO with Existing Systems
about 10 times higher than with peripheral high-speed The SCALEXIO system can interact with all dSPACE HIL sys-
Application Fields
(PHS) bus-based technology, and input signals can be read tems, such as dSPACE Simulator Mid-Size and dSPACE Simu-
synchronously. lator Full-Size. These are based on the PHS bus technology,
You can also use decentralized I/O, in other words, I/O units which is used for communication between the processor
without their own processing units. and the I/O units. A SCALEXIO system is connected to a
PHS system by processor-to-processor coupling with an
IOCNET Gigalink connection.
TCP/IP
Host
Software
Gigalink
IOCNET
Processor IOCNET DS100x Gigalink
I/O Subrack PHS I/O Board

Processor IOCNET
IOCNET
I/O Subrack PHS
I/O Subrack I/O Subrack PHS I/O Board

Router Router
Hardware
I/O Board I/O Board
I/O Subrack
I/O Board I/O Board Router
IOCNET
I/O Board I/O Board I/O Board
I/O Board I/O Board I/O Board

.. .. ..
. . .
Engineering
FIU/PowerSwitch FIU/PowerSwitch FIU/PowerSwitch
323
2016

Failure Simulation
Hardware Components
The SCALEXIO Failure Insertion Unit (FIU) consists of several The central FIU is located on either the DS2642 FIU &

components: Power Switch Board or the DS2680 I/O Unit. The central
An onboard failure routing unit (FRU) on the I/O channels FIU uses semiconductor switches for switching the failures.
prepares failure simulation by switching the I/O channels It switches very fast (pulsed switching), which makes it
to failrails. The FRU is available for each channel on the possible to simulate loose contacts or insert faults for a
MultiCompact and HighFlex boards and uses relays to very precise duration.
provide the features of the central failure simulation unit The failrail segment switch is used to switch selected

to each channel. segments into the failrails for failure simulation. This way,
Depending on their properties, the channels are con- the conducting capacity can be minimized to avoid signal
nected to the failure simulation system by the high-current corruption, even for large simulation systems that have
(up to 80 A) or the low-capacitance (up to 1 A) failrail. a high number of inputs/outputs or that are distributed
The low-capacitance failrail for an optimized signal quality across several cabinets.
connects signal generation channels and bus channels to
the central FIU. The high-current failrail connects signal
measurement channels to the central FIU.
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  –
1)
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 failrail.
License Concept Tracing FIU States

The SCALEXIO HighFlex and MultiCompact boards include The diagnostic functions of ECUs have to detect each failure
a failure simulation (FS) function. You need an additional within a specified time. To help test an ECU’s diagnostic
FS license to activate the failure simulation. The FS license functions, SCALEXIO provides FIU state tracing. This enables
will be checked at the host PC. Each license can be used you to measure or plot FIU states and therefore to monitor
for one SCALEXIO system. the time from a change in FIU state to any other event, such
The licenses are scaled for failure simulation with different as the detection of the failure.
numbers of I/O channels capable of failure simulations.
The failure simulation is configured in ConfigurationDesk, Multiple Failures
so you need the appropriate SCALEXIO failure simulation SCALEXIO supports the simultaneous insertion of multiple
license for the number of I/O functions that are mapped failures during simulation to allow failure classes such as
to channels with an FRU that you use in your real-time broken wire, short circuit to ground or UBAT, or short between
application. The FS license is needed only for running channels. This function can be enabled in ConfigurationDesk
the simulation, not for configuring the I/O channels with for channels without current enhancement.
ConfigurationDesk.
324
2016

Introduction
SCALEXIO
DS2671
Bus Board
DS2621
Signal Generation
failrail
Application Fields
Board
DS2601
Signal Measurement
Board
DS2642
FIU & Power Switch DS2908
Board Failrail
ECU connection
Segment
I/O unit Switch
failrail
Low- High-
capacitance current
failrail failrail
DS2908
DS2671 Failrail
Bus Board Segment
Software
Switch
another HIL system

DS2621
Signal Generation
failrail
Connection to
Board
DS2601 DS2908
Signal Measurement Failrail
Board Segment
DS2642 Battery Switch
FIU & Power Switch
Board
power
supply
I/O unit unit
Hardware
The SCALEXIO FIU concept with an example selection of HighFlex I/O boards.
Order Information

SCALEXIO Failure Simulation SCLX_FS_100 (for 100 functions)

Engineering



SCLX_FS_UNLTD (for an unlimited number of functions)

325
2016

Power Supply Control for Battery Simulation

With the SCALEXIO system, the battery simulation can be In the DS2680 I/O Unit (p. 330), the control for the power
addressed from directly within the simulation model. No supply and the power switch are already integrated.
additional I/O is needed. The battery simulation consists of
three components: You can read out and check the latest current and voltage
Battery simulation controller (e.g., DS2907 Battery values at any time during simulation. The voltage behavior
Simulation Controller, p. 350) to control the power is specified in the model.
supply unit by current and voltage values
Power supply unit to generate current and voltage
A switch for the power supply to the ECU (e.g.,
DS2642 FIU & Power Switch Board, p. 346)
Controls SCALEXIO® System

Battery simulation current and
voltage
controller supply
(e.g., DS2907) Switches the
power supply
to the ECU
Switch for power

Power supply unit
supply (e.g., DS2642)
ECU
Configuration Software
ConfigurationDesk® (p. 48) is the configuration and imple- ConfigurationDesk supports the open Functional Mock-up
mentation software for SCALEXIO and intensifies the sys- Interface (FMI) standard (p. 25). This enables the users to use
tem's flexibility. You can perform all configuration tasks in different modeling approaches by using functional mock-
a single tool, in an easy-to-read 3-column window: up units (FMUs). In HIL projects, FMUs can be integrated
Describing the connected devices together with V-ECUs (p. 327) and Simulink® models.
Assigning I/O functions and hardware
Connecting to the model
dSPACE Engineering Services

You can make use of dSPACE Engineering Services (p. 608) know-how. These will help you get the maximum benefit
in any project phase. Whether you need engineering support from the system's flexibility for your projects. For example,
for an entire project or just for system installation or first use, all the I/O units contain FPGAs whose microcode machines
you can rely on our years of experience and comprehensive we can program for project-specific I/O functions.
326
2016

Introduction
Special Applications
Tests for Electric Motors
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. 335)
with a freely programmable FPGA and a high level of I/O.
Application Fields
Used in combination with the XSG Electric Components
Library (p. 271), 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.
You can also connect electronic load modules to the
SCALEXIO system to inject real phase currents into power SCALEXIO emulates electric motors together with the Electronic Load
electronics test devices. Module and DS2655 FPGA Base Board.
Software
HIL Simulation with Virtual ECUs
Hardware
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.
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.
Engineering
For using a V-ECU during HIL simulation, a SCALEXIO Real-
Time license is needed (p. 329).
To configure V-ECUs, you can integrate them into a real-
time application in ConfigurationDesk (p. 48) just like any The generation of VECUs is based on AUTOSARcompliant ECU
other behavior model. software development.
327
2016

SCALEXIO / Processing Unit
SCALEXIO Processing Unit

The newest processor technology
Highlights
x86 processor technology Intel XEON E3

High bandwidth for I/O communication

via IOCNET
SCALEXIO connectable to DS100x-based HIL

systems (via Gigalink)
Multiprocessor support

The SCALEXIO Processing Unit is based on an industrial updated regularly to benefit from performance improve-
PC with an Intel XEON E3 quad-core processor, a real-time ments in processor technology.
operating system (RTOS), and a PCIe plug-on card developed To ensure communication between the real-time applica-
by dSPACE for communication with the I/O and with other tion running on the processor and the I/O, dSPACE offers
real-time processors. Because the processor and mother- the SCALEXIO Real-Time Library that is based on the QNX®
board components are standard components, they can be real-time operating system.
Processing
Unit The IOCNET Link Board connects the
Real-time IOCNET
Host processor Link Board IOCNET/ realtime processor to the SCALEXIO
PCI Express
interface Gigalink I/O. The Ethernet host interface is
connected to the service core of the
realtime processor.
Multicore Support for Large Models IOCNET

Large, complex simulation models can be distributed across SCALEXIO's communication network IOCNET (I/O Carrier
three processor cores instead of one to ensure that they can Network) uses a proprietary dSPACE protocol to guarantee
be computed in real time. The fourth core is reserved for the simulator's real-time capability. It is the interface to
internal system services. A configuration software is used the I/O boards and SCALEXIO processing units, providing a
to distribute model parts to the cores and to configure the flexible network topology and high bandwidth to connect
communication behavior, the simulation hardware and the a large number of I/O boards, even when they are far apart
model connections (see ConfigurationDesk, p. 48). (p. 323).
Large Test Systems via Multiprocessor Support

With the multiprocessor support for SCALEXIO, two or systems can be coupled to processing units via IOCNET.
more SCALEXIO systems can be coupled to increase com- To ensure convenient modeling, you still have just one overall
putational power. To provide large bandwidths, SCALEXIO project in ConfigurationDesk.
328
2016

SCALEXIO / Processing Unit
Introduction
IOCNET Link Board Host PC Interface
The DS2502 IOCNET Link Board is used to connect I/O units Communication with the host PC runs via Gigabit Ethernet,
or couple the SCALEXIO with other dSPACE HIL simulator so that the SCALEXIO system can be used in any company
systems. It is available in two versions: one with 4 and one network. When more than two SCALEXIO Processing Units
with 8 IOCNET connectors. are used, they are coupled via the SCALEXIO MP Switch to
The DS2502 also has angular processing unit (APU) func- ensure communication with the host PC. The IP address for
Application Fields
tionality for highly precise angle-based simulation, for ex- the connection can be assigned via a DHCP server or stored
ample, to measure injection and ignition signals. Up to six on the SCALEXIO system itself.
independent APUs can be used.
Technical Details
Parameter Specification
Processor Intel XEON E3-1275v3 with 3.5 GHz

Memory L1 cache: 32 + 32 kB (data + instructions)

Software
L2 cache: 256 kB

L3 cache: 8 MB

4 GB RAM memory (DDR3)

Angular processing unit (APU) 6 APUs on the DS2502 IOCNET Link Board

Angular resolution 0.011°

Speed range ± 28,610 rpm

Speed resolution 0.109 rpm

Interfaces for I/O boards 4
or 8 IOCNET connectors on the DS2502 IOCNET Link Board (optionally usable
as Gigalink connectors)
Host interface Gigabit Ethernet

Hardware
Physical data Physical size 19-inch subrack

3 HU

483 x 133 x 400 mm (19.0 x 5.2 x 15.7 in)

Cooling Active cooling

Operating temperature 0 °C ... 40 °C (32 °F ... 104 °F)

Voltage supply 100 ... 240 V AC, 50/60 Hz

Order Information
Engineering
SCALEXIO Real-Time Library SCLX_RTLib

SCALEXIO Real-Time Library for Multicore Systems SCLX_RTLib_MC

SCALEXIO Real-Time Library for Multiprocessor Systems SCLX_RTLib_MP

SCALEXIO Real-Time Library for virtual ECUs SCLX_RTLib_VECU


SCALEXIO Real-Time PC (Rack-Mount Version) SCLX_RTPC_RACK E31275

Please inquire if you use a SCALEXIO Real-Time PC with another processor

DS2502 IOCNET Link Board DS2502_4P (with 4 IOCNET connectors)

DS2502_8P (with 8 IOCNET connectors)

SCALEXIO MP Switch SCLX_SWITCH SG300_10

Relevant Software
Product 329
Required ConfigurationDesk (p. 48) 2016

SCALEXIO / DS2680 I/O Unit
DS2680 I/O Unit

MultiCompact unit for powertrain and vehicle dynamics scenarios
Highlights
140 channels for extensive I/O functions

Galvanically isolated as a unit

Compact half 19" unit

Attractive price

The DS2680 I/O Unit is a MultiCompact unit for the function, i.e., they are dedicated analog or digital channels.
SCALEXIO system that provides all the I/O channels required With its predefined channels, the DS2680 has an attractive
for the hardware-in-the-loop simulation of transmission or price, and is ideal for specific application scenarios.
vehicle dynamics ECUs. Most of the I/O channels have a fixed
I/O Functionality Testing Electrical Failures

The DS2680 has numerous I/O channels, each with a mostly The DS2680 includes a Failure Insertion Unit (FIU) for testing
predefined function. You can choose between analog and ECU behavior in the event of a failure. It can be used as a
digital inputs and outputs, resistance simulation channels, central FIU for the SCALEXIO system. Each channel has a
and special I/O channels. Signal measurement and genera- failure routing unit (FRU) for switching the connection to
tion can be time-triggered or angle-triggered. the FIU via the fail rails. For further information, please refer
to Failure Simulation on p. 324.
Real Loads Component Variants

Substitute loads can be plugged onto the DS2680 internally The DS2680 is available with and without an integrated
if required. An exchangeable load board is available for bus board. The integrated bus board provides two channels
you to mount different plug-on loads. Real loads or large for each of the bus protocols LIN, CAN and FlexRay. If you
substitute loads can be connected externally via the load need more or different bus channels, for example, four CAN
connector provided for them. channels, you can use a HighFlex bus board in addition or
as an alternative.
330
2016

Introduction
Technical Details
Parameters Specification
Signal measurement Max. 6 A per channel

Substitute loads pluggable, up to 2 W per measurement channel

Connector for real loads

Application Fields
Channel bundling to increase current carrying capacity

Multifuse for electrical safety

20 analog inputs
Only voltage measurement

(Analog In 1) Measurement range 0 ... 60 V

Resolution 16 bit

30 digital inputs
Voltage measurement

(Digital In 1) Trigger value 0 ... 24 V

Voltage range 0 ... 60 V

18 variable inputs
Voltage measurement digital

(Flexible In 2) Voltage range 0 ... 60 V

Trigger value 0 ... 24 V

Current measurement analog and digital

Software
Measurement range ±18 A

Resolution 16 bit (analog)

Signal generation 15 analog outputs (DC)
Only voltage generation

(Analog Out 1) Output voltage 0 ... 10 V

Output current -5 ... +5 mA

Resolution 14 bit

8 analog outputs (DC)
Output voltage 0 ... 10 V

(Analog Out 4) Output current -5 ... +5 mA

Resolution 14 bit

Current sink: Current range -30 ... +30 mA


Hardware
(Analog Out 3) Output voltage -20 ... +20 V

Resolution 14 bit

Effective inner resistance 250 Ω

12 resistance simulation channels
Resistance range 16 Ω ... 1 MΩ

(Resistance Out 1) Voltage range -3 ... +18 V to GND

Current range -80 ... +80 mA

Power max. 250 mW

28 digital outputs
Configurable as low-side/high-side switch or push/pull

(Digital Out 1) Low-side = GND

High-Side VBAT or Dig-Out-Ref

High-side voltage range: 5 ... 60 V
Engineering


Special I/O channels 2 analog input and output groups,
1 ADC

e.g., for lambda probe simulation 1 DAC

(Analog In 2, Analog Out 2, Load 1) 1 load (component channel)

Voltage range -10 ... +10 V


Voltage supply 1 channel to control the power unit
Control of TDK-Lambda GenesysTM power supply

(Power Control 1)
6 power switches without current

Up to 60 V

measurement (Power Switch 2) Continuous current 4 x 6 A per channel (but a maximum total of 50 A for all channels)

331
2016

Buses 1)
2 CAN (CAN 1)
Configurable as high-speed or low-speed CAN

Conventional CAN VBAT

2 LIN (LIN 1)
Configurable as K-Line

Conventional LIN VBAT

2 FlexRay (FlexRay 1)
Only 4 bus lines, i.e., 1 fault-tolerant FlexRay bus (channels A + B) or 2 FlexRay buses

(channel A)
Conventional FlexRay VBAT

Failure Insertion Unit General Voltage ±60 V

Failure switch for up to 48 A

Continuous current for high-current fail rail 48 A

Continuous current fail rail with low capacitance 1 A

Failure types Broken wire

Short circuit to GND or UBAT

Crossed wire between two channels

All failures with optional bouncing

Internal communication interface IOCNET

Physical data Physical size 475 x 132 x 215 mm (18.7 x 5.2 x 8.5 in)

Voltage supply 24 V

Only for DS2680 with bus support

1)
Order Information

DS2680 I/O Unit (without bus support) DS2680_ONLY

DS2680 I/O Unit (with bus support) DS2680_2672

Additional Hardware DS2680-IL Load Board (exchangeable load board) DS2680_IL

OBD to Sub-D Adapter Cable SCLX_OBD_CAB1

Relevant Software
Product
Required ConfigurationDesk (p. 48)
Optional for DS2680 I/O Unit with bus support RTI CAN MultiMessage Blockset (p. 74)
NEW: Bus Manager (p. 54)
332
2016

SCALEXIO / DS2690 Digital I/O Board
DS2690 Digital I/O Board
Introduction
MultiCompact board for vehicle body scenarios
Highlights
Application Fields
Large number of digital I/O channels

Signal measurement or generation

Connection of real loads

Seamless integration into SCALEXIO FIU concept

Attractive price

Software
The DS2690 Digital I/O Board is the tailored SCALEXIO solu- The DS2690 offers a large number of dedicated digital I/O
tion for hardware-in-the-loop (HIL) simulation of body elec- channels for signal generation and measurement. Their
tronics ECUs. Vehicle body applications such as electric win- supported I/O functionalities cover exactly the ones needed
dow lift and windscreen wipers require many high-current for body electronic ECUs. Real loads can be connected to
digital I/O channels, as well as the ability to simulate failures. each channel individually.
An on-board failure routing unit (FRU) enables failure simu-
lation on all channels. For further information on the fail-
Hardware
ure simulation function, please refer to Failure Simulation
on p. 324.
I/O Functionality
The DS2690 offers digital channels that are either predefined IOCNET connector I/O connector
for signal measurement or signal generation, or can be indi-
vidually configured for either. Channels for signal measure-
Engineering
Fuse Fuse
ment and generation are usable as Digital In, PWM In or
Digital Out, PWM Out. FRU
The signal types and channel bundling are configured with
Controller Internal load
ConfigurationDesk (p. 48).
I/O
Real Loads for Real Currents ...
Testing ECUs under realistic circumstances sometimes

requires real currents, so real loads can be connected Digital Digital

In Out
externally. Substitute loads are available internally as well.
PWM PWM
Status LED In Out
333
2016

Technical Details
General Multifuse for electrical safety

Channels bundling to increase the continuous current

Signal measurement 10 channels

(Digital In 2) Supported I/O functions

Multi Bit In

PWM/PFM In

Measurement range 0 ... 60 V

Max. 6 A per channel


Real loads can be wired externally

FIU via high-current failrail

Signal generation 10 channels

(Digital Out 2) Supported I/O functions

Multi Bit Out

PWM/PFM Out


Low-side = GND

High-side = external reference for each channel

Voltage range high-side: 5 ... 60 V


FIU via low-capacitance failrail

Signal measurement or generation 10 channels

(Digital In/Out 1) Supported I/O functions

Multi Bit In

PWM/PFM In

Multi Bit Out

PWM/PFM Out

FIU via low-capacitance failrail

Digital In Measurement range 0 ... 60 V

Max. 100 mA per channel


Real loads can be wired externally

Digital Out Configurable as low-side/high-side switch or push/pull

Low-side = GND

High-side = external reference for each channel



Failure simulation On-board failure routing unit (FRU)

Signal forwarding to central FIU

Based on relays

Available for each channel



Requires 3 slots

Voltage supply 24 V

Order Information

DS2690 Digital I/O Board DS2690

Relevant Software
Product
334
2016

SCALEXIO / DS2655 FPGA Base Board
DS2655 FPGA Base Board
Introduction
HighFlex board with userprogrammable FPGA
Highlights
Application Fields

Flexible board for special I/O solutions

Up to 5 piggyback modules for I/O can be added

Software
The DS2655 FPGA Base Board has been designed for ap- The DS2655 includes a powerful, freely programmable field-
plications that require very fast, high-resolution signal pro- programmable gate array (FPGA), the Xilinx® Kintex®-7 160T.
cessing, for example: To include I/O channels, you connect up to five I/O modules
Hybrid vehicle applications to the board.
Electric drive applications Together with dSPACE electronic load modules and/or the
Wind energy converters XSG Electric Components Library (p. 271), the DS2655 pro-
Processor-based motor simulation vides the fast reaction times required for simulating electrical
Hardware
FPGA-based motor simulation machines in closed-loop operation with a controller.
Protocols
DS2655 I/O Modules

Programming the FPGA
Programs for the DS2655 FPGA Base Board's FPGA are pro- For expanding the I/O channels of the DS2655 there are
grammed with the RTI FPGA Programming Blockset and with two I/O modules available: the DS2655M1 Multi-I/O Module
Engineering
XSG-based solutions. The programs are downloaded to the and the DS2655M2 Digital I/O Module. They provide a high
FPGA via dSPACE ConfigurationDesk (p. 48). number of the digital and analog I/O channels needed for
You can test the program in offline simulation before imple- applications such as electric drives, for example.
menting it on the real-time hardware. This enables you to For more information, please see the tables on page 337.
react flexibly to new requirements, such as new interfaces
or having to accelerate the execution of submodels.
335
2016

Technical Details DS2655

General User-programmable FPGA

FPGA 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 5

Device timing 125 MHz


Physical characteristics Physical size 100 x 18 x 210 mm ( 3.9 x 0.7 x 8.3 in)

Power supply 24 V

Order Information

Required DS2655 FPGA Base Board DS2655 7K160
Optional DS2655M1 Multi-I/O Module DS2655_M1
DS2655M2 Digital I/O Module DS2655_M2
Adapter for two Sub-D 50 connectors to one Hypertac connector HYPERTRONICS_CON90_FP1_QT
Relevant Software
Product
Required RTI FPGA Programming Blockset (p. 90)
Optional XSG Electric Components Library (p. 271)
XSG Utils Library (p. 104)
XSG AC Motor Control Library (p. 106)
336
2016

Introduction
Technical Details DS2655M1
Digital I/O 10 channels, usable as input or output

Input Maximum input voltage: 15 V

Threshold for each channel adjustable from 1 V to 7.5 V

Output Push-pull drivers
One output voltage can be selected for all channels: 3.3 V or 5 V
Analog I/O Input 5 channels
Application Fields

Resolution 14 bit

Sampling rate 4 MSPS SAR

Input voltage range selectable for each channel: ±5 V or ±30 V

Output 5 channels

Resolution 14 bit

Update rate 7.8 MSPS

Output voltage range: ±10 V

Physical Physical size 208 x 100 x 18 mm (8.2 x 3.9 x 0.7 in)

characteristics Power supply 24 V

Software
Technical Details DS2655M2


Threshold for each channel adjustable form 1 V to 7.5 V

Hardware
UART 16 channels extended with RS232/RS485 transceivers

RS232: max. 250 kBaud

RS485: max. 40 MBaud

Configuration Maximal configuration of the functions 32 x digital input

32 x digital output, (push/pull or push or pull)

16 x digital output, (push/pull/tristate)

8 x RS232 RX, (24 digital I/O or 8 x RS232 TX channels are free)

8 x RS232 TX, (24 digital I/O or 8 x RS232 RX channels are free)

8 x RS485 RX, (16 digital I/O channels are free)

8 x RS485 TX, (16 digital I/O channels are free)

8 x RS485 RX/TX, (8 digital I/O channels are free)

Engineering

characteristics Power supply 24 V
337
2016

SCALEXIO / DS6101 MultiI/O Board
DS6101 MultiI/O Board

I/O hardware with signal conditioning for automotive systems
Highlights
69 channels for comprehensive I/O functions

Signal conditioning for signal levels of 12-V, 24-V,

and 48-V automotive systems
Ideally suited for engine, powertrains, and vehicle dy-

namic applications

The DS6101 comprises a large variety of I/O functions need- The DS6101 Multi-I/O Board offers 69 I/O channels for volt-
ed for hardware-in-the-loop simulation and can be used age-related functions, including analog, digital, resistance,
for generating and measuring typical automotive signals. and special input/output groups, for example for lambda
This makes the DS6101 ideally suited for applications with probe simulation.
extensive I/O requirements. The integrated signal conditioning is tailored to automo-
For failure simulation, you can connect additional hardware tive project requirements, such as voltages of 12 V, 24 V,
to your system. The same holds true for bus communication. and 48 V.
There you can use the DS2671 Bus Board.
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.
338
2016

SCALEXIO / DS6101 Multi-I/O Board
Introduction
Technical Details
General All I/O channels are software-configurable

3 x 50-pin Sub-D connectors

Signal Measurement 10 analog inputs
Voltage measurement range 0 ... 60 V

Application Fields
(Analog In 4) Resolution 16 bit

12 digital inputs
Voltage measurement range 0 ... 60 V

(Digital In 3)
10 variable inputs
Voltage measurement digital

(Flexible In 3) Voltage range -10 ... 10 V

Fast threshold adaptation (useful for ignition/injection signal measurement)

Voltage measurement analog

Voltage range -10 ... 10 V

Resolution 16 bit

Signal generation 8 analog outputs (DC)

(Analog Out 6) Output voltage 0 ... 10 V

Output current -5 ... +5 mA

Software
Resolution 14 bit


(Analog Out 9) Output current -5 ... +5 mA

Resolution 14 bit

Current sink: Current range -30 ... +30 mA

3 analog outputs (AC)

(Analog Out 8) Output voltage -20 ... +20 V

Resolution 14 bit

6 resistance simulation channels
Effective inner resistance range 16 Ω ... 1 MΩ

(Resistance Out 2) Voltage range -3 ... +18 V to GND


Hardware
Power max. 250 mW

14 digital outputs

(Digital Out 3) Low-side = GND

High-side Dig-Out-Ref 1 or 2


Current range 0 ... ±150 mA

150 mA per channel and 1 A in sum per group

Special I/O channels 1 analog input and output group,
1 ADC, 12 bit

e.g., for lambda probe simulation 1 DAC, 14 bit

(Analog In 4, Analog Out 7) Voltage range -10 ... +10 V

Engineering



Requires 3 slots

Voltage supply 24 V

Order Information
DS6101 DS6101

Relevant Software
Product
Required ConfigurationDesk (p. 48) 339
2016


SCALEXIO I/O board with 96 bidirectional digital I/O channels
Highlights
96 channels for high I/O requirements

Signal conditioning up to 60 V

Measures and generates automotive signals and

TLL signals
All channels configurable as input or output

Software-configurable channels


The DS6201 Digital I/O Board comprises a large number of The DS6201 Digital I/O Board offers 96 I/O channels for sig-
digital I/O channels that can all be configured as input or nal measurement and signal generation. The onboard signal
output channels. The available I/O functions cover digital, conditioning is tailored to automotive project requirements,
PWM, and PFM functions for hardware-in-the-loop simula- such as voltages of 12 V, 24 V, 36 V, and 48 V, as well as to
tion in automotive projects, such as the test of body elec- customary TLL levels.
tronics ECUs.
Additionally the DS6201 includes an onboard signal con-
ditioning unit. This makes the DS6201 a cost-efficient way
to start a HIL simulation project.
I/O Functionality
The 96 digital channels of the DS6201 can be configured
for signal measurement or signal generation. They can be
used as
Multi Bit In or Out
PWM In or Out
PFM In or Out
The channels are software-configurable and are defined and

configured graphically in the dSPACE ConfigurationDesk®
software.
340
2016

Introduction
Technical Details
General Supported I/O functions

Multi Bit In

PWM/PFM In

Application Fields
Multi Bit Out

PWM/PFM Out

3 x 50-pin Sub-D connectors

Digital signal measurement Digital inputs
Measurement range 0 ... 60 V

or generation Digital outputs

(Digital In/Out 3) Low-side = GND

High-side
= 2 independent external high-side references per group (Sub-D connector /
32 channels)
Voltage range high-side: 3.3 ... 60 V

Current max. 150 mA

150 mA per channel and 2 A in sum per group


Software

Requires 3 slots

Voltage supply 24 V

Order Information

DS6201 DS6201


Hardware
Relevant Software
Product
Engineering
341
2016

SCALEXIO / DS2601 Signal Measurement Board
DS2601 Signal Measurement Board

HighFlex board for measuring ECU output signals
Highlights
Current and voltage measurement

Channel bundling to increase current carrying capacity

Configurable fuses

Onboard failure routing unit

Onboard loads or external loads via 2nd connector

Galvanically isolated channels

Application Area
The DS2601 Signal Measurement Board measures ECU out- For information on the failure simulation function, see
put signals and passes the measurement values to the real- Failure Simulation on p. 324.
time processor. Signal measurement can be time-triggered
or event-triggered, and the execution of signal measurement
can be voltage- or current-triggered.
I/O Functionality
The DS2601 has 10 flexibly configurable input channels, onto the board itself or connect real loads via a cable har-
which can connect analog (analog-digital converter) and ness to the externally accessible load connector.
also digital (comparator) measurement units
to measure the current and voltage. For
example, the measurement units can be com- IOCNET interface I/O connector Load connector
bined to trigger analog current measurement
if a specified voltage is exceeded. The channels DC
are defined and configured in the Configura- DC
tionDesk® software.
Fuse
The 10 channels on the DS2601 can be con-
FRU
nected in parallel. This channel bundling Controller
Fuse Analog-
increases the current-carrying capacity up to Voltage
measurement
digital
Measurement converter
80 A (RMS). ConfigurationDesk displays the circuit
Current Comparator
bundled channels as one single I/O function. Internal load measurement
The DS2601 supports the use of loads for the Status LED LED 1
...
10
ECU. You can either plug substitute loads
342
2016

SCALEXIO / DS2601 Signal Measurement Board
Introduction
Technical Details
General 10 galvanically isolated channels for signal measurement

Load connections for plugging loads of up to 2 W on the board

External load connection (for real loads or substitute loads > 2 W)

Application Fields
Up to 10 channels connected in parallel to increase the continuous current to max. 80 A

Status LED for overall board status

10 channel-specific LEDs to indicate channel voltage

Electrical capacity Voltage ±60 V per channel

Continuous current ±10 A per channel

Maximum continuous current of 80 A when all 10 channels bundled

Signal measurement Adjustable digital filtering for analog measurements

(Flexible In 1) Current/voltage measurement: Sampling rate up to 250 kHz

Voltage measurement Voltage measurement ±60 V per channel

Voltage, analog and digital (settable trigger value)

ADC resolution 16 bit

Current measurement Current measurement ±30 A per channel

Software
Current measurement, analog and digital (settable trigger value)

ADC resolution 16 bit

Trigger Time-, angle- and event-driven signal measurement

Voltage-driven current measurement

Control from within the model

Failure simulation Onboard failure routing unit (FRU)


Relay-based


Electronic fuses Software-configurable and software-resettable

Fuse trip settable 0.5 ... 10 Aeff

Hardware


Requires 2 slots

Voltage supply 24 V

Order Information
Engineering
DS2601 Signal Measurement Board DS2601

Relevant Software
Product
343
2016

SCALEXIO / DS2621 Signal Generation Board
DS2621 Signal Generation Board

HighFlex I/O board for simulating ECU input signals
Highlights
Signal generation for simulating voltage, current,

resistance and switches
Channel bundling to increase output voltage


Galvanically isolated channels

Application Area
The DS2621 Signal Generation Board stimulates ECU inputs. For information on the failure simulation function, please
It mimics sensors or switches such as door contact switches, refer to Failure Simulation on p. 324.
Hall sensors, and sensors for wheel speed and oil tempera-
ture. Each of the DS2621's 10 channels can be software-
configured 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
IOCNET connection I/O connector
to make analog and digital signal generators available. To
increase the current or voltage range, up to 10 channels can DC Current sink
be bundled in parallel or in series. For example, two voltage DC
Voltage
sources can be switched in sequence, or two current sinks in source
Fuse
parallel, to increase the output voltage or current. The digital
FRU Digital output
output can be used as a switch and can generate time- and Controller
Fuse Resistance
frequency-dependent signals (such as PWM). For example, simulation
Signal generator
the resistance simulation can be used to pass the specified circuits
... 10
1
temperature changes to an ECU via the environment model. Status LED
Channel bundling is supported by the software. Configu-
rationDesk displays the bundled channels as one single I/O
function.
344
2016

SCALEXIO / DS2621 Signal Generation Board
Introduction
Technical Details
General 10 galvanically isolated channels

Up to 10 channels can be connected in sequence or in parallel to increase the current range

to max. ±320 mA and the voltage range to max. ±60 V
Application Fields

Signal generation Voltage source Output voltage ±20 V

(Flexible Out 1) Output current ±40 mA

DAC resolution 16 bit

Signal frequency 0 … 140 kHz (sine)

Current sink Voltage range ±60 V

Current range ±40 mA

DAC resolution 15 bit

Signal frequency 0 ... 140 kHz (sine)

Resistance simulation Resistance range 17.5 Ω ... 1 MΩ

Voltage range ±20 V


Software
Digital output Voltage range ±60 V


Signal frequency 0 ... 1 MHz

Failure simulation Onboard failure routing unit (FRU)


Relay-based


Electronic fuses 100 mA RMS ECU (effective value)

On ECU side tripping at I = 100 mA

On sensor side with configurable trip range I = 5 ... 40 mA


Hardware

Requires 1 slot

Voltage supply 24 V

Order Information

DS2621 Signal Generation Board DS2621

Engineering
Relevant Software
Product
345
2016

SCALEXIO / DS2642 FIU & Power Switch Board
DS2642 FIU & Power Switch Board

HighFlex board for powerswitching with Failure Insertion Unit
Highlights
Central FIU

Switched battery voltage

Failure feedforward

High-precision current measurement on each channel

Application Area
The DS2642 FIU & Power Switch Board combines two com- Power switches for simulating up to 10 switched

ponents: potentials, for example, on terminal K15
Central Failure Insertion Unit (FIU) for simulating failures
for the I/O channels of the SCALEXIO HighFlex boards
and MultiCompact units
Central FIU Power Switch

The central FIU on the DS2642 is connected to the failure The power switch provides 10 switchable channels, which
routing units of the I/O boards via the fail rails. It switches supply current to the external devices such as ECUs and
the failures for the channels on the boards. loads. The current can be measured simultaneously. The
The following options are available: central FIU can also use the power switch channels to simu-
Broken wires on each individual channel, with or with- late short circuits to the supply to the ECU. The channels
out bouncing as selected can be bundled to increase the current, and are selected in
Crossed wire between two channels, with or without ConfigurationDesk®. Several DS2642s can be used in one
bouncing SCALEXIO system.
Short circuit to a fixed potential such as the supply
voltage, with or without bouncing Current Measurement
The power consumption of the connected components
The failures are prepared on the I/O boards by relays, and can be measured precisely on each power switch channel.
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.
For information on the failure simulation function, please
refer to Failure Simulation on p. 324.
346
2016

SCALEXIO / DS2642 FIU & Power Switch Board
Introduction
Technical Details
Power switches (Power Switch 1) General 10 channels for the ECU's current supply

Voltage 60 V

Continuous current 10 A per channel

Application Fields
Channel parallelization to increase the measurement range to max. 80 A (RMS)


10 channel-specific LEDs for channel status (power switch open/closed)

Current Measurement Current measurement on each channel

Precision mode

Resolution 6.25 µA

Sampling time 135 ms

Measurement range 0 ... 1.6 A

Dynamic mode

Resolution 150 µA

Sampling time 262 µs

Measurement range 0 A ... 39 A

Electronic fuses 10 A RMS ECU (effective value)

Software
Software-configurable and software-resettable

Failure Insertion Unit General Voltage ±60 V

Failure switch for up to 80 A

Continuous current for LC fail rail 80 A

Continuous current fail rail with low capacitance 1 A

Status LED for the FIU component

Failure types Broken wire

Short circuit to GND or UBat

Crossed wire between two channels

All failures with optional bouncing

Hardware


Requires 2 slots

Voltage supply 24 V

Order Information

DS2642 FIU & Power Switch Board DS2642

Relevant Software Engineering
Product
347
2016

SCALEXIO / DS2671 Bus Board
DS2671 Bus Board

HighFlex board for interfacing to different bus systems
Highlights
Supports CAN, LIN, CAN FD, and FlexRay bus systems

4 flexibly configurable channels


Application Area
The DS2671 Bus Board is the interface between dSPACE With its freely configurable channels, the DS2671 can serve
Simulator and various bus systems. It has 4 multifunctional different bus systems. The selected bus system can easily be
channels, each of which can support a bus system that is changed from project to project because the channels can
assigned to it by software. be completely configured by software.
The following buses and protocols are supported:
FlexRay Other bus systems and protocols can be added on request.
CAN (high-speed & fault-tolerant)
CAN FD
LIN/K-Line
RS232, RS422, RS485
TLL–based protocols
I/O Functionality
Each channel on the DS2671 has the circuit parts for sup- A different bus system can be used on each of the 4 chan-
porting various bus systems, comprising a FPGA for the core nels on the DS2671.
and assorted transceivers. The bus system controllers, which
include certified IP cores such as the Bosch E-Ray controller For information on the failure simulation function, please
for FlexRay, are implemented on the bus FPGA. refer to Failure Simulation on p. 324.
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.
348
2016

SCALEXIO / DS2671 Bus Board
Introduction
Technical Details
General 4 independent bus channels

Onboard failure routing unit (FRU) (p. 324)

Overvoltage and undervoltage protection for transceivers

Application Fields
Parallel termination resistors with overcurrent protection


Channel-specific LEDs for individual bus channels (inactive, ready for data transfer, data

transfer running, error message)
One piggyback module slot per channel for a customer-specific transceiver

Supported protocols/bus systems FlexRay 2.1 (based on Bosch E-Ray)

High-speed CAN (ISO 11898-2), incl. CAN FD (ISO and non-ISO)

Fault-tolerant CAN (ISO 11898-3)

LIN 2.0/K-Line (ISO 9141)

RS232, RS422 and RS485

TTL driver


Software

Requires 1 slot

Voltage supply 24 V

Order Information

DS2671 Bus Board DS2671

Hardware
Relevant Software
Product
IOCNET
I/O connector
connection Required ConfigurationDesk (p. 48)
Optional RTI CAN MultiMessage Blockset (p. 74)
DC
DC
Fuse NEW: Bus Manager (p. 54)
Engineering
FRU
Termination
Controller
Bus Piggy-
transceivers or back
Bus FPGA
. 4
1 ..
Status LED LED
349
2016

SCALEXIO / DS2907 Battery Simulation Controller
DS2907 Battery Simulation Controller

Power supply control for battery simulation
Highlights
Supports different power supply units for battery

simulation
Wiring simplified by adapter

Application Area
The DS2907 Battery Simulation Controller is used to control Two battery simulation modules can be plugged onto the
the current and voltage values of battery simulation in a DS2907 to support up to two power supply units from
SCALEXIO system. Control is performed by software. different manufacturers like TDK-Lambda and Delta. Other
power supply units can also be used.
Supported Power Supply Units

Two adapter modules are available for easier connection No slot is needed for mounting it in SCALEXIO. An optical
and wiring of different power supply units. IOCNET connection acts as an internal interface.
Battery Simulation Adapter Module Supported Power Supply Units

DS2907M1 Adapter Module TDKLambda GenesysTM 20V76A

TDKLambda GenesysTM 40V38A

TDKLambda GenesysTM 60V25A

DS2907M2 Adapter Module Delta SM35/45 (with RS232 option – P183)1)

Delta SM15/100 (with RS232 option – P183)1)

1)
Example of custom-specific solution. Further power supplies can be supported on request.
Order Information

DS2907 Battery Simulation Controller (Base Board) DS2907

DS2907M1 Adapter Module for TDKLambda power supply units DS2907_M1
DS2907M2 Adapter Module for Delta power supply units DS2907_M2

Relevant Software
Product
350
2016

SCALEXIO / Additional Solutions
Additional Solutions
Introduction
SCALEXIO Interface Solution for ARINC 429
The SCALEXIO Interface Solution for ARINC 429 enables
the connection of a dSPACE real-time system to an ARINC
429 network. ARINC 429 is typically used in commercial
aircraft projects.
Application Fields
The solution is based on PMC modules from AIT, a full-
featured and aerospace-industry-proven hardware. The PMC
modules are on a carrier board that is plugged into the
SCALEXIO processing unit (p. 328), providing the optimal
bandwidth to the real-time model. dSPACE specifically de-
veloped QNX device drivers to ensure real-time simulation
capability.
Configuration with the well-known and established AIT
Software
Flight Simulyzers is seamlessly integrated into the configura-
tion process via dSPACE ConfigurationDesk (p. 48).
Technical Details
General AIT ARINC 429 module on PCI carrier board

Hardware
4, 8, 16, or 32 software-programmable Tx/Rx channels per PMC module

AIT Flight Simulyzer used for fieldbus configuration

Code generation by ConfigurationDesk

Features Programmable high-speed and low-speed operation

Transmission and reception of multiple labels per channel

Multiple transmission rates for individual labels

Configuration of the labels based on the data formats and scaling factors

Transmission of same labels with different SDI values possible

Scheduled transfers and block transfers supported

Data buffers for individual labels for scheduled and block transfers

Continuous and counter-based transfers

Engineering
Order Information

SCALEXIO Interface Solution for ARINC 429 Please inquire
351
2016

SCALEXIO Interface Solution for MIL-STD-1553

The SCALEXIO Interface Solution for MIL-STD-1553 en-
ables the connection of a dSPACE real-time system to an
MIL-STD-1553 network. MIL-STD-1553 is typically used in
non-commercial aerospace projects.
The solution is based on XMC modules from AIT, a full-

featured and aerospace-industry-proven hardware. The XMC
capability.

Technical Details
General AIT MIL-STD-1553 XMC module on PCIe carrier board

One, two or four dual redundant MIL-STD-1553A/B databus streams

Operate as bus controller, 31 remote terminals, and bus monitor operation



Features Multi-level trigger for capture and filtering

IRIG-B time code encoder/decoder

FPGA-based hardware architecture

Transformer or direct coupling for connection to the MIL-STD-1553A/B bus stub

Order Information

SCALEXIO Interface Solution for MIL-STD-1553 Please inquire
352
2016

Introduction
SCALEXIO Interface Solution for AFDX®
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. AFDX is
typically used for commercial aircraft.
Application Fields
The solution is based on XMC modules from AIT, a full-
featured and aerospace-industry-proven hardware. The XMC
capability.
Software
Technical Details
General AIT AFDX XMC module on PCIe carrier board

Dual-channel AFDX/ARINC 664 interface

Hardware


Features Simulates up to 32 ARINC 664 end systems, including virtual link (VL) traffic shaping and

input VL redundancy management
Support for up to 128 output virtual links

Support for up to 512 input virtual links

Time stamping of all received messages with 8 ns resolution

Support for transfers of the following types:

UDP Sampling

UDP Queuing

Engineering
SAP (Service Access Ports) UDP

SAP IP

SAP MAC

Order Information

SCALEXIO Interface Solution for AFDX Please inquire
353
2016

SCALEXIO Interface Solution for PROFIBUS and EtherCAT

The dSPACE SCALEXIO Fieldbus 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 PCIe card, which is plugged into the SCALEXIO
processing unit (p. 328) 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. You can use
ConfigurationDesk® (p. 48) for the configuration process,
and configure fieldbuses in Hilscher SYCON.net.
Technical Details
General Hilscher softwarereconfigurable boards

CIFX PCI PROFIBUS board

CIFX PCI RealTime Ethernet (RTE) board

SyCon.Net used for fieldbus configuration


PROFIBUS Features Bus master and slave supported

Cyclic data exchange by selectable bus cycle time

PROFIBUSspecific settings performed in SyCon.net

EtherCAT Features 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

SCALEXIO Interface Solution for PROFIBUS and EtherCAT Please inquire
354
2016

Introduction
PSI5 Master/Slave Solution
Based on the Programmable Generic Interface (PGI1)

Generic interface box for decentralized connection of

sensors and actuators to dSPACE systems via diverse
serial interfaces and protocols
Application Fields
Emulation of sensor signals (e.g., of yaw rate or crash

sensors) with hardware-in-the-loop (HIL) simulation
Connection to a SCALEXIO system via Ethernet

PSI5 Master/Slave Solution supporting up to 4 masters

and 10 slaves
For more information, please see page 500.
Software
Hardware
Engineering
355
2016

SingleBoard Hardware / Introduction
SingleBoard Hardware
For building a complete realtime control system with just one controller board
Highlights
Compact and versatile controller boards

For a variety of applications in rapid control

prototyping
Real-time processor for fast calculation of models

Variety of I/O components


Controller development and rapid control prototyping are Both boards, the DS1103 as well as the DS1104, combine
ideal application areas for the DS1103 PPC Controller Board compactness with high performance and a high number of
and the DS1104 R&D Controller Board. features. Used with Real-Time Interface (RTI), the controller
The DS1103 (ISA bus) can be installed in an AutoBox or boards are fully programmable from the Simulink® block
a dSPACE Expansion Box. The DS1104 board can be in- diagram environment.
stalled in virtually any PC with a free PCI or PCIe slot.
356
2016

SingleBoard Hardware / Introduction
Introduction
Controller Boards
Controller boards contain a real-time processor for fast dSPACE offers two compact and versatile controller boards
calculation of your model, and a variety of I/O interfaces for different requirements and fields of application:
that allow you to carry out your control developments. the DS1103 PPC Controller Board and the DS1104 R&D
Controller Board.
Application Fields
DS1103 PPC Controller Board1) DS1104 R&D Controller Board
Versatile controller board with a high number of I/O Cost-effective controller board with a comprehensive set of
modules, including CAN, and ample calculation power for I/O modules frequently used in control systems.
control prototyping.
DS1104 R&D Controller Board (p. 364)

DS1103 PPC Controller Board1) (p. 358)

Connector Panels
Software
All I/O signals of controller boards can usually be accessed tailored to a specific controller board, so that you have all the
via adapter cables. A more convenient solution is I/O access signals for easy connection to the real world at your disposal.
via connector panels, which make the signals available
in either a 19” rack or a 19” desktop box. The panels are Connector Panels (p. 370)

Demo Equipment
For educational and training purposes, dSPACE also offers Demo Equipment (p. 371)

Hardware
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.
Programming Single-Board Hardware

Implementing your model on dSPACE single-board hardware
is easy with Simulink® and dSPACE’s Real-Time Interface.
Engineering
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 hard-
ware without Real-Time Interface is also possible with the
included C software environment, together with a com-
piler and loader software.
Real-Time Interface (RTI) (p. 56)

1)
The end of life of the DS1103 is planned for 31.12.2019. You can still buy the product until 31.12.2016. New releases
of dSPACE software are guaranteed to continue supporting the DS1103 until at least the end of 2018. After the end
of 2018, no services of any kind will be available for this product. We advise against using the DS1103 in new
projects. For new projects we recommend that you use the successor, dSPACE MicroLabBox (p. 540).
357
For general information on the dSPACE product life cycle, please see p. 617.
2016

SingleBoard Hardware / DS1103 PPC Controller Board
DS1103 PPC Controller Board1)

Powerful controller board for rapid control prototyping
Highlights
Single-board system with real-time processor

and comprehensive I/O
CAN interface and serial interfaces ideally suited

to automotive applications
High I/O speed and accuracy

PLL-driven UART for accurate baud rate selection


The DS1103 controller board is designed for rapid control The DS1103 is an all-rounder in rapid control prototyp-
prototyping and is suitable for applications such as: ing. You can mount the board in a dSPACE Expansion Box
or dSPACE AutoBox to test your control functions in a
Automotive controllers
laboratory or directly in the vehicle. Its processing power
Induction motor control
and fast I/O are vital for applications that involve numer-
Robotics
ous actuators and sensors. Used with Real-Time Interface
Positioning systems and stepper motors
(RTI, p. 56), the controller board is fully programmable from
Active vibration control
the Simulink® block diagram environment. You can configure
all I/O graphically by using RTI. This is a quick and easy way
An integrated Infineon CAN microcontroller makes the to implement your control functions on the board.
board an attractive tool for automotive and automation
applications.
Comprehensive Interfaces Recording and Output of I/O Values

The high number of I/O interfaces makes the DS1103 a The control of electrical drives requires accurate recording
versatile controller board for numerous applications. It pro- and output of I/O values. It is possible to synchronize the
vides a great selection of interfaces, including 50 digital A/D channels and D/A channels, and the position of the
I/O channels, 36 A/D channels, and 8 D/A channels. For incremental encoder interface, with an internal PWM signal
additional I/O tasks, a DSP controller unit built around Texas or an external trigger signal. Also, the serial interface (UART)
Instruments‘ TM320F240 DSP is used as a subsystem. is driven by a phase-locked loop to achieve absolutely
accurate baud rate selection.
1)
of dSPACE software are guaranteed to continue supporting the DS1103 until at least the end of 2018. After the end
of life, no services of any kind will be available for this product. We advise against using the DS1103 in new projects.
358 For new projects we recommend that you use the successor, dSPACE MicroLabBox (p. 540).
2016 For general information on the dSPACE product life cycle, please see p. 617.

Single-Board Hardware / DS1103 PPC Controller Board
Introduction
Technical Details
Processor PowerPC Type PPC 750GX

CPU clock 1 GHz

Cache 32 KB level 1 (L1) instruction cache

32 KB level 1 (L1) data cache

1 MB level 2 (L2)

Bus frequency 133 MHz
Application Fields

Temperature sensor Reads actual temperature at the PPC

Memory Local memory 32 MB application SDRAM as program memory, cached

Global memory 96 MB communication SDRAM for data storage and data exchange with host

Timer 2 general-purpose timers One 32-bit down counter

Reload by software

15-ns resolution

One 32-bit up counter with compare register

Reload by software

30-ns resolution

1 sampling rate timer (decrementer) 32-bit down counter

Reload by software

Software
30-ns resolution

1 time base counter 64-bit up counter

30-ns resolution

Interrupt controller 3 timer interrupts

7 incremental encoder index line interrupts

1 UART (universal asynchronous receiver and transmitter) interrupt

1 CAN interrupt

1 slave DSP interrupt

2 slave DSP PWM interrupts

1 host interrupt

4 external interrupts (user interrupts)

Hardware
A/D converter Channels 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.)
4 parallel channels each equipped with one sample & hold A/D converter

Note: 8 A/D converter channels (4 multiplexed and 4 parallel) can be sampled simultaneously.

Resolution 16-bit

Input voltage range ±10 V

Overvoltage protection ±15 V

Conversion time Multiplexed channels: 1 µs1)

Parallel channels: 800 ns1)

Engineering
Offset error ±5 mV

Gain error ±0.25%

Offset drift 40 µV/K

Gain drift 50 ppm/K

Signal-to-noise ratio >83 dB

D/A converter Channels 8 channels

Resolution 16-bit

Output range ±10 V

Settling time 5 µs (14-bit)

Offset error ±1 mV

Gain error ±0.5%


Gain drift 25 ppm/K

Speed and timing specifications describe the capabilities of the hardware components and circuits of our products.
1)
Depending on the software complexity, the attainable overall performance figures can deviate significantly from the hardware
specifications. 359
2016

D/A converter Signal-to-noise ratio >83 dB

I max ±5 mA

C I max 10 nF

Digital I/O Channels 32 parallel I/O channels

Organized in four 8-bit groups

Each 8-bit group can be set to input or output (programmable by software)

Voltage range TTL input/output levels

I out , max ±10 mA

Digital incremental Channels 6 independent channels

encoder interface Single-ended (TTL) or differential (RS422) input (software programmable for each channel)

Position counters 24-bit resolution

Max. 1.65 MHz input frequency, i.e.,fourfold pulse count up to 6.6 MHz

Counter reset or reload via software

Encoder supply voltage 5 V/1.5 A

Shared with analog incremental encoder interface

Analog incremental Channels 1 channel

encoder interface Sinusoidal signals: 1 Vpp differential or 11 µApp differential (software programmable)

Position counters < 5° resolution

32-bit loadable position counter

Max. 0.6 MHz input frequency, i.e., fourfold pulse count up to 2.4 MHz

A/D converter performance 6-bit resolution

10 MSPS

Encoder supply voltage 5 V/1.5 A

Shared with digital incremental encoder interface

CAN interface Configuration 1 channel based on SAB 80C164 microcontroller

ISO DIS 11898-2 CAN high-speed standard

Baud rate Max. 1 Mbit/s

Serial interface Configuration TL6C550C single UART with FIFO


RS232/RS422 compatibility

Baud rate Up to 115.2 kBd (RS232)

Up to 1 MBd (RS422)

Slave DSP Type Texas Instruments TMS320F240 DSP

Clock rate 20 MHz

Memory 64 Kx16 external code memory

28 Kx16 external data memory

4 Kx16 dual-port memory for communication

32 KB flash memory

I/O channels1) 16 A/D converter inputs

10 PWM outputs

4 capture inputs

2 serial ports

Input voltage range TTL input/output level

A/D converter inputs: 0 … 5 V

Output current Max. ±13 mA

Host interface Plug & Play support

Requires a full-size 16-bit ISA slot


characteristics Ambient temperature 0 … 50 ºC (32 … 122 ºF)

Cooling Passive cooling

Power supply +5 V ±5%, 4 A

+12 V ±5%, 0.75A

-12 V ±5%, 0.25A

360
2016 1)
The exact number of I/O channels depends on your configuration and is described in the user documentation.

Order Information
Introduction
DS1103 PPC Controller Board DS1103


Included DS1103 Real-Time Library
–
Application Fields
Experiment and Platform Manager for hardware management
–
Required Real-Time Interface (RTI) (p. 56)
RTI

Microtec C Compiler for PowerPC (p. 111)
CCPPPC

Optional Real-Time Interface CAN Blockset (p. 71)
RTICAN_BS

Real-Time Interface CAN MultiMessage Blockset (p. 74)
RTICANMM_BS

See p. 120
PLATFORM_API

MotionDesk (p. 156)
See p. 156
Software
Optional Connector Panel (p. 370)
CP1103

Connector/LED Combi Panel (p. 370)
CLP1103

Set of adapter cables for DS1103
ADP_CAB1103

Block Diagram
Hardware
ISA Bus PC
Slave
DSP I/O
96 MB
Host
Interface Communication PWM
PowerPC SDRAM 1 x 3-Phase
750GX 4 x 1-Phase
4 Capture
Inputs
Engineering
Local Bus TMS320F240
DSP Analog Input
16 ch. 10-bit
32 MB 2 General Interrupt Dual Port Serial

Application Purpose Controller RAM peripheral
SDRAM Timers interface
Serial
16- / 32-bit I/O Bus communication
interface
ADC DAC Incr. Encoder Digital I/O Serial Digital I/O

20 channels 8 channels Interface Dual Port
7 channels 32 channels RAM 18 channels
16-bit 16-bit RS232/RS422
CAN Interface
on 80C164
Master PPC I/O
DS1103
361
2016

SingleBoard Hardware / DS1103 PPC Controller Board
Graphical Configuration of the Controller Board

Using RTI
With Real-Time Interface (RTI, p. 56), 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. 71), CAN configurations can be completely carried out
in a Simulink block diagram, with very little effort.
RTI CAN MultiMessage Blockset (p. 74) for graphical configuration

of CAN interfaces.
RealTime Interface (p. 56) provides Simulink blocks for convenient

configuration of items such as A/D, D/A, digital I/O lines, incremental
encoder interface and PWM generation.
362
2016

Introduction
Robotics
Rapid Control Prototyping in Robotics Easy Handling
The DS1103 provides six digital incremental encoder inter In the example below, the controller board replaces the
faces. This is sufficient to pick up all the movements of position controller. The easy programmability of the DS1103
a six-joint robot. Thus, this cost-effective single-board enables you to implement and test different control algo-
hardware makes it possible to perform rapid control rithms very quickly, which reduces design iteration times
prototyping in robotics. to a minimum. The prototyping hardware allows easy
Application Fields
parameter changing and modification, without any hardware
setup changes.
Calculating Values
The real-time system picks up the robot‘s six incremental
encoder signals to determine the current robot position.
Then this data is compared with the reference values.
Software
Afterwards, the DS1103 calculates the control algorithm
and sends the controller output – for example, data on
positions and velocities – back to the robot.
Hardware
Calculating a control algorithm for robotics on a DS1103 PPC Controller Board.
Further Processing Potential Engineering

All reference values are calculated in real-time, even for
inverse kinematics with highly nonlinear functions. Exter-
nal 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.
363
2016

SingleBoard Hardware / DS1104 R&D Controller Board
DS1104 R&D Controller Board

Costeffective system for controller development
Highlights
Single-board system with real-time hardware

and comprehensive I/O
Cost-effective

PCI/PCIe (PCI Express) hardware for use in PCs


The real-time hardware based on PowerPC technology and The DS1104 R&D Controller Board upgrades your PC to a
its set of I/O interfaces make the controller board an ideal powerful development system for rapid control prototyping
solution for developing controllers in various fields, such as (“R&D“ stands for research & development). Real-Time
drives, robotics, and aerospace. The board is used in many Interface (RTI, p. 56) provides Simulink® blocks for graphical
university laboratories. 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 func-
tion 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.
364
2016

Single-Board Hardware / DS1104 R&D Controller Board
Introduction
Technical Details
Processor MPC8240 processor with PPC 603e core and on-chip peripherals

64-bit floating-point processor

CPU clock: 250 MHz

2 x 16 KB cache, on-chip

Memory Global memory 32 MB SDRAM

Flash memory 8 MB
Application Fields

Timer 4 general-purpose timers 32-bit down counter

Reload by hardware

80-ns resolution

1 sampling rate timer (decrementer) 32-bit down counter

Reload by software

40-ns resolution

1 time base counter 64-bit up counter

40-ns resolution

Interrupt controller 5 timer interrupts

2 incremental encoder index line interrupts

1 UART interrupt

Software
1 slave DSP interrupt

1 slave DSP PWM interrupt

5 A/D converter (end of conversion) interrupts

1 host interrupt

4 external interrupts (user interrupts)

A/D converter Channels 4 multiplexed channels equipped with one sample & hold A/D converter (1x16-bit)

4 parallel channels each equipped with one sample & hold A/D converter (4x12-bit)

Note: 5 A/D converter channels (1x16-bit and 4x12-bit) can be sampled simultaneously

Resolution Multiplexed channels: 16 bit

Parallel channels: 12 bit

Input voltage range ±10 V

Hardware
Conversion time Multiplexed channels: 2 µs1)

Parallel channels: 800 ns1)

Offset error ±5 mV

Gain error Multiplexed channels: ±0.25%

Parallel channels: ±0.5%


Gain drift 25 ppm/K

Signal-to-noise ratio Multiplexed channels: >80 dB

Parallel channels: >65 dB

D/A converter Channels 8 channels

Engineering
Resolution 16-bit

Output range ±10 V

Settling time Max. 10 µs (full-scale, accuracy ½ LSB)

Offset error ±1 mV

Gain error ±0.1%


Gain drift 25 ppm/K

Signal-to-noise ratio >80 dB

Imax ±5 mA

Digital I/O Channels 20-bit parallel I/O

Single bit selectable for input or output


Iout, max ±5 mA

1)
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.
365
2016

Digital incremental Channels 2 independent channels

encoder interface Selectable single-ended (TTL) or differential (RS422) input (software programmable

for each channel)
Position counters 24-bit resolution

Max. 1.65 MHz input frequency, i.e., fourfold pulse count up to 6.6 MHz

Counter reset or reload via software

Sensor supply voltage 5 V/0.5 A

Serial interface Configuration Single UART (universal asynchronous receiver and transmitter) with FIFO


RS232/RS422/RS485 compatibility


Up to 1 MBd (RS422/RS485)

Slave DSP Type Texas Instruments TMS320F240 DSP

16-bit fixed-point processor

Clock rate 20 MHz

Memory 64Kx16 external code memory

28Kx16 external data memory

4Kx16 dual-port memory for communication

32 KB flash memory

I/O channels 1)
10 PWM outputs

4 capture inputs

1 serial peripheral interface

Input voltage range TTL input/output level

A/D converter inputs: 0 … 5 V


Host interface (requires one PCI or one PCIe x 1 slot) PCI PCIe
Physical Physical size 185 x 107 mm (7.28 x 4.2 in)
220 x 111 mm (8.66 x 4.3 in)

0 … 55 ºC (32 … 131 ºF)

Cooling Active cooling by fan
Active cooling by fan

Power consumption 18.5 W
Please inquire
Power supply +5 V ±5%, 2.5 A
Please inquire
+12 V ±5%, 0.3 A

-12 V ±5%, 0.2 A

1)
The exact number of I/O channels depends on your configuration and is described in the user documentation.
366
2016

Introduction
Order Information

DS1104 R&D Controller Board (with PCI host interface) DS1104

DS1104 R&D Controller Board (with PCI Express host interface) DS1104PCIE

Application Fields
Included DS1104 Real-Time Library
–
Experiment and Platform Manager for hardware management
–
RTI

Microtec C Compiler (p. 111)
CCPPPC

Optional ControlDesk® Next Generation (p. 120)
See p. 120
PLATFORM_API

Software
Optional Connector Panel (p. 370)
CP1104

Combined Connector/LED Panel (p. 370)
CLP1104

Adapter cable for DS1104
ADP_CAB1104

Hardware
Engineering
367
2016

Block Diagram
PCI Bus / PCIe x 1 Bus PC
Slave
DSP I/O
PCI Interface / PWM
PCIe Interface 1 x 3-Phase
4 x 1-Phase
Interrupt Control
Unit
32 MB TMS320F240 4 Capture
SDRAM Timers DSP Inputs
Memory Controller
8 MB Flash Dual Port Serial

Memory PowerPC 603e RAM peripheral
interface
Digital I/O
24-bit I/O Bus 14 channels
ADC DAC Incr. Encoder Digital I/O Serial Interface

4 ch. 16-bit 8 channels 2 channels 20 channels RS232/RS485/
4 ch. 12-bit 16-bit RS422
Master PPC I/O
DS1104
368
2016

Introduction
Induction Motor Control
Use Case
Drive Control Determining Values
In this use case, an induction motor controller is developed One of the board‘s incremental encoder interfaces picks up
with the DS1104. The DS1104 is well suited for drive control: the encoder signal of the motor, while two A/D converters
while in this use case the slave DSP system calculates the are required to analyze the motor currents. The controller
Application Fields
PWM signals, the PowerPC’s calculation power supports board calculates the control algorithm on the basis of the
convenient simulation. With an experiment software such measured values and determines the corresponding pulse
as ControlDesk® Next Generation (p. 120), measuring and width modulation (PWM). The three-phase PWM signals are
parameterization can be performed during run-time. generated on the board‘s DSP subsystem and determine the
converter‘s output voltage and frequency.
DS1104 R&D
Software
Controller Board
Encoder Signal
6 PWM ia
Signals
Ua
Hardware
Frequency Ub 3
AC
Converter Uc
Engineering
369
2016

SingleBoard Hardware / 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

Access digital signals via Sub-D connectors

Sub-D connectors are grouped according to I/O

channels or functional units
LED panels indicate the status of the board‘s digital

signals
Connector Panel Connector/LED Combi Panel
Board BNC Connectors Sub-D Connectors Width Width

DS1103 (p. 358) 20 ADC inputs
Digital I/O
14 MU 1)
21 MU1)
8 DAC outputs
Slave DSP I/O

Incremental encoder interfaces

CAN interface

Serial interfaces

DS1104 (p. 364) 8 ADC inputs
Digital I/O
9 MU1) 14 MU1)
8 DAC outputs
Slave DSP I/O

Incremental encoder interfaces

Serial interfaces

1)
MU = measurement unit (1.2“ / 30.5 mm)
Order Information

Connector Panel for DS1103 PPC Controller Board CP1103

Connector Panel for DS1104 R&D Controller Board CP1104

Connector/LED Combi Panel for DS1103 PPC Controller Board CLP1103

Connector/LED Combi Panel for DS1104 R&D Controller Board CLP1104

370
2016

SingleBoard Hardware / Demo Equipment
Demo Equipment
Introduction
Hardware and software for demonstrating singleboard hardware
Highlights
Application Fields
For DS1103 PPC Controller Board and

DS1104 R&D Controller Board
Simulation of a hard disk‘s access arm

Ideally suited to university labs

Simulation of a 7th-order mechanical actuator

(voice-coil-driven flexible positioner, VCFP)
Software
Simulating a Positioning System VCFP Demo Equipment
If you want to start controlling right after installing the VCFP hardware
system, or if you are looking for an inexpensive, ‘impossible- MATLAB®/Simulink® demo controller for simulation
to-break’ way to close the loop in your students’ labs, the Instrumentation panel
VCFP demo is an attractive solution. The model’s dynamics Automation scripts
include an integrator, two first-order lag transfer functions,
and two resonances at 1.5 and 2 kHz.
Hardware
Order Information
Product Order Number Engineering

VCFP demo equipment VCFP

Relevant Hardware

Required Cable to DS1103 PPC Controller Board or VCFP_CAB1103

Cable to DS1104 R&D Controller Board VCFP_CAB1104

DS1103 PPC Controller Board (p. 358) or DS1103

DS1104 R&D Controller Board (p. 364) DS1104

371
2016

Modular Hardware / Introduction
Modular Hardware
Optimum scalability and flexibility for hardware that fits your project
Highlights
Scalable hardware for applications like rapid control

prototyping and hardware-in-the-loop simulation
High processing power

High performance with multiprocessor systems

Fast access to I/O hardware

Variety of I/O boards available

Key Benefits Processor Boards

Our modular hardware gives you optimum scalability and Processor boards (p. 373) are the basis of dSPACE’s modu-
flexibility. You can choose from our wide range of I/O boards lar hardware. They give your system real-time calculation
and processor boards to put together exactly the hardware power, and also provide the interfaces to the I/O boards
you need for your project. You can set up both single- and to the host PC. The processor boards also do all the
processor and multiprocessor systems with a processor communication with experiment tools running on the host
board as a base, and then adapt the system to your tasks computer.
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.
I/O Boards Accessories

The wide range of I/O boards (p. 374) features numerous Accessories (p. 375) for our modular hardware will help you
options, from simple signal input/output to complex signal complete your system. In addition to expansion boxes for
generation and interface support. Nearly all I/O boards can installing dSPACE systems, for use in either the laboratory
be configured and programmed graphically using Simulink® or a vehicle, there are also panels allowing easy access to
and Real-Time Interface (RTI). For special I/O specifications, the signals from I/O boards.
which are not covered by our off-the-shelf boards, dSPACE
provides additional I/O solutions (p. 498).
372
2016

Introduction
Processor Boards
DS10051) PPC Board DS1007 PPC Processor Board
The DS1005 PPC Board (p. 376) provides the computing The DS1007 PPC Processor Board (p. 386) is designed for
power for your real-time system and also functions as an applications which require a combination of high computing
interface to the I/O boards and the host PC. It is equipped power and fast closed-loop rates. It features a QorlQ P5020
with the 750GX PowerPC processor from IBM. The process- dual-core processor running at 2 GHz.
ing power and I/O capacity can be boosted even further by The DS1007 offers an integrated, high-data-throughput Eth-
Application Fields
linking up to 20 DS1005 PPC Boards in a multiprocessor ernet host interface for setting up modular systems without
system (p. 373). additional host interface cards. The DS1007 is highly expand-
able. Its Ethernet I/O interface can be used for direct real-time
DS1006 Processor Board model access via the TCP/ IP or UDP/IP protocol and for by-
The DS1006 Processor Board (p. 380) is dSPACE’s flagship passing. The DS1007 also comes with a USB interface for
for high-end real-time applications. The DS1006 is an alterna- long-term data acquisition via a USB mass storage device.
tive heart for modular hardware, designed for calculating Just as the DS1005 and DS1006, the DS1007 also allows the
complex, precisely detailed simulation models that require setup of a multiprocessor system (p. 373). For example, you
enormous computing power. The processing power and I/O can connect the DS1007 to several other DS1007 boards to
capacity can be boosted even further by linking up to 20 boost the processing power and I/O capacity of your system.
Software
DS1006 Processor Boards in a multiprocessor system (p. 373).
Choosing between DS10051), DS1006, and DS1007

This table gives you an impression of the three processor boards’ capabilities.
DS1005 PPC Board1)2) DS1006 Processor Board3) DS1007 Processor Board4)

Key Features For applications with very high I/O
n For applications with moderate I/O
n For applications with high I/O
n
requirements (minimum latencies, high requirements (moderate latencies, moderate requirements (low latencies, high
Hardware
reactivity) reactivity) reactivity)
For models with low complexity
n For models with very high complexity
n For models with high complexity
n
1)
The end of life of the DS1005 is planned for 31.12.2020. You can still buy the product until 31.12.2016. New releases of dSPACE software are
guaranteed to continue supporting the DS1005 until at least the end of 2019. After the end of life, no services of any kind will be available
for this product. We advise against using the DS1005 in new projects. For new projects we recommend that you use the successor, the dSPACE
DS1007 PPC Processor Board (p. 386). For general information on the dSPACE product life cycle, please see p. 617.
2)
1 GHz processor
3)
2.8 GHz Quad-Core AMD Opteron™ processor
4)
QorlQ P5020 dual-core processor running at 2 GHz
Engineering
Multiplying Calculation Power
Up to 16 I/O boards Up to 16 I/O boards
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, DS1006 and DS1007 you can reach
any performance and I/O capacity you need simply by ex- PHS bus
panding your hardware with further processor boards. The

processor boards are connected via Gigalink Modules, which Gigalink

Module
Gigalink
Module
Further processor boards
allow high-speed serial data transmission via fiber-optic Processor boards (up to 20 in total)
cable and 1.25 Gbit/s technology, and over distances ex-

Setting up multiprocessor systems.
ceeding 100 meters.
Multiprocessor setup for the DS1005 (p. 376)
373
2016

I/O Boards
Key Benefits
Modular hardware usually contains at least one I/O board for interface support. If you cannot find the I/O board you need,
connection to the real world. we also offer additional I/O solutions to fit your require-
To meet all the demands of rapid control prototyping and ments.
hardware-in-the-loop simulation, dSPACE‘s wide range of I/O boards overview (p. 374)
intelligent I/O boards features numerous options, from Additional I/O solutions (p. 498)
simple signal input/output to complex signal generation and Engineering services (p. 608)
Connector Panels for I/O Boards

With I/O boards, all I/O signals can usually be accessed at tailored to specific I/O boards, so that all the signals for
the boards’ connectors. A more convenient solution is I/O connection to the real world are at your disposal.
access via connector panels, which make the signals avail- Panels for I/O boards (p. 504)
able 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 High-speed 32-bit bus between processor board and

performed via the peripheral high-speed I/O bus (PHS bus). I/O boards
The PHS bus provides several features that are essential for 20 MB/s peak transfer rate (higher for new I/O boards)

real-time control systems: The I/O access times are guaranteed Up to 16 I/O boards can be connected to one processor

because it is a single-master bus, and is always available for board
I/O-to-processor communication. As the PHS bus is espe- Up to 64 interrupts from up to 8 I/O boards can be

cially designed for real-time applications, there is no software used, for example, from CAN messages, ECU inter
overhead caused by extensive transfer protocols. 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. 390
DS2003 Multi-Channel A/D Board 32 channels, resolution 4, 8, 10, 12, 13, 14, 15 or 16 bit, MUX, 2 ADCs p. 390
DS2004 High-Speed A/D Board 16 channels, resolution 16 bit, 16 independent ADCs, 800 ns conversion time p. 396
DS2101 D/A Board 5 parallel D/A converters, resolution 12 bit, sample time 3.0 μs p. 399
DS2102 High-Resolution D/A Board 6 parallel D/A converters, resolution 16 bit, sample time 1.6 μs p. 399
DS2103 Multi-Channel D/A Board 32 parallel D/A converters, resolution 14 bit, sample time 10.0 μs p. 399
DS2202 HIL I/O Board Signal conditioning for 12 V, 24 V, and 48 V automotive systems p. 406
DS2211 HIL I/O Board Central I/O board for hardware-in-the-loop simulation,16 x A/D, 20 x D/A p. 410
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. 416
DS2401 Resistive Sensor Simulation Board Simulating resistive sensors, 4 resistance output channels (10 Ω to 500 kΩ) p. 422
DS3001 Incremental Encoder Interface Board Precise position control, 5 incremental encoder interface channels (digital) p. 424
374
2016

Introduction
I/O Board Details Page
DS3002 Incremental Encoder Interface Board Precise position control, 6 incremental encoder interface channels (digital and analog) p. 424
DS4002 Timing and Digital I/O Board Generating and capturing digital signals, 8 timing channels, 200 ns resolution, 32 digital I/O p. 428
DS4003 Digital I/O Board 96 digital I/O channels for various applications p. 433
DS4004 HIL Digital I/O Board 96 bidirectional digital I/O channels with signal conditioning p. 434
DS4121 ECU Interface Board Connection of ECUs to a dSPACE system, 2 bypass interfaces p. 436
DS4201 Prototyping Board Integration of customized circuits p. 440
DS4201-S Serial Interface Board Communication between a dSPACE system and external devices, 4 RS232/RS422/RS485 channels p. 441
Application Fields
DS4302 CAN Interface Board Connection to CAN bus, 4 CAN channels p. 442
DS4330 LIN Interface Board Connection to LIN bus, 16 channels p. 445
DS4505 Interface Board Interface to FlexRay or CAN FD communication bus p. 448
DS5001 Digital Waveform Capture Board Capturing of digital signals, 16 channels, resolution 25 ns p. 452
DS5101 Digital Waveform Output Board Generation of pulse patterns, 16 channels, resolution 25 ns p. 456
SCRAMNet+ Interface Connection to SCRAMNet+ networks p. 466
PROFIBUS Interface Connection to PROFIBUS systems p. 468
Interface to MIL-STD 1553 Connection to MIL-STD-1553 networks p. 470
ARINC 429 Interface Connection to ARINC 429 bus p. 472
ARINC 717 Interface Connection to ARINC 717 bus p. 474
Software
FPGA Base Board FPGA application-specific-programmable on a per project basis p. 476
DS5203 FPGA Board Completely user-programmable via RTI FPGA Programming Blockset p. 462
PWM Measurement Solution High-precision capturing of 3-phase PWM signals p. 478
Position Sensor Simulation Solution Simulation of position sensors p. 480
AC Motor Control Solution Control of diverse AC motors p. 484
EMH Solution Electric motor simulation p. 488
EtherCAT Slave Interface Slave interface to an EtherCAT communication bus p. 494
100 Mbit/s Ethernet Interface (UDP/IP, TCP/IP) Connection to an Ethernet network p. 496
Additional I/O Solutions Solutions for I/O and buses not covered by dSPACE standard boards. Examples: electrical failure p. 498
Hardware
insertion, interfaces to Ethernet, VME, and resolvers
Accessories
Expansion Boxes DS830 MultiLink Panel
Accessories for our modular hardware will help you com- The DS830 MultiLink Panel gives you the option of control-
plete your system. Our I/O boards can be inserted in expan- ling up to 16 dSPACE systems (expansion boxes, Auto-
Engineering
sion boxes with several ISA slots for up to 20 boards. The Boxes, and MicroAutoBoxes1)) from one host PC.
boxes communicate with the host PC via ISA, PCI, PCI DS830 MultiLink Panel (p. 518)
Express, PCMCIA, ExpressCard or Ethernet connections.
Expansion boxes (p. 508)
AutoBoxes DS802 PHS Link Board

AutoBox and Tandem-AutoBox are special expansion The DS802 PHS Link Board enables developers to use I/O boards
boxes for in-vehicle applications. in expansion boxes that do not have their own processor
AutoBox/Tandem-AutoBox (p. 512) boards, but utilize those in other expansion boxes instead.
DS802 PHS Link Board (p. 516)
375
Does not apply to the MicroAutoBox II. The MicroAutoBox II offers an Ethernet host interface.
1) 2016

Modular Hardware / DS1005 PPC Board
DS1005 PPC Board1)

Computing power and scalability
Highlights
PowerPC 750GX, 1 GHz

Fully programmable from Simulink®

High-speed connection to all dSPACE I/O boards

via PHS bus
Multiprocessor system of several DS1005 PPC Boards

via fiber-optic connection (Gigalinks)
Key Benefits Modular Hardware Concept

The DS1005 features a PowerPC 750GX processor running The DS1005 PPC Board is one of dSPACE’s processor boards
at 1 GHz, so it has ample power for the vast majority of that form the core of dSPACE’s modular hardware. Proces-
cases. If you need even more calculation power, the DS1005 sor boards provide the computing power for your real-time
PPC Board meets all multiprocessing requirements. system and also function as interfaces to the I/O boards and
The DS1005 is directly connectable to all dSPACE I/O boards the host PC. The DS1005 is the board of choice for applica-
via PHS and PHS++ bus. The PHS++ bus standard is compat- tions with high sampling rates and a lot of I/O capacity.
ible with the standard PHS bus, but allows faster commu- Great processor power plus fast access to I/O hardware with
nication with I/O boards supporting PHS++ bus access, such minimum latencies make dSPACE processor boards consider-
as the DS2211. ably faster than solutions based on commonly available PCs.
Multiprocessor Setup Compatibility with Earlier Versions

The processor board can be connected to other DS1005 The DS1005 (1 GHz) is compatible with all of its earlier
boards via an additional optical interface (DS910 Gigalink versions. Programs or models compiled for the older versions
Module) to create DS1005 multiprocessor systems of all run on the DS1005 (1 GHz) without modifications. Multi-
sizes, so that your modular hardware can be tailored processor systems can mix old and new DS1005 boards
exactly to your requirements. Synchronization between without impairing performance.
the boards is ensured, since interrupts can be dispatched
to other DS1005 boards via hardware, with minimal
latencies.
1)
of dSPACE software are guaranteed to continue supporting the DS1005 until at least the end of 2019. After the end of
life, no services of any kind will be available for this product. We advise against using the DS1005 in new projects. For
376 new projects we recommend that you use the successor, the dSPACE DS1007 PPC Processor Board (p. 386).

Introduction
Technical Details
Processor IBM PowerPC 750GX, 1 GHz

Up to 4 instructions in parallel

32 KB L1 data cache

32 KB L1 instruction cache

Memory 1 MB L2 cache

Cache running at processor clock

Application Fields
128 MB SDRAM global main memory for host data exchange and application

16
MB flash memory for boot firmware and for user-specific applications, with flight
recorder functionality for data recording
Full host access to global memory

Timer 2 general-purpose timers

Synchronous time base unit (for multiprocessor systems)

Interrupt controller Interrupt controller with up to 18 interrupt sources

Interfaces Serial interface RS232 interface with standard UART allowing transfer rates of up to 115.2 Kbaud

Connection to I/O boards PHS++ bus Interface

32-bit I/O bus for modular I/O configuration (p. 374)

Peak transfer rate 20 MB/s, up to 30 MB/s for new I/O boards

Up to 64 PHS bus interrupts

Software
Host interface One full-size 16-bit ISA slot required

Interface via eight 16-bit I/O ports (ISA bus)

Bidirectional interrupt line (PPC/host PC)

Plug & Play support

Multiprocessor systems Building multiprocessor systems with further DS1005 PPC Boards

Up to 20 DS1005 PPC Boards

High-speed link via one DS910 Gigalink Module on each DS1005

Cable length of up to 100 m

Physical characteristics Physical size 340 x 125 x 15 mm (13.4 x 4.9 x 0.59 in)

Ambient temperature 0 ... 55 ºC (32 ... 131 ºF)

Hardware
Cooling Passive cooling

Power supply +5 V ±5%, 4 A (without DS910 Gigalink Module)

+5 V ±5%, 5.2 A (with DS910 Gigalink Module)

Order Information

DS1005 PPC Board DS1005

Engineering

Included C Real-Time Library
–
Experiment and Platform Manager
–
Required Real-Time Interface (p. 56)
RTI

Microtec C compiler for PowerPC (p. 111)
CCPPPC

Optional Real-Time Interface for multiprocessor systems extension (p. 62)
RTI_MP


Optional PHS bus cable (with x connectors and terminator)
PHS-CABx

DS910 Gigalink Module
DS910

DS802 PHS Link Board
See p. 375

377
2016

Block Diagram
Further DS910 Gigalink PHS Bus
DS1005s Module I/O Boards
1 MB Level 2 PowerPC 16 MB Boot

Cache 750 GX Flash
PHS-Bus Supervisor
Local Bus
64 MB Interface
Global RAM Global Bus
Peripheral Bus
64 MB
Global RAM Global Bus
Serial Interrupt External
Interface Controller Timers
Host
Interface
DS1005
ISA Bus PC
Graphical Programming
Programming from MATLAB®/Simulink®/Stateflow®
You can easily program the DS1005 PPC Board from Simu- Dialogs for altering simulation parameters such as solver
link via Real-Time Interface. A set of Simulink blocks gives options and simulation time, and for generating C code,
access to the entire range of dSPACE I/O Boards. Even are directly accessible from the Simulink environment.
setting up multiprocessor systems is simple thanks to dedi-
cated RTI-MP blocks.
378
2016

Introduction
Multiprocessor Setup via DS910 Gigalink Module
Expanding Processor Power Gigalink Modules
With modular hardware based on the DS1005 PPC Board, All variants of the DS1005 PPC Boards are connected via
you can reach any performance you need simply by expand- optional Gigalink modules, which allow high-speed serial
ing your hardware with further DS1005 boards. Tasks can data transmission via fiber-optic cable and 1.25 Gbit/s tech-
be shared between the processor boards to attain optimum nology. You can connect up to 20 processor boards in a
response times and performance. And what is more, you system, and over distances up to 100 meters, in this way.
Application Fields
automatically increase the I/O capacity of your system. The fiber-optic connectors of the Gigalink modules are
pluggable, making it easy to replace them yourself.
Software
Technical Details – DS910 Gigalink Module
Hardware
General Hardware extension to DS1005 PPC Board for building multiprocessor systems

Requires several DS1005 PPC Boards (1 GHz, 933 MHz, 800 MHz, or 480 MHz variant), each with

a DS910 Gigalink Module
Gross transfer rate: 1.25 Gbit/s

Distance up to 100 m

Hardware details 4
optical, high-speed communication ports (Gigalinks), each providing 16 bidirectional interrupt lines
and 16 bidirectional data channels (2 kilowords width on each channel)
The fiber-optic connectors are pluggable, making it easy to replace them yourself. Substitute connectors

Engineering
are available only from dSPACE (order number: SFP_TRANS_MOD).
I/O access speed of send operations adapted to Gigalink’s capabilities: Data is sent directly without

a FIFO buffer
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
Real-time interrupt dispatching

Passive cooling

379
2016

Modular Hardware / DS1006 Processor Board

Computing power for processingintensive realtime models
Highlights
x86 processor technology

Quad-core AMD Opteron™ processor with 2.8 GHz


High-speed connection to all dSPACE I/O boards

via PHS bus
Multiprocessor system of several DS1006 Processor

Boards via fiber-optic connection (Gigalinks)

The DS1006 Processor Board is one of the processor boards The DS1006 Processor Board is based on an a quad-core
that form the heart of dSPACE’s modular hardware. It is our AMD Opteron™ x86 processor with 2.8 GHz clock fre-
flagship for very complex, large, computation- quency. Thus, it always delivers a high level of processing
intensive models – like the ones found in powertrain and power, even for large-scale real-time applications. If re-
virtual vehicle simulations. In such simulations, the DS1006 quired, you can add an Ethernet I/O interface for Gigabit
provides the computing power for the real-time system and data streaming or a flash memory for automatic, host-
also functions as an interface to the I/O boards and the host independent booting of the real-time applications.
PC. It can be directly connected to all dSPACE I/O boards
via PHS bus.
Multicore Processor for More Computing Power Multiprocessor Setup

You can set up a multiprocessor system by using the indi- If you need even more performance, you can build a multi-
vidual cores of the multicore processor, and assign the I/O processor system by connecting several DS1006 boards via
boards easily by graphical programming via RTI-MP (p. 62). an additional optical interface (DS911 Gigalink Module,
With the possibility for parallel computing and a high- p. 385). Synchronization between the boards is guaranteed,
performance data exchange between the cores, the DS1006 since interrupts can be sent to other processor boards via
multicore board speeds up all your applications (p. 383). hardware, with minimal latencies.
380
2016

Introduction
Technical Details
Processor Quad-core AMD Opteron™ processor, 2.8 GHz

4 x 64 kB L1 data cache, 4 x 64 kB L1 instruction cache, 4 x 512 kB L2 cache, 6 MB L3 cache

Memory 1 GB DDR2-800 SDRAM local memory for the application and dynamic application data

4 x 128 MB DDR2-267 SDRAM global memory for host data exchange

2 MB on-board boot flash memory for boot firmware

Application flash memory on CompactFlash card (accessable via ControlDesk®). The capacity

Application Fields
depends on the card.
Timer For each core: 3 general-purpose timers

Synchronous time base unit (STBU) for multiprocessor systems

Interrupt controller For each core: one interrupt controller with 18 different interrupt sources

The
interrupt sources of the connected I/O boards can be handled from each core via internal
Gigalinks.

Connection to I/O boards PHS++ bus interface

32-bit I/O bus for modular I/O configuration (p. 374)



Software
Host interface One full-size 16-bit ISA slot required

Interface via eight 16-bit I/O ports (ISA bus)

Multiprocessor system Building multiprocessor systems with further DS1006 Processor Boards

Up to 20 DS1006 Processor Boards

Up to 4 high-speed links via one DS911 Gigalink Module on each DS1006

Possible cable length of up to 100 m


Ambient temperature 0 ... 40 °C (32 ... 104 °F)

Cooling Active cooling (fan)

Power supply ISA bus:

Hardware
+5 V ±5%, 2.0 A (without DS911)

+5 V ±5%, 3.0 A (with DS911 as of module revision 2.0)

+12 V ±5%, 1.5 A

CPU power connector: +5 V ±5%, 20 A

Order Information

DS1006 Processor Board DS1006

Engineering
381
2016


–
–
RTI

GNU C compiler for AMD Opteron™
DS1006_COMP

RTI_MP

DS1006 Ethernet Blockset (p. 92)
–

Required For safety reasons DS1006 Processor Boards must be used only in
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.)
Optional PHS bus cable (with x connectors and terminator)
PHS-CABx

DS911 Gigalink Module
DS911

See p. 375

DS921 (Connector bracket for Ethernet connection)
See p. 499

Block Diagram
Further DS911 Gigalink

module PHS bus
DS1006s I/O boards
1 ... 4
Firmware Compact 1024 MB

flash Flash local RAM
AMD
Chipset OpteronTM
(Quad-Core)
..
128 MB PHS-bus External
Bus arbiter interface Timers
global RAM
..
Host
Interface Peripheral bus (32 bit)
.. ..
Interrupt Internal
Controller Gigalink
Watchdog connection
..
Timer A (32 bit)
Timer B (32 bit)
Timer C (64 bit)
DS1006
ISA bus PC
382
2016

Introduction
Programming from
MATLAB®/Simulink®/Stateflow®
You can easily program the DS1006 Processor Board from
Simulink via Real-Time Interface (RTI, p. 56). Simulink blocks
provide access to the entire range of dSPACE I/O boards.
The setting up of multiprocessor systems as well as the
Application Fields
configuration of the data transfer between the processor
cores is simple thanks to dedicated RTI blocks (RTI-MP,
p. 62).
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.
Software
Hardware
Speed Information
Performance of the DS1006 Processor Board Using One Core
ASM Package (including I/O and CAN Restbus Simulation) Mean Turnaround Time
ASM Gasoline Engine Basic Simulation Package (p. 263)
0.11 ms

Engineering
ASM Vehicle Dynamics Simulation Package (including Brake Hydraulics Model) (p. 273)
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 ASM Main Model Component Mean Turnaround Time
model components (Gasoline Engine Basic, Vehicle Dynam- Gasoline Engine Basic
0.16 ms

ics) with I/O and CAN restbus simulation is calculated on Vehicle Dynamics
0.20 ms

different cores with connections to each other via internal

Gigalinks; two DS2211 HIL I/O Boards are connected to the For comparison: the same model with external Gigalinks
PHS bus of one DS1006 Processor Board: and the predecessor DS1006 Processor Board (single-core
383
2016

processor with 2.6 GHz). Two DS1006 Processor boards are Comparison of both Measurements
used with one DS2211 HIL I/O Board connected to each: Because the I/O communication is split into two PHS buses
in the second benchmark, it might be expected to be faster
ASM Main Model Component Mean Turnaround Time than the first one. But the better performance of the
Gasoline Engine Basic
0.17 ms
internal Gigalink connections used in the first benchmark
Vehicle Dynamics
0.22 ms
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).
Performance of the DS1006 Processor Board Using

More Than One Core (Without Connected I/O Boards)
The following benchmark without any connected I/O For comparison: the same model with external Gigalinks
demonstrates the different performance of external and and the predecessor DS1006 Processor Board. ASM – Virtual
internal Gigalink connections: ASM Virtual Vehicle with Vehicle with main model components (Drivetrain, Gasoline
three main model components (Drivetrain, Gasoline Engine, Engine, VehicleDynamics) is calculated on different DS1006s
Vehicle Dynamics) is calculated on different cores connected (predecessor DS1006 with 2.6 GHz single core processor)
to each other via internal Gigalinks. connected to each other via external Gigalinks.
ASM Main Model Component ASM Main Model Component

Mean Turnaround Time Mean Turnaround Time
(without I/O) (without I/O)
Drivetrain
17.2 µs
Drivetrain
43.7 µs

Gasoline Engine
36.1 µs
Gasoline Engine
66.5 µs

Vehicle Dynamics
91.3 µs
Vehicle Dynamics
140.9 µs

These benchmarks are only examples that give an idea of The way the model is divided into parts that can be

the performance achievable by the DS1006 Processor Board. calculated in parallel
The turnaround time of an application depends on a large
number of factors, such as: For applications with tough requirements on I/O latencies,
The application size compared to the cache size of the please note that the DS1006 Processor Board with the
processor Quad-Core processor has to access all connected I/O boards
The amount of I/O at each PHS-bus, because of addi- via one PHS bus.
tional time needed for communication via PHS bus
The number of signals that have to be sent via
Gigalink connections (external or internal)
384
2016

Introduction
With modular hardware based on the DS1006 Processor The DS1006 Processor Boards are connected via optional
Board, you can achieve any performance you need simply Gigalink modules, which allow high-speed serial data trans-
by expanding your hardware with further DS1006 boards. mission via fiber-optic cable and 1.25 Gbit/s technology.
Tasks can be shared between the processor boards to attain You can connect up to 20 processor boards in a system, and
Application Fields
optimum response times and performance. over distances up to 100 meters, in this way.
What is more, this automatically increases the I/O capacity The fiber-optic connectors of the Gigalink modules are
of your system. pluggable, making it easy to replace them yourself.
Software
Hardware
General Hardware extension to DS1006 Processor Board for building multiprocessor systems

Requires several DS1006 Processor Boards, each with a DS911 Gigalink Module



Hardware details 4 optical, high-speed communication ports (Gigalinks), each providing 16 bidirectional interrupt lines and

Engineering
16 bidirectional data channels (2 kilowords width on each channel)
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).

a FIFO buffer


Passive cooling

385
2016

Modular Hardware / DS1007 PPC Processor Board

Computing power and small I/O latencies
Highlights
Freescale QorlQ P5020, dual-core, 2 GHz


Integrated Ethernet host interface

Ethernet I/O interfaces for real-time connection of

sensors and devices via TCP/IP and UDP/IP protocols
Multiprocessor system of several DS1007 PPC Processor

Boards via fiber-optic connection (Gigalinks)

The DS1007 PPC Processor Board is one of the processor As the successor of the DS1005, the DS1007 features a
boards that form the core of dSPACE’s modular hardware. QorlQ P5020 dual-core processor running at 2 GHz. The
The DS1007 is an excellent fit when your application DS1007 offers an integrated, high-data-throughput Ether-
models require a combination of high computing power net host interface for setting up modular systems without
and fast closed-loop rates (e.g., for electric motor control, additional host interface cards.
advanced driver assistance systems or active noise and The DS1007 is highly expandable. Its Ethernet I/O interface
vibration cancellation). 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 and
booting applications via the integrated USB interface.
Dual-Core Processor for More Computing Power Multiprocessor Setup

You can set up a multicore system by using the individual Several DS1007 boards can be connected together via
cores of the dual-core processor and easily assign the I/O additional optical interfaces (DS911 Gigalink Module) to
boards by graphical programming via RTI-MP. The DS1007 create different powerful DS1007-based multiprocessor
dual-core board speeds up all your applications with paral- systems. This lets you increase the processing power and
lel computing and high-performance data exchange I/O capabilities for real-time applications far beyond the
between the cores. individual board performance. Synchronization between the
boards is ensured, since interrupts can be dispatched to
other DS1007 boards via hardware, with minimal latencies.
386
2016

Introduction
Technical Details
Processor Real-time processor Freescale QorlQ P5020, dual-core, 2 GHz

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 Freescale QorlQ P1011 800 MHz for communication with host PC

coprocessor
Memory 1 GB DRAM

Application Fields
128 MB flash memory

Timer Each core has 3 general-purpose timers

Synchronous time base unit (for multiprocessor systems)

Interrupt controller Each core has one interrupt controller with full and independent access to all real-time events

Additional interprocessor interrupts and messages via internal Gigalinks


Ethernet interface Integrated low-latency Gigabit Ethernet I/O interface

USB interface USB
2.0 interface for data logging (“flight recorder”) and booting applications via USB mass
storage device (max. 32 GB supported)
Connection to I/O boards PHS++ bus Interface

32-bit I/O bus for modular I/O configuration

Software


Host interface Integrated Gigabit Ethernet host interface

Multiprocessor systems Building multiprocessor systems with further DS1007 PPC Processor Boards

Up to 20 DS1007 PPC Processor Boards

Up to 4 high-speed links via one DS911 Gigalink Module on each DS1007

Cable length of up to 100 m



Cooling Active cooling via fan

Hardware

+12 V ±5%, 0.8 A

Engineering
387
2016

Order Information

DS1007 PPC Processor Board DS1007


–
–
RTI

GNU C Compiler for PowerPC
DS1007_COMP

RTI_MP

RTI_ETH_BS

RTI USB Flight Recorder Blockset
RTI_USB_FR_BS


Optional PHS bus cable (with x connectors and terminators)
PHS-CABx

DS911 Gigalink Module (requires an additional slot)
DS911_DS1007

See p. 375

DS1007 RS232 bracket (requires an additional slot)
DS1007_RS232

Block Diagram
I/O boards PHS bus I/O boards
RAM PHS-bus
2 x 512MB interface
Real-time
processor
(P5020)
Flash Interrupt
128MB controller
Local bus
Timer A (32 bit)

RAM Real-time
Timer B (32 bit)
256MB Host clock (RTC)
Timer D (32 bit)
communication
coprocessor
(P1011)
Flash
64MB
Ethernet USB 2.0 UART

switch
DS1007
DS911
ECU Ethernet PC RS232 Gigalink Further
Module DS1007s
388
2016

Introduction
With modular hardware based on the DS1007 PPC Proces- The DS1007 PPC Processor Boards are connected via op-
sor Board, you can achieve any performance you need tional Gigalink modules, which allow high-speed serial data
simply by expanding your hardware with further DS1007 transmission via fiber-optic cable and 1.25 Gbit/s technol-
boards. Tasks can be shared between the processor boards ogy. In this way, you can connect up to 20 processor boards
Application Fields
to attain optimum response times and performance. What in a single setup, and over distances up to 100 meters.
is more, this automatically increases the I/O capacity of your
system. With RTI-MP the models can be distributed to the
individual processor boards in an intuitive way.
Software
Hardware
General Hardware extension to DS1007 PPC Processor Board for building multiprocessor systems

Requires several DS1007 PPC Processor Boards, each with a DS911 Gigalink Module

Engineering


Hardware details 4 optical, high-speed communication ports (Gigalinks), each providing 16 bidirectional interrupt lines and

16 bidirectional data channels (2 kilowords width on each channel)
Fiber-optic connectors are pluggable, making it easy to replace1) them yourself.


a FIFO buffer


Passive cooling

1)
Substitute connectors are available only from dSPACE (order number: SFP_TRANS_MOD).
389
2016

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
Up to 32 channels; resolution up to 16 bit

Sample times 3.9 - 5.6 μs (16 bit)


A/D conversion is an element of most applications in rapid The A/D boards provide various channel numbers, resolu-
control prototyping and hardware-in-the-loop (HIL) simulations, and speeds for you to choose from. The table below
tion. In rapid control prototyping, sensors for pressure, gives you an initial overview. The boards can be configured
temperature, or other signals provide analog voltages or from Simulink® using Real-Time Interface (p. 56). You can
currents. In HIL simulations, the electronic control unit pro- select the voltage range and the resolution separately for
vides analog voltages or currents that control the simulated each channel or A/D converter.
actuators.
Comparing the Boards

Sample Time1) Sample Time1)
Board Channels Resolution
(2 Channels) (All Channels)
DS2002 32 in 4, 8, 12, 16 bit, 3.9 μs (16 bit) 66.9 μs (16 bit)
MultiChannel A/D Board shortcycling
DS2003 32 in 4, 8, 10, 12, 13, 14, 15, 5.6 μs (16 bit) 56.6 μs (16 bit)
MultiChannel A/D Board 16 bit, shortcycling
1)
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.
390
2016

Introduction
DS2002 Multi-Channel A/D Board
Technical Details
General 32 A/D input channels (single-ended)

2 independent A/D converters with separate sample & hold (S/H), 16 multiplexed inputs each

Hold mode

4-, 8-,12- or 16-bit resolution (programmable)

Application Fields
±5 V or ±10 V input voltage range (programmable)

A/D channels1), 2) Conversion time1) 1.5, 2.0, 2.5, 3.0 µs (resolution-dependent)

S/H acquisition time 0.9 µs to 0.01% of FSR (full-scale range)

Multiplexer settling time 1.2 µs to 0.01% of FSR

Offset error ±2.0 mV

Gain error ±0.2% of FSR

Offset drift ±4 ppm of FSR/K

Gain drift ±25 ppm of FSR/K

Linearity error ±0.003% of FSR

Differential linearity error ±0.002% of FSR

Software
Missing codes No missing codes at 14-bit resolution

SNR (signal-to-noise ratio) 78 dB

Channel crosstalk -75 dB (at 10 kHz signal frequency)

Input impedance 1 MΩ

Input overvoltage protection Up to ±15 V

Warm-up time 2 min.

Interrupt controller 2 interrupts on end of A/D conversion (one for each A/D converter)

Sampling By software from processor board

Simultaneous

Physical connections 50-pin male Sub-D input connector

Hardware
Host interface One 8- or 16-bit ISA slot (power supply only)




+12 V ±5%, 200 mA

-12 V ±5%, 130 mA

1)
2)
Typical values at 25 °C, 16-bit resolution and ±10 V input voltage range (FSR = full-scale range).

DS2002 Multi-Channel A/D Board DS2002



RTI


Optional Connector Panel for DS2002 (p. 504)
CP2002

391
2016

DS2003 Multi-Channel A/D Board

Technical Details
General 32 A/D input channels (single-ended)

2 independent A/D converters

Simultaneous sample-and-hold (S/H)

Hold mode

4-, 8-,10-, 12-, 13-, 14-, 15- or 16-bit resolution (programmable separately for each channel pair)

±5 V or ±10 V input voltage range (programmable)

1 external trigger input line

A/D Channels1), 2) Conversion time1) 1.4 ... 3.0 µs (resolution-dependent)

S/H acquisition time 1 µs to 0.01% of FSR (full-scale range)

Hold step time 1.6 μs to 0.01% of FSR

Multiplexer settling time 400 ns

Offset error ±2.5 mV







SNR (signal-to-noise ratio) 78 dB

Adjacent channel crosstalk -80 dB

Static crosstalk -80 dB (at 10 kHz signal frequency)

Dynamic crosstalk -110 dB


Input overvoltage protection Protection up to ±15 V

Warm-up time 10 min.

Interrupt controller Scan process complete

A/D converter data buffer: not empty, half full, full

Sampling By software from processor board

By external signal

Simultaneous





Power supply +12 V ±5%, 350 mA

-12 V ±5%, 280 mA

+5 V ±5%, 1.5 A

1)
2)
392
2016

Introduction
Order Information

DS2003 Multi-Channel A/D Board DS2003

Application Fields
RTI


CP2003

Software
Block Diagram for DS2002
PHS Bus
Processor
Board
I/O Boards Multi-Channel A/D Board
PHS-Bus
Interface
Barrel
Shifter
Hardware
A/D 2
Setup A/D 1
Register
Channels
Power Short 17 ... 32
Supply Cycle
Interrupt
Controller Channels
Range 1 ... 16
S/H 16 to 1
16-bit ADC Select MUX
Start of
Conversion
Generator
Channel Power
Select
Engineering
Supply
Register
DS2002
ISA Bus PC
393
2016


Processor
Multi-Channel A/D Board PHS Bus Board I/O Boards
PHS-Bus Control
Interface
Ext. trigger
Start
Scanning
Register
A/D 2
Scan A/D 1
Table
Power Short
Supply Cycle
Buffer
Channels
1 ... 32
Range 32 to 1 S/H
16-bit ADC Select MUX
Setup
Register
Interrupt Power
Controller Supply
DS2003
ISA Bus PC
394
2016

Introduction

The Real-Time Interface (RTI) board libraries for
the A/D boards provide blocks that implement
Application Fields
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.
Software
Hardware
Engineering
395
2016

Modular Hardware / DS2004 HighSpeed A/D Board
DS2004 HighSpeed A/D Board

Fast and precise A/D board
Highlights
16 high-speed differential A/D channels

16-bit resolution and 800 ns conversion time

Extensive trigger functions

Key Benefits Application Areas

Each of the DS2004‘s 16 channels has an independent The DS2004‘s triggered sample mode can be used to record
A/D converter with a resolution of 16 bits and differential data within a defined window based on trigger events. For
inputs. The conversion time is 800 ns per channel. Four example, angle-synchronous measurements of a combustion
external trigger lines, extensive trigger functions and on- engine can be started by an external software trigger.
board sample buffers enable single measurement as well as Possible applications include cylinder pressure-based control
burst conversion. The board buffers up to 16,384 values per and the measurement of knock signals in an angle window.
channel and then transfers them to the processor board as
a burst. This reduces the communication overhead and
improves the overall system performance.
Two Burst Modes Using Real-Time Interface

The DS2004‘s burst mode offers two ways of converting The Real-Time Interface (RTI) libraries for the A/D board
measurement values: provide RTI blocks that allow you to implement the function-
Continuous sample mode: When one burst of ality and I/O capabilities of the board in Simulink® models.
conversions ends, the next burst starts automatically. The RTI blocks can be added to a Simulink model via
The conversion of individual measurement values drag & drop.
within a burst is triggered by software, an internal
timer, or an external trigger.
Triggered sample mode: A burst of conversions can
be started by software or a trigger event.
396
2016

Modular Hardware / DS2004 High-Speed A/D Board
Introduction
Technical Details
General 16 A/D input channels (differential)

16 independent A/D converters

16-bit resolution

0.8 µs ... 1 s trigger interval (adjustable)

±5 V or ±10 V input voltage range (programmable for each channel)

±12 V input voltage working range

Application Fields
4 external trigger input lines

A/D Channels1), 2) Conversion time 800 ns

Initial offset error ±1 mV

Initial gain error ±0.1% of FSR

Input offset drift ±2 ppm of FSR/K





SNR (signal-to-noise-ratio) ≥+85 dB (at 10 kHz, 10 V range)

≥+83 dB (at 10 kHz, 5 V range)

Software
THD (total harmonic distortion) ≤-85 dB (at 10 kHz, 10 V range)

≤-83 dB (at 10 kHz, 5 V range)

Channel crosstalk ≤-95 dB

≥+85 dB (at 10 kHz signal frequency)
CMRR (common mode rejection ratio)

Input overvoltage protection ±50 V continuous, ±60 V for up to 10 s

Interrupt controller Burst start

Data ready

Data lost

Conversion trigger overflow

Hardware
External trigger Input voltage CMOS level

input Input overvoltage protection ±50 V continuous, ±60 V for 10 s



Characteristics Ambient temperature 0 … 55 ºC (32 … 131 ºF)

Power supply +5 V ±5%, max. 1.5 A

+12 V ±10%, 1.5 A

1)
2)

DS2004 High-Speed A/D Board DS2004



RTI


CP2004

397
2016

Modular Hardware / DS2004 High-Speed A/D Board
Block Diagram
PHS bus Processor

board I/O boards
16
...
PHS-bus 1
interface Swinging buffer
Free buffer
Differential
A/D converter Signal
Free buffer Write buffer unit conditioning input
External trigger 1
IRQ controller Buffer .
control unit Trigger .
unit .
External trigger 4
ADC
timer
Power supply
DS2004
ISA bus PC
398
2016

Modular Hardware / DS2101/DS2102/DS2103 D/A Boards
DS2101/DS2102/DS2103 D/A Boards
Introduction
Fast D/A boards
Highlights
Application Fields
D/A boards with various resolutions, channel numbers,

and speeds
Up to 32 channels, resolution up to 16 bit

Minimum settling time of 1.6 μs

Software
D/A conversion is required by many rapid control prototyp- The D/A boards provide various channel numbers, resolu-
ing applications to provide the control signal for actuators. tions, and speeds for you to choose from. The table below
In the other direction, in hardware-in-the-loop applications, gives you an initial overview. All three boards can be con-
sensors that provide analog signals have to be simulated. figured from Simulink® with Real-Time Interface. You can
select the voltage range for each channel individually.
Hardware
Comparing All Three Boards
Board 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
1)
Engineering
399
2016

DS2101 D/A Board

Technical Details
General 5 parallel D/A converters

12-bit resolution

±5 V, ±10 V or 0 ... +10 V output voltage range (programmable)

Reset to 0 V on I/O error (programmable)

D/A channels 1), 2) Settling time 3 µs typ. (4 µs max.) to ±0.01% of FSR (full-scale range)

1 µs typ. at major carry

Output current ±5 mA max.

Output impedance 0.3 Ω

Offset error < 3 mV

Gain error < 0.1 %



Linearity error ±1/2 LSB

Differential linearity error ±3/4 LSB

Monotonicity Fully monotonic

Triggering By software from the processor board

Immediate output or simultaneous output

Physical connections 25-pin female Sub-D output connector



characteristics Ambient temperature 0 ... 70 ºC (32 ... 158 ºF)


1)
2)
Typical values at 25 °C and ±10 V output voltage range (FSR = full-scale range).
Order Information

DS2101 D/A Board DS2101


RTI


CP2101

400
2016

Introduction
DS2102 High-Resolution D/A Board
Technical Details

16-bit resolution

±5 V, ±10 V or 0 ... +10 V output voltage range (programmable)

Application Fields
Reset to 0 V on I/O error (programmable)

D/A channels1), 2) Settling time Board revisions DS2102-01 … DS2102-043):
Deglitcher disabled: 1.3 µs to ±0.025% of FSR (full-scale range)
Deglitcher enabled: 2 µs to ±0.025% of FSR
Board revision DS2102-053):
1.6 µs to ±0.025% of FSR
Offset error ±1 mV

Gain error 0.05%



Linearity error ±2 LSB
Software

Differential linearity error ±4 LSB

Monotonicity 14 bits

THD (total harmonic distortion) -90 dB (at 10 KHz)


Immediate output or simultaneous output





Hardware
Power supply +5 V ±5%, 3.3 A (DS2102-01 ... DS2102-04)

+5 V ±5%, 1.6 A (DS2102-05)

±12 V ±5%, 50 mA

1)
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 DS2102-
05, the DS2102 uses D/A converters with reduced output spikes.
Order Information
Engineering
DS2102 High-Resolution D/A Board DS2102



RTI


CP2102

401
2016

DS2103 Multi-Channel D/A Board

Technical Details

14-bit resolution

±5 V or ±10 V ouput voltage range (programmable)

Reset to 0 V on I/O error (programmable)

D/A channels1), 2) Settling time 10 µs to ±0.012% of FSR (full-scale range)


Offset error ±1 mV




Differential linearity error ±1 LSB

Monotonicity 14 bits

THD (total harmonic distortion) -92 dB (at 10 kHz)


Immediate output or simultaneous update in groups of four channels






±12 V ±5%, 50 mA

1)
Typical values at 25 °C and ±10 V output voltage range.
2)
Order Information

DS2103 Multi-Channel D/A Board DS2103


RTI


CP2103

402
2016

Introduction
Processor
PHS Bus Board
I/O Boards
D/A Board
PHS-Bus
Application Fields
Interface D/A 5
D/A 4
D/A 3 Ch. 5
D/A 2
Setup Ch. 4
Register D/A 1
Ch. 3
Ch. 2
Auto-Zero Range
Circuit 12-bit DAC Ch. 1
Select
Power
Supply
DS2101
Software
ISA Bus PC

PHS Bus Processor
Board I/O Boards
High-Resolution D/A Board
Hardware
Calibration
PHS-Bus D/A 6
Interface D/A 5 Ch. 6
D/A 4
D/A 3 Ch. 5
D/A 2
Setup D/A 1 Ch. 4
Register
Ch. 3
EEPROM DAC
Ch. 2
Auto-Zero Range Ch. 1
Circuit 16-bit DAC
Select
Power
Supply Engineering
DS2102
ISA Bus PC
403
2016


Multi-Channel D/A Board PHS Bus Processor
Board I/O Boards
PHS-Bus
Interface D/A 8 Channels
D/A 7
D/A 6 29...32
D/A 5 25...28
Scan
Table D/A 4 21...24
D/A 3 17...20
D/A 2 13...16
D/A 1 9...12
Range
Register
14-bit 14-bit 5...8
DAC DAC
1...4
14-bit 14-bit
Strobe DAC DAC
Register
Mode
Register
Auto-Zero Power
Circuit Supply
DS2103
ISA Bus PC
404
2016

Introduction
The Real-Time Interface (RTI) board libraries for the D/A blocks can be added to a Simulink model via drag & drop.
boards provide blocks that implement the functionality and The blocks can be configured using their setup masks.
I/O capabilities of the boards in Simulink® models. The RTI
Application Fields
Software
Hardware
Engineering
405
2016

Modular Hardware / DS2202 HIL I/O Board

I/O hardware with signal conditioning for 12 V, 24 V, and 48 V automotive systems
Highlights
Ideally suited to body electronics, transmission,

and component tests
Lower-cost alternative to DS2211 HIL I/O Board,

without signal processor and angular processing unit
High number of analog and digital channels

Key Benefits Building an HIL Simulator

The DS2202 HIL I/O Board has been designed for hardware- Together with a processor board (DS1005, DS1006 or
in-the-loop simulation in automotive applications, and is DS1007), the DS2202 HIL I/O Board constitutes the hardware
tailored to the simulation and measurement of automotive core of dSPACE Simulator. While the DS2202 measures and
signals. The board contains signal conditioning for typical generates the signals required, the processor board performs
signal levels of 12 V, 24 V, and 48 V automotive systems the calculation of the real-time model. Communication
and supports 2-voltage systems. Typical use cases are body between the processor board and the I/O board runs via the
electronics, transmission, and component tests performed peripheral high-speed bus (PHS++ bus). The DS2202 can
by automotive suppliers, or as an additional HIL I/O board be used in dSPACE Simulator Mid-Size (p. 520) and Full-Size
in large powertrain and vehicle dynamics HIL applications. (p. 524).
406
2016

Introduction
Technical Details
A/D channels Channels 16 differential A/D channels (multiplexed)

Resolution 14 bit

Conversion time1) 1.1 µs per channel

Input voltage range 0 … 60 V, differential inputs

Offset error ±10 mV

Application Fields
Gain error ±0.5 %

Input impedance >1 MΩ

D/A channels Channels 20 D/A channels with individual ground sense line

Output voltage range 0 … 10 V (with internal reference, or ratiometric with 5 … 10 V external

reference)
Sense
lines allow differential outputs with DACx2) output swing -10 V ... +12 V
from system ground
Resolution 12 bit

Settling time 20 µs (full scale to 1 LSB)

Output current ±5 mA

Offset error ±5 mV

Software
Gain error ±0.5 % (with internal reference)

Digital inputs Channels Max. 24 PWM measurement inputs (shared with digital inputs),

up to 50 ns resolution, 0.01 Hz … 100 kHz
Max. 38 digital inputs (24 inputs shared with PWM inputs)

PWM measurement input channels can also be used for frequency

measurement
Input voltage 0 … +60 V

Threshold voltage level 1 V … 23.8 V

Input impedance 390 kΩ

Digital outputs Channels 16 digital outputs

Hardware
9 PWM outputs, resolution 16 bit, 0.01 Hz … 100 kHz, push/pull outputs

PWM outputs can also be used for square wave signal generation

External supply voltage +5 V … +60 V

Supplied from two independent rails (VBAT1 and VBAT2)

2-voltage support for digital outputs, selectable pin-wise

Output current range Max. ±50 mA

Vout high, min. (VBATx – 1.2 V) at +50 mA

Vout low, max. 0.4 V at -50 mA

Interfaces Serial interface Configuration TL16C550C single UART (universal asynchronous receiver and transmitter)

RS232, RS422 compatibility
Engineering


Up to 1 MBd (RS422)

CAN bus interface Configuration 2 CAN channels based on ST10F269 microcontroller

ISO DIN 11898-2 CAN High-Speed standard

Baud rate Max. 1 MBd

Physical connections I/O
connection via 2 x 100 pin high-density connectors and a 50-pin female
Sub-D connector

1)
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.
407
2016

Technical Details

characteristics Requires three brackets

Ambient temperature 0 … 55 ºC (32 … 131 ºF)

Power supply From host PC/expansion box +5 V ±5%; 1 A (without load on power supply outputs on output connector)

+12 V ±5%; 0.15 A (typ.), 0.3 A max. (with load on all analog outputs)

-12 V ±5%; 0.15 A (typ.), 0.3 A max. (with load on all analog outputs)

VBAT Two VBAT rails (5 V … 60 V DC)

Each rail (VBATx): 0.05 A + load current on digital outputs

VBATx has to be supplied from an external source

Order Information

DS2202 HIL I/O Board DS2202

Relevant Software

RTI

Optional RTI CAN Blockset (p. 71)
RTICAN_BS

RTICANMM_BS

408
2016

Introduction
Block Diagram
PHS bus Processor board I/O boards
Sensor and
actuator interfaces
PHS-bus ADC
interface interface
Application Fields
DAC
interface
Bit I/O unit
PWM unit
CAN
Software
subsystem
Serial
interface
Communication
Power interface
supply
DS2202
ISA bus PC
Hardware
Engineering
409
2016


Central I/O board for hardwareintheloop simulation
Highlights
Highlights
Simulates and measures all engine signals

(for up to 8 cylinders)
Signal conditioning for signal levels of 12 V,

24 V, and 48 V automotive systems; support of
2-voltage systems
Ideally suited for engine, powertrain,

and vehicle dynamics applications
Key Benefits Building a HIL Simulator

The DS2211 HIL I/O Board is the central I/O board for hard- Together with a processor board (the DS1005, DS1006 or
ware-in-the-loop simulation, especially in the field of auto- DS1007), the DS2211 HIL I/O Board constitutes the hardware
motive electronics. The DS2211 HIL I/O Board is tailored to core of dSPACE Simulator. The processor board performs
the simulation and measurement of automotive signals, the calculation of the real-time model, for example, of an
particularly for engine and vehicle dynamics applications, engine, while the DS2211 measures and stimulates all the
and combines a variety of typical HIL I/O signals on one required I/O signals. The simulator can be expanded from
board. The board contains signal conditioning for typical 8-cylinder up to 96 cylinders by using two or more DS2211
signal levels of 12 V, 24 V, and 48 V automotive systems HIL I/O Boards.
and supports 2-voltage systems.
Angular Processing Unit Angle-Synchronous Cascading

The DS2211 HIL I/O Board features a unique angular For tougher I/O requirements, several boards, for example,
processing unit which supports high-speed generation and several DS2211s, can be cascaded. The boards operate
measurement of crank angle-related signals to simulate angle-synchronously if their time base connectors are con-
engines up to 29,000 rpm. nected. 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-syn-
chronously on several boards. The same applies to the
DS4002 Timing and Digital I/O Board (p. 428), the DS5001
Digital Waveform Capture Board (p. 452), and the DS5203
FPGA Board (p. 462), which can all be connected to the
time base, too.
See p. 414 for an application example.
410
2016

Introduction
Technical Details
General Angular
processing unit (APU) to handle all crankshaft-angle-related signals (ignition,
injection, crankshaft, camshaft, etc.)
Simulation of crankshaft sensors that detect the direction of rotation

1 crankshaft signal output (programmable analog and digital waveforms)

Max. 4 camshaft signal outputs (2 with programmable analog and digital output plus

2 with digital output only, shared with 2 digital outputs)
Application Fields
Complex comparator functionality support for ignition and injection signals

Support for the SAE standard J2716 (SENT)

Time-base connector

Slave processor DSP (digital signal Texas Instruments TMS320VC33 floating-point DSP

processor) 150 MFLOPS

13.3 ns cycle time

Interrupt controller 6 angle position interrupts (can be set at any engine position in 0.01 degree increments)

1 CAN controller interrupt

1 serial interface (universal asynchronous receiver and transmitter) interrupt

Angular processing unit (APU) Angular resolution 0.011° crank angle

Speed range ±29,000 rpm

Speed resolution 0.112 rpm
Software

A/D channels Channels 16 differential A/D channels (multiplexed)

Resolution 14 bits

Conversion time1) 1.1 µs per channel

Input voltage range 0 … 60 V, differential inputs

Offset error ±10 mV

Gain error ±0.5 %

Input impedance > 1 MΩ

D/A channels Channels 20 D/A channels with individual ground sense line

Output voltage range 0 … 10 V (with internal reference, or ratiometric with 5 … 10 V external reference)

Hardware
Sense lines allow differential outputs with DACx2) output swing -10 V ... +12 V from

system ground
Resolution 12 bits

Settling time 20 µs (full scale to 1 LSB)

Analog outputs 1 crankshaft signal (angular processing unit)

2 camshaft signals (angular processing unit)

4-channel wheel speed or 4-channel knock signal generation (based on DSP); up to

8 knock signals per cycle
4 additional analog waveform outputs (from DSP, no sense line, ±10 V)


Engineering
Offset error ±5 mV

Gain error ±0.5 % (with internal reference)

Slave DSP DAC Settling time 10 µs (full scale to 1 LSB)

Output voltage range ±10 V


Transformer outputs Output voltage range ±20 V (transformer output mode)

±10 V (DC output mode)


1)
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.
411
2016

Technical Details
Resistive output channels Channels 10 channels

Topology 16-bit switched resistor ladder

Resistance range 15.8 Ω … 1 MΩ

Resistance error ±2% or ±3 Ω, whichever is greater, with RESx– pin within ±5 V of system ground

Voltage range Each terminal must stay within ±10 V of system ground


Power per channel Max. 250 mW

Digital inputs Channels 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
Max. 16 digital inputs (all inputs shared with PWM measurement inputs)

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
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
Max. 2 auxiliary capture inputs (all inputs shared with ignition inputs)

PWM measurement input channels can also be used for frequency measurement

Max. 4 SENT receive channels (revision SENT2010)

Input voltage 0 … +60 V

Threshold voltage level 1 V … 22.65 V or 23.8 V (dependent on I/O circuit)

Input impedance 390 kΩ

Digital outputs Channels Max. 16 digital outputs (2 pins shared with digital camshaft signal outputs)

9 PWM outputs, resolution 16 bit, 0.01 Hz … 100 kHz, push/pull outputs

PWM outputs can also be used for square wave signal generation

Max. 5 SENT transmit channels (revision SENT2010)

External supply voltage +5 V … +60 V

Supplied from two independent rails (VBAT1 and VBAT2)

2-voltage support for digital outputs, selectable pin-wise


Vout high, min. (VBATx – 1.2 V) at +50 mA

Vout low, max. 0.4 V at -50 mA

Interfaces Serial interface TL16C550C single UART (universal asynchronous receiver and transmitter)

RS232, RS422 compatibility

Up to 115.2 Kbaud (RS232)

Up to 1 Mbaud (RS422)

CAN bus interface 2 CAN channels based on ST10F269 microcontroller

ISO DIN 11898-2 CAN High-Speed standard

Max. 1 Mbaud

Physical connections I/O connection via 2 x 100 pin high-density connectors and a 50-pin female Sub-D

connector

Requires three brackets (for I/O connectors)

Physical characteristics Physical size 340 x 125 x 61 mm (13.4 x 4.9 x 2.4 in)

The board requires three brackets.


Power supply +5 V ±5%; 1.5 A

+12 V ±5%; 0.25 A typical (max. 0.5 A with load on all analog and transformer outputs)

-12 V ±5%; 0.2 A typical (max. 0.5 A with load on all analog and transformer outputs)

Two VBAT rails (5 V … 60 V DC)

Each rail (VBATx ): 0.05 A + load current on digital outputs

VBATx has to be supplied from an external source.

412
2016

Introduction
Order Information

DS2211 HIL I/O Board DS2211

Relevant Software
Application Fields
RTI

Optional RTI CAN Blockset (p. 71)
RTICAN_BS

RTICANMM_BS

Texas Instruments C3X/4X Code Composer (p. 111)
TMDS3240130

Block Diagram
Software
Further
DS2211s,
DS4002s, PHS bus Processor board I/O boards
DS5001s
Angular Sensor and

Engine Position Bus
processing unit actuator interfaces

Engine
position PHS-bus ADC
accumulator Interface interface
Hardware
Crankshaft DAC
signal interface
generator
Camshaft Resistance
signal simulation
generators
Ignition Bit I/O unit

capture
Injection PWM unit
Engineering
capture
DSP CAN
subsystem subsystem
Serial
interface
Communication
interface
Power
supply
DS2211
ISA bus PC
413
2016

Programming from MATLAB®/Simulink®/Stateflow®
Programming and connecting to I/O is simple with our Real-Time For connection to the CAN bus, for example, the optional
Interface (p. 56), which enables you to program all your I/O RTI CAN Blockset extends Real-Time Interface for easy,
graphically in Simulink, even the angular processing unit. graphical CAN configuration from Simulink. The blockset
comprises CAN controller configuration and dialog-based
parameterization of messages in receive and transmit modes
(p. 71).
Application Example: Simulating a 12-Cylinder EVT Engine

The Challenge: Immense I/O Cascading Several I/O Boards
HIL simulation of a 12-cylinder, 48-valve engine with an The DS2211 HIL I/O Board is designed to be the heart of
electromagnetic valve train (EVT) is a real challenge, espe- such applications. The hardware can be cascaded via the
cially as regards I/O. The engine ECU generates 12 injection Engine Position Bus, with further boards operating angle-
signals plus 12 ignition signals. In addition, 4 valve signals synchronously. In this case, the dSPACE Simulator hardware
are needed for each of the 12 cylinders to control the consists of a further DS2211 and three DS5001 Digital
electromagnetic valve actuators. This means that if the Waveform Capture Boards. The DS2211s are ready to cap-
engine is simulated, 72 signals generated by the ECU have ture injection and ignition signals of 6 (up to 8) cylinders
to be captured – angle-synchronously. 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
DS5001 Injection signals
Engine Position Bus
(Slave) 12
signal capturing is a rail pressure actuator for direct injection
gasoline engines.
DS5001 Injection signals
(Slave) 12
DS5001 Valve train signals

(Slave) ECU
48
DS2211 Crankshaft signal

(Slave)
DS2211
(Master)
.
.
.
414
2016

Introduction
Application Example: HIL Simulation of a 6-Cylinder Engine
A HIL System with Just Two Boards Engine Position Based Signal Generation
Together with a processor board (the DS1005, DS1006 or The processor board performs the calculation of an engine
DS1007), the DS2211 provides a compact, yet powerful model and sends all the calculated engine data to the
dSPACE Simulator for hardware-in-the-loop simulation, for DS2211 (for example, engine speed, camshaft phase, and
example, for function or system testing. engine knock parameters). The DS2211 processes this data
with an engine position accumulator that constantly calcu-
Application Fields
lates the engine position according to the current engine
speed. With a 16-bit angle resolution and an engine speed
resolution of 0.112 rpm, this engine position is the basis for
all further signal generation.
Processor Board
Speed Engine Position Crankshaft Signal Crankshaft Signal

Accumulator Generator
Software
Camshaft Signal Camshaft Signal
Camshaft Phase Generator
Engine
PHS Position Knock Signals
Bus Knock Parameters Bus VC33 DSP ECU
Ignition Ignition Signals

Spark Advance Capture
Injection Injection Signals

Injection Angles Capture
Hardware
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 ECU’s reactions to the
Engineering
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.
415
2016

Modular Hardware / DS2302 Direct Digital Synthesis Board
DS2302 Direct Digital Synthesis Board

Powerful board for realtime and highaccuracy signal generation
Highlights
Flexible sensor signal simulation with up to 6 channels

Fast analog output on up to six 16-bit DACs

APU (angular processing unit) slave interface for each

channel

The DS2302 enables you to simulate complex sensor signal To test an ECU to its limits, even interferences such as noise
waveforms for testing electronic control units (ECUs). The or spikes often need to be simulated. For example, in auto-
board was redesigned and equipped with a faster processor, motive hardware-in-the-loop applications, signals such as
and is compatible with its earlier version. It meets tough crankshaft or camshaft pulses have to be generated as
requirements regarding complexity, flexibility and resolution. angle-based for the greatest accuracy. Signal variables, such
The DS2302 is equipped with six DSPs and designed for as engine speed, must be modified in real time. The Fast
fast, flexible waveform generation. It computes each signal Analog Capturing Module (p. 418) is used to capture injec-
sample just-in-time and outputs it immediately. The signal tion control voltage and calculate the injection quantity for
parameters can easily be changed on-the-fly by a master piezo actuators of SI engines.
processor board. The DS2302 C functions allow you to
exchange data between your main application and an ap-
plication running on one of the six DSPs. Communication
runs via the dual-ported memories of the DS2302.
416
2016

Introduction
Technical Details
General 6 independent direct digital synthesis channels

Processor Digital signal processor (DSP) Texas Instruments TMS320VC33 floating-point DSP

150 MFLOPS

13.3 ns cycle time

Memory Dual-port memory (DPMEM) 16 K x 32-bit true dual-port RAM per channel

Used for program download and to read/write parameters (e.g., for communi

Application Fields
cation between DSPs)
DSP interrupts On-board I/O (e.g., timer or DMA), external, other DSP channels

Interrupt controller One interrupt to PHS-bus master per DSP channel

Plug-on modules Plug-on DAC module (optional) (p. 418)

Plug-on ADC module for fast analog capturing (optional)

Digital I/O Voltage range TTL input/output levels

Output current Max. -800 µA/+1.5 mA

Further details 7 digital I/O lines per DSP

Programmable as input or output

One line programmable as external interrupt input

APU (angular processing unit) slave interface for each channel

Software
Physical connections 44-pin female high-density Sub-D output connector



Power supply +5 V ±5%, 4.0 A (with 6 DAC modules inserted)

Order Information
Hardware
DS2302 Direct Digital Synthesis Board DS2302


Required Texas Instruments C3X/4X Code Composer
TMDS3240130

Engineering
Real-Time Interface (p. 56)
RTI


Optional Connector panel for DS2302 (p. 504)
CP2302

417
2016

Block Diagram
PHS Bus Processor
Board I/O Boards
PHS-Bus APU
PHS-Bus
Interface Interrupt Slave
Controller Interface
Channel 6
Interrupt Channel 5 Analog
Select In/Out
Register Channel 4
Channel 3 Digital
Channel 2
I/O
..
Address
Channel 1 ..
Register Plug-On Analog
VC33
16K x 32
DSP
Module In/Out
DPRAM
150 MHz Digital
I/O
Setup
Register
Data
Register
DS2302
DAC Module
General One D/A converter per channel

16-bit resolution

Reset on I/O error (programmable)

Analog output Voltage output range ±10 V

(typical values at 25 °C) Output current Max. ±5 mA

Initial offset error ±1 mV

Offset drift ±10 ppm of FSR/K (FSR = full scale range)

Initial gain error ±0.5%


Settling time 0.8 µs typ. at ±0.012% of FSR

Slew rate Approx. 25 V/µs

Differential linearity error ±1 LSB (least significant bit)

Monotonicity 14 bit

Total harmonic distortion -90 dB (at 10 kHz)


Ambient temperature 0 … 70 °C (32 … 158 °F)

Power consumption 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 calcu-
late injection quantity for piezo actuators of SI engines.
418 1)
The Fast Analog Capturing Module is an additional I/O solution for the DS2302 Direct Digital Synthesis Board. It is neither
2016 part of the dSPACE product range, nor part of any dSPACE releases. For more information, please contact dSPACE.

Introduction
Hardware Details Software Details
16-bit resolution
Integration (Euler) on DS2302 slave DSP in 8 ... 10 µs

1 megasamples per second sampling rate
Threshold values for starting and stopping computation

2 channels
included
±10 V input range
Capture of n injection pulses (currently n=3 per cylinder)
Optional external trigger input
per 720° crankshaft revolution
Values provided to the master via dual-port memory

Application Fields
Generating Signals
Common Signals
Software examples are included with the DS2302 for most Crankshaft, camshaft, and knock signals

of these signal types: PWM

Sine-wave, square-wave and sawtooth Incremental sensor simulator

Gaussian noise and PRBS Fourier synthesis

Software
Typical Nontrivial Signals
Signal generation is based on algorithms, so there is virtu- Engine knock signals consisting of damped oscillation

ally no limit to the variety of waveform signals, including overlaid by random noise
interdependencies between several signals. This list therefore Digital pulses with variable logic levels

Hardware
includes just a small selection of what is actually possible: Interferences such as spikes with variable waveforms,

Sinusoidal wheel speed signals periods or amplitudes
Angle-based sinusoidal crankshaft and camshaft signals Nonstationary noise of variable noise color depending

Missing teeth on toothed crankshaft sensor wheels on engine speed or type
Non-angle-equidistant pulses with stochastically Time-variant Fourier synthesis, i.e., for simulating

disturbed edge positions engine sound
Real-Time Interface Engineering
The DS2302 Simulink® read/write blocks and dialogs
provided by Real-Time Interface allow convenient param-
eter updates via the on-board dual-port memories.
419
2016

Programming the DS2302

Host PC
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
Compiling +
channel can run its own signal generator program. Channels Speed Optimization
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 MATLAB/Simulink +
are utilities for execution time measurement and optimization. Real-Time Interface
Downloading an Application
Indirect Download
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
processor board to the DS2302 by using dSPACE’s Real-Time
Interface from your Simulink block diagram. PHS bus
DS2302
Controlling the DS2302

Simulink
Controlling via Simulink block diagram
The variables controlling signal generation, such as the
engine speed for a crankshaft signal, can be updated con- Read/Write
Variables
tinuously via the master processor board, for example, from
your Simulink block diagram. Processor Board
Master Application
DS2302
Signal Generation
Use Cases
Sensor Simulation
Simulating Sensor Signals
The simulation of crankshaft, camshaft, and knock signals simulated signals therefore have to meet rigorous quality
plays an important role in HIL applications for testing engine requirements. For example, a 0.1° angle resolution for the
or powertrain control units. The ECU uses these signals to crankshaft requires a 2.8 µs timing resolution at a speed of
determine the proper injection and ignition timing. The 6,000 rpm.
420
2016

Introduction
Crankshaft, Camshaft, and Knock Signal Simulation
Application Areas Testing an Engine ECU
The DS2302 board is ideally suited for simulating crankshaft, While crankshaft and camshaft signals mainly depend on
camshaft and knock signals. Channel 2 generates the sinu- the engine speed calculated by the processor board, the
soidal crankshaft signal, including the gap for the two knock signal also depends on various other parameters. To
missing teeth in the sensor wheel. This channel also com- test the engine ECU under different conditions, simply
putes the triggers for the camshaft pulses and the knock change the engine type or introduce noise or spikes – all
Application Fields
signal, which are generated in channels 1 and 3. The knock on-the-fly.
signal basically consists of damped oscillation, overlaid by
speed-dependent random noise.
To Processor Board
Engine Speed
DP-RAM 1 DSP 1
Camshaft
PHS Bus or ISA Bus
Software
Engine Speed
DP-RAM 2 DSP 2
Crankshaft
Engine Speed
DSP 3
DP-RAM 3
Knock Signal
Knock
Parameters
Hardware
Simulating Angle-Based Sensor Signals
Precise Sensor Simulation
In many applications, precise sensor simulation requires engine model. Each time a certain angle is reached, a pulse
the generation of angle-based sensor signals. To get the edge is generated. The fast on-board DSPs make it possible
angle of a crankshaft, for example, the DS2302 board can to check the crankshaft angle on a microsecond basis, thus
autonomously integrate the engine speed coming from an providing an extremely high resolution.
Engineering
Angle-based signals
421
2016

Modular Hardware / DS2401 Resistive Sensor Simulation Board
DS2401 Resistive Sensor Simulation Board

For simulating resistive sensors
Highlights
4 resistance output channels

10 Ω to 500 kΩ resistance range

Channels individually insulated from system ground


In hardware-in-the-loop applications, the simulation of sen- The DS2401 features four resistance output channels of
sors plays an important role. While many sensors provide identical structure. All channels are insulated from system
voltages or currents, others have a resistance output – for ground individually. The application running on the proces-
example, thermistors or resistance temperature detectors sor board writes the desired resistance to the DS2401 board,
(RTDs) for temperature measurement. To simulate these and the resistance is then simulated electronically between
resistive sensors, precise resistance values must be provided. the two output pins of that channel.
Block Diagram
PHS Bus Processor
Board I/O Boards
Resistor Channel 4
PHS-Bus
Interface Resistor Channel 3
Resistor Channel 2
Resistor Channel 1
12-bit
Opto Multiplying D/A Default
Isolation Converter Resistance CH4
CH3
CH2
Power Insulated Current Sense Overload
Supply Power Supply & Ranging Protection CH1
DS2401
ISA Bus PC
422
2016

Modular Hardware / DS2401 Resistive Sensor Simulation Board
Introduction
Technical Details
General 4 simulated resistors

12-bit resolution

Default resistance output during power-down (determined by external resistor)

Overload relay state output

Resistor terminals Resistance range 10 Ω ... 500 kΩ total resistance range (programmable)

Automatic range switching for each channel (by software): 10 Ω ... 250 Ω, 200 Ω
... 5 kΩ,
Application Fields
2 kΩ ... 50 kΩ, 20 kΩ ... 500 kΩ
Cutoff frequency (-3 dB) 15 kHz (10 kHz at R > 50 kΩ)

Settling time to 1% 50 μs

Voltage across resistor Max. ±20 V

Load current Max. ±20 mA

Initial offset voltage error ±5 mV (typ.)

Initial resistance error ±0.5% + 0.5 Ω (typ.)

Total linearity error ±2 LSB

Monotonicity 12 bit

Offset drift ±100 μV/K

Software
Resistance drift ±40 ppm/K

Noise voltage 10 mVrms (at 1 kΩ)

Isolation All channels individually insulated from system ground

Overload relay state Voltage output range TTL

outputs Output current Max. -0.4 mA/+4 mA

DEF_EN output Voltage output range TTL

Output current Max. -0.4 mA/+20 mA

Triggering By software from master processor board; immediate output or simultaneous update


Hardware


characteristics Ambient temperature 0 ... 70 °C (32 ... 158 °F)


+12 V ±5%, 1 A

Order Information
Engineering
DS2401 Resistive Sensor Simulation Board DS2401

Relevant Software

RTI

423
2016

Modular Hardware / DS3001/DS3002 Incremental Encoder Interface Boards
DS3001/DS3002 Incremental Encoder Interface Boards

Essential for precise position control
Highlights
Up to 6 incremental encoder interface channels

24- or 32-bit position counters

Measuring digital or sinusoidal position signals

Key Benefits for DS3001 Key Benefits for DS3002

The DS3001 is designed for position control applications If digital encoder information cannot provide the desired
with sensors providing digital phase information. It composition accuracy, or if you want to employ encoders with
prises five parallel input channels, each providing everything fewer lines, sinusoidal position sensor signals can increase
needed to connect an incremental encoder and process its accuracy and resolution significantly. The DS3002‘s six chan-
output signals: a regulated encoder power supply with sense nels capture sinusoidal encoder signals and subdivide them
lines, differential or single-ended inputs for the encoder’s up to 4096 times. Each channel has its own 32-bit position
two phase lines, and an index input. counter that can also be used for digital signals.
Main Differences Between DS3001 and DS3002
DS3001 DS3002
Number of channels 5 6
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
424
2016

Introduction
DS3001 Incremental Encoder Interface Board
Technical Details
General 5 independent incremental encoder interface channels

Differential inputs for encoder phase lines and an index line on each channel

Encoder power supply lines

Application Fields
Interrupt on index

Four-stage digital filter

Interrupt controller 5 index interrupts (one for each channel)

Encoder signal types Digital signals: single-ended (TTL) or differential (RS422)

Selectable individually for each channel

Minimum index pulse width 200 ns

Position counters 24-bit counters

Max. 1.25 MHz input frequency, i.e., fourfold pulse count up to 5 MHz

Counter reset via hardware or software (asynchronous via PHS bus, synchronous via index-

pulse once or always)
Encoder power supply lines 5 V, 200 mA max. per channel

Voltage regulation with sense lines

Software
Index detection Separate index signal for each channel, via interrupt (edge-triggered) or flag (polling mode,

level-triggered)
Index signal can be used for counter reset

Encoder interface 150 Ω in series with 4.7 nF input impedance (RS422)

200 mV min. differential input voltage (differential mode only)

5 V max. common mode input voltage (differential mode only)

200 ns minimum encoder state width (programmable)

9.6 ms max. noise pulse width (programmable)

200 ns minimum index pulse width

Physical connections 50-pin female Sub-D input connector

Hardware




+12 V ±5%, 1.2 A

-12 V ±5%, 150 mA

Order Information
Engineering
DS3001 Incremental Encoder Interface Board DS3001


RTI


CP3001

425
2016

DS3002 Incremental Encoder Interface Board

Technical Details
General 6 independent incremental encoder interface channels

Differential inputs for encoder phase lines and an index line on each channel

Synchronized sampling of multiple channels

Encoder power supply line per channel

On-board line termination

Connector for measuring pulse widths and frequency of count/index pulses with other I/O

boards, e.g., DS5001
Encoder signal types Sinusoidal signals: 11 µApp differential or 1 Vpp differential

Digital signals: single-ended (TTL) or differential (RS422)

Selectable individually for each channel

Minimum index pulse width 250 ns

Position counters 32-bit counters

Max. 750 kHz input frequency, i.e., fourfold pulse count up to 3 MHz

Counter reset or preload via software or automatically on index pulse

Encoder power supply lines 5 V, 200 mA max. per channel

Voltage regulation with sense lines

Input performance ADC 12-bit resolution

800 ns data conversion time, 10 MSPS (pipelined)

Offset error (PHI0, PHI90) ±4 mV for 1 Vpp (±0.08 % position error)

±75 nA for 11 µApp (±0.14 % position error)

ADC nonlinearity ±0.06 % resulting position error

No missing codes

Gain match (PHI0, PHI90) ±0.25 % (±0.025 % position error) of 1 Vpp

±0.6 % (±0.06 % position error) of 11 µApp

Common mode rejection ratio (PHI0,
±2.5 mV/V (±0.05 %/V position error) each channel
PHI90 in 1 Vpp mode only)
Sinusoidal signal capture Up to 4096 subdivisions between two encoder lines

Position calculation on processor board (look-up tables and interpolation)

Physical connections 62-pin female Sub-D input connector





+12 V ±5%, 200 mA plus 200 mA for each channel in use

Order Information

DS3002 Incremental Encoder Interface Board DS3002


RTI


CP3002

426
2016

Introduction
How to Measure Encoder Signals
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
Application Fields
stores the current value. The count direction depends on
the encoder‘s rotation direction. The counter is initialized
from the processor board or by means of the encoder‘s
index pulse. With the DS3002, sampling of count values
can be synchronized over multiple channels.
Measuring Sinusoidal Signals

The DS3002 board supports 11 µApp signals as well as 1 Vpp
signals. With sinusoidal encoder signals, you can achieve a
Software
much higher resolution than with digital signals.
The DS3002 board measures the analog values of the sinu-
soidal 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.
Hardware
Block Diagram
PHS Bus Processor
Board I/O Boards
Channel 6
PHS-Bus
Interface Channel 5
Channel 4
Channel 3
Channel 2
Channel 1
Start of Sensor
Conversion Power
Index
Engineering
32-bit
Position
Counter Phase
Register Decoder
32 bit
+ 12-bit Phase 2
12 bit ADC
+
12 bit 12-bit Phase 1
ADC
Power
Supply
DS3002
ISA Bus PC
427
2016

Modular Hardware / DS4002 Timing and Digital I/O Board
DS4002 Timing and Digital I/O Board

Generating and capturing digital signals
Highlights
Captures digital signals for parameter measurement

Generates flexible pulse patterns

Comprehensive set of standard applications included


The DS4002 Timing and Digital I/O Board combines a The DS4002 Timing and Digital I/O Board is ideally suited
variety of digital I/O tasks on one board. It provides the to all kinds of hardware-in-the-loop simulations and rapid
functionality you expect from an ordinary digital I/O board control prototyping. It captures digital signals for the mea-
plus additional features that help you perform specific con- surement of parameters such as frequency or phase, and
trol tasks easily. Eight channels can be programmed for generates digital signals such as PWM pulses to control
either capturing digital signals or generating flexible pulse actuators or simulate sensors. It also performs many digital
patterns. 32 additional I/O lines can be used for further I/O tasks, for example, controlling switches or displays.
digital I/O tasks, for example, to control single input lines A brief overview of applications:
(switches, sensors) or output lines (relays, displays).
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. 410).
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. 452, p. 456).
428
2016

Introduction
Technical Details
General 8 channels (timing I/O) with 200 ns resolution

Each channel individually programmable as input or output

Common 30 bit/200 ns time base

Fast dual-port RAM for data storage

32 additional digital I/O lines (TTL)


Application Fields
Time-base connector

Interrupt controller 1 read event interrupt

2 signal generation interrupts

Timing I/O Signal capture mode Time and polarity stored for each edge (time stamps)

Stores up to 512 30-bit time stamps per channel

Rising and/or falling edge detection programmable

Latchup protection

Interrupt to master processor after predefined number of edges

Minimum pulse widths: see table on p. 430

Signal generation mode Signals described as a series of rising and falling edges

Stores up to 256 commands and 29-bit delay constants

Minimum pulse width: see table on p. 430

Software
All channels triggerable from channels 1 and 2

Interrupts programmable from channels 1 and 2

Loop counter

Update of time constants, output level, jump address, and loop counter during program execution

(swinging buffer mechanism)



Input/output frequency Max. 833 kHz (1 channel active)

Digital I/O Lines 32 lines with ESD (electrostatic discharge) protection:

24 lines input/output (programmable in 8-bit groups, as direct input, strobed input or output)
Hardware

4 lines fixed input mode

4 lines fixed output mode

1 strobe input

2 handshake lines for acknowledge and output ready

Direct and/or latched input mode

Used to control single input or output lines

Voltage range TTL input/output level

Output current Max. -64 mA/+16 mA

External trigger input 2 lines with TTL input level

Physical connections 50-pin female Sub-D connector

Engineering




Order Information

DS4002 Timing and Digital I/O Board DS4002

429
2016


Included C functions for accessing/controlling the DS4002
–
Required Real-Time Interface (RTI), (p. 56)
RTI


CP4002

Connector/LED Combi Panel for DS4002 (p. 504)
CLP4002

Minimum Pulse Widths1)

The table below shows the minimum pulse widths for dif-
ferent numbers of channels in use, which are the same for
Capture and Generation mode.
Channels Pulse Width Pulse Width

in Use (Capture Mode) (Generation Mode)
1 0.6 µs 0.6 µs
2 1.0 µs 1.0 µs
3 1.4 µs 1.4 µs
4 1.8 µs 1.8 µs
5 2.2 µs 2.2 µs
6 2.6 µs 2.6 µs
7 3.0 µs 3.0 µs
8 3.4 µs 3.4 µs
1)
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.
430
2016

Introduction
Block Diagram
PHS bus Processor
board I/O boards
PHS-bus Time base Time-base Further DS5001/

interface connector DS4002/DS2211
Application Fields
Dual-port
memory
Channel 8
.
.
.
Controller .
.
Timing I/O
unit Channel 1
Interrupt
controller
External
trigger
Software
Power Digital I/O unit
supply 32-bit
DS4002
ISA bus PC
Hardware
The DS4002 Simulink® blocks provided by Real-Time Inter-
face allow convenient control of all timing and I/O lines: bit
in, bit out, PWM, F/D, D/F, signal capture mode, and hard-
ware interrupt.
Engineering
431
2016

Creating Pulse Patterns in Generation Mode
You can create complex pulse patterns flexibly in Generation rupts to the master processor. In addition, all channels can
mode. Functions for the most common applications, such be controlled by two external trigger input lines. During
as PWM pulse pattern generation and square-wave signal program execution, the delay constants, output level, jump
generation, are included. Alternatively, you can program address, and loop counter can be updated synchronously
your own pulse patterns directly in C code. or individually per channel.
Channels 1 and 2 can trigger other channels and send inter-
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 evaluat-
ing 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 pre-
defined number of edges can trigger an interrupt to the
master processor.
432
2016

Modular Hardware / DS4003 Digital I/O Board
Introduction
Large number of digital I/O channels for various applications
Highlights
Application Fields
96 TTL lines (three 32-bit ports)

3 handshake control lines per port

2 interrupts per port plus one on I/O error

Software
Technical Details
General Release output for external release logic

I/O error monitor output and I/O error request input for error monitoring of external devices

Two customization module connectors (pinheaders) supporting digital I/O lines and power supply of two ports

Interrupt controller Interrupt sources Three user interrupts, one per port

Three strobe interrupts, one per port

One interrupt on I/O error

Voltage range TTL input level

Hardware
Digital I/O Lines provided by 32 I/O lines programmable in 8bit groups, usable as nonstrobed input, strobed input or output

each port One strobe input

Two handshake lines for acknowledge and output ready

Voltage range TTL input level

Output current 15 mA out (high, 2.4 ... 5 V), 24 mA in (low, 0 ... 0.8 V)

Input current 0.12 mA in (high, 2.4 ... 5 V), 0.2 mA out (low, 0 ... 0.8 V)

Physical connections Three 50pin male SubD connectors (three brackets required)

Host interface One 8 or 16bit ISA slot (power supply only)


Engineering
characteristics The board requires three brackets

Ambient temperature 0 ... 70 °C ( 32 ... 158 °F)

Power supply +5 V ±5%, 1.5 A (without customization modules/external loads)

Relevant Software and Hardware Order Information
Software Order Number Product Order Number

Required RealTime Interface (p. 56)

RTI


CP4003
Combined Connector/LED Panel for
CLP4003

DS4003 (p. 504)
433
2016

Modular Hardware / DS4004 HIL Digital I/O Board
DS4004 HIL Digital I/O Board

96 bidirectional digital I/O channels with signal conditioning
Highlights
96 digital I/O channels with general signal conditioning
up to 60 V
Measures and generates automotive signals and

TTL signals
All channels configurable via software


The DS4004 comprises 96 digital I/O channels with signal The automotive signal conditioning on the DS4004 HIL
conditioning for typical automotive systems with electrical Digital I/O Board is a cost-efficient way to start using HIL
system voltages of 12 V, 24 V, 36 V, and 48 V, etc., as well simulation for body electronics ECUs. The DS4004 can be
as for customary TTL levels. The 96 digital I/O channels of used hassle-free and at low cost in an expansion box, the
the DS4004 are arranged in three identical groups, each dSPACE Simulator Mid-Size and the dSPACE Simulator Full-
with two different voltage systems, ranging from 5 V to Size. These simulators are frequently used to test body
60 V. Each of the 96 I/O channels of the DS4004 can be electronics ECUs with the DS4004.
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.
434
2016

Modular Hardware / DS4004 HIL Digital I/O Board
Introduction
Technical Details
I/O channels 96 bidirectional digital I/O channels with automotive signal conditioning, arranged in three

ports (P1, P2, P3) of 32 I/O lines each
Software-configurable as digital I/O or timing I/O (PWM I/O)

PWM functionality with up to 50 ns resolution

Digital inputs Input voltage 0 ... +60 V

Threshold voltage level 1 V ... 23.8 V (software-configurable)

Application Fields
Input impedance 390 kΩ

Overvoltage protection 0 ... +60 V continuous

Digital Outputs Output voltage +5 V ... +60 V (supplied from external power source)

6 independent rails VBAT_Px_y (two rails for each port P1 ... P3)

Output current range Max. ±50 mA; short circuit proof to GND and VBAT by self-resetting fuse

Vout high, min. VBAT -1.2 V; at +50 mA

Vout low, max. 0.4 V; at -50 mA

Interrupt controller Interrupt channels 3 x 2 pins (shared with I/O channels)

Trigger source Interrupt generation on falling edges, rising edges, or both edges (software-configurable)

Threshold voltage level 1 V ... 23.8 V (software-configurable)


Software

characteristics The board requires three brackets


Power supply (from host PC) +5 V ±5%, 1.5 A max. (from host PC or expansion box)

+12 V ±5%, 0.4 A max. (without load on power supply outputs)

-12 V ±5%; 0.01 A max.

Power supply (from external power
6 VBAT_Px_y rails (+5 V ... +60 V DC)
source) Each supply rail (VBAT_Px_y): 0.2 A max. (0.05 A typ.) + load on digital outputs

Hardware
Order Information


Relevant Software

RTI

Engineering
435
2016

Modular Hardware / DS4121 ECU Interface Board
DS4121 ECU Interface Board

Connects electronic control units with a dSPACE modular system
Highlights
Real-time interface to ECUs with 8-, 16- and 32-bit

microprocessors
Two LVDS channels for high-speed, low latency

communication
Tailored for bypass applications and the

RTI Bypass Blockset
Application Areas
The DS4121 provides the link between your electronic ECUs can be connected to the DS4121 at the same time.
control unit (ECU) and a dSPACE modular system. Bypassing This offers the flexibility to operate such things as powertrain
individual ECU algorithms and calculating them on a control modules containing the engine and transmission
prototyping system is a typical application example. The controllers, or valve controls for 8- and 12-cylinder engines.
connection is made via a dual-port memory plug-on device In addition, the DS4121 board provides the interface to the
(DPMEM POD), on-chip debug interfaces like the DCI-GSI1 LVDS-Ethernet Link cable allowing dSPACE modular systems
(p. 598) or an LVDS-Ethernet Link cable (p. 437) to establish to be connected to Ethernet devices or networks.
an Ethernet UDP/IP communication. Two independent
Key Benefits Bypassing with the DS4121

The DS4121 is designed to carry out bypassing exactly the With the DS4121, you can either use one single hardware
way you want. For example, the production-intent ECU can interrupt from the ECU to the prototyping system, or you
remain in its final mounting position while the prototyping can split one interrupt into up to 128 subinterrupts with
system might be mounted virtually anywhere in the vehicle. a specially designed ECU software porting kit, allowing full
The standard board version of the DS4121 is connected multi-level, multitasking bypassing. The interrupts can be
to the ECU via copper cable. The DS4121-FX uses a fiber- specified via easy-to-use dialogs. You can also perform
optic link which increases the possible distance between service-based bypassing with the RTI Bypass Blockset
board and ECU. (p. 64).
436
2016

Introduction
Technical Details
General 2 communication channels

Memory Dual-port memory (DPMEM) 16 K x 16 for each channel

16-bit word access, 8-bit low byte, 8-bit high byte

Interrupts Bidirectional interrupts for synchronization of data transfer (for each channel)

Connection lost interrupt (for each channel)

16 subinterrupts (using RTI Bypass Blockset) via one interrupt line
Application Fields

FIFO-full and FIFO-empty interrupt (for each channel)

Target ECUs Most kinds of 8-, 16- and 32-bit microprocessors

Communication with ECU Two channels for connecting two ECUs or one dual-CPU ECU

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. 598) or an LVDS-Ethernet Link.
POD for SPI available

Customer-specific POD can adapt ECU signals to the DS4121 (PODs can be

integrated into the ECU enclosure)
Compatibility with PODs designed for MicroAutoBox

Cabling DS4121: twisted pair cable (CAT5 STP) suitable for close-to-engine location

DS4121-FX: connection between board and ECU via fiber-optic cable
Software

Signaling system Full-duplex high-speed LVDS link (low-voltage differential signaling)

Transfer rate 250 Mbit/s LVDS interface between DS4121 and ECU

80 Mbit/s effective data rate per channel in both directions


Physical characteristics Physical size 340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in.)


Power supply +5 V, 1.2 A

Hardware
Order Information

DS4121 ECU Interface Board DS4121

Engineering
Included ECU software porting kit
–
RTI

Optional RTI
Bypass Blockset (for service-based bypassing) RTIBYPASS_BS
(p. 64)

Optional Generic Serial Interface DCI-GSI1 (p. 598)
DCI-GSI1

Customer-specific Plug-On Devices (PODs) (p. 604)

Please inquire
LVDS-Ethernet Link cable
LVDS_CAB13/14

LVDS Link cable
LVDS_CAB2

437
2016

Block Diagram
PHS Bus Processor

Board I/O Boards
PHS-Bus
Interface
Address
Register
Channel 1
Channel 1 High
Reflective POD ECU
Data DPMEM Speed
Register . Memory Link
16 K x 16
Controller
Interrupt
Register
Channel 2
Channel 2 High
Reflective Speed POD ECU
DPMEM Memory
Power 16 K x 16 Link
Controller
Supply
DS4121
ISA Bus PC
438
2016

Introduction
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
Application Fields
DS4121.
Software
RTI Bypass Blockset:
Configuring bypass interfaces and
bypass services for function prototyping.
Hardware
For address-based bypassing using PODs and for coupling
multiple real-time systems such as AutoBoxes, the DS4121
Blockset can be used.
Engineering
Standard ECU Interface blockset

fully integrated in MATLAB/Simulink.
439
2016

Modular Hardware / DS4201 Prototyping Board
DS4201 Prototyping Board

Integrates customized circuits into dSPACE systems
Highlights
Provides all the required electronics for connection

to the dSPACE PHS bus
Space for mounting custom devices

Useful for additional I/O solutions

Technical Details
Custom interface Bidirectional buffered 32bit data bus

8 interrupt lines (programmable)

4 PHS bus address signals

13 predefined chip select outputs (for I/O ports)

1 board select signal; read/write signals; I/O signals

Up to 25 MB/s transfer speed

80pin custom connector

Power lines (ground, +5 V, +12 V, 12 V)

Timing SYNCIN and SYNCOUT lines for input and output on several I/O boards

Physical connections 50pin male SubD connector for external devices

Host interface One 16bit ISA slot


Custom board size Up to 115 x 185 mm (4.5 x 7.3 in)

Ambient temperature 0 ... 70 °C (32 ... 158 °F)

Power supply +5 V ±5%, 500 mA (without custom module)

Order Information

DS4201 Prototyping Board DS4201

Relevant Software and Hardware for DS4201 and DS4201-S

Included C library functions for serial communication (for DS4201S only)
–
Required RealTime Interface (for DS4201S only) (p. 56)
RTI


Optional Adapter cable with standard 9pin SubD (for DS4201S only)
SIO_CAB

440
2016

Modular Hardware / DS4201S Serial Interface Board
DS4201S Serial Interface Board
Introduction
Interface for serial communication between a dSPACE system and external devices
Highlights
Application Fields
Supports RS232, RS422, and RS485 line

transceivers
Useful for connecting two systems over long

distances
Software
Technical Details
General 4 independent serial communication channels, each with a PC16550D UART (universal asynchro

nous receiver/transmitter)
Supported transceiver types: RS232C, RS422, RS485

Interrupts Programmable interrupt control unit for up to 4 independent serial communication interrupts

Serial communication channels 4 RS232 transceiver channels

RS422 and RS485 transceivers optional

Hardware
Clock source: up to 24 MHz (optional for RS422 and RS485, custom clock source possible)

Modem control functions

Baud rate range RS232 1.8432 MHz clock: up to 115.2 Kbaud
24
MHz clock: up to 115.2 Kbaud
(limited by RS232 transceiver)
RS422 1.8432 MHz clock: up to 115.2 Kbaud
24
MHz clock: up to 1.5 Mbaud
RS485 1.8432 MHz clock: up to 115.2 Kbaud
24
MHz clock: up to 1.5 Mbaud
Parity bits Even, odd, or no parity

Stop bits 1, 1.5, or 2 bits

Word length 5, 6, 7, or 8 bits

FIFOs 16 byte input FIFO

Engineering
16 byte output FIFO

Physical connections 50pin male SubD connector

Host interface One 8 or 16bit ISA slot (power supply only)



Power supply +5 V ±5%, 350 mA

+12 V ±5%, 75 mA

Order Information

DS4201S Serial Interface Board 1)
DS4201S

1)
For information on relevant hardware and software see p. 440.
441
2016

Modular Hardware / DS4302 CAN Interface Board
DS4302 CAN Interface Board

Interface to CAN bus
Highlights
Connects modular dSPACE systems to the CAN bus
Features 4 CAN channels

The DS4302 CAN Interface Board has been designed to The DS4302 enables dSPACE systems to take part in CAN-
operate in controller area network (CAN) environments as bus traffic without the need for extra interface electronics.
used primarily in the automotive and automation industries. Its three individual transceivers on each of the four inde-
Typical application fields of the DS4302 are: pendent channels cover almost all possible application areas.
They include a high-speed transceiver for hard real-time
In-vehicle rapid control prototyping communication and a fault-tolerant low-speed transceiver,
Hardware-in-the-loop tests necessary for tasks such as comfort electronics. Every con-
Restbus simulation figuration of the DS4302 can be carried out in a Simulink®
Automation tasks block diagram, thereby eliminating CAN controller program-
ming.
Comprehensive Software Support

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 con-
figuration options range from message setup to interrupt
configuration, right through to message time-stamping.
The easiest way is if you already have communication de-
scription 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.
RTI CAN Blockset (p. 71)

442
2016

Introduction
Technical Details
General 4 independent CAN channels
3 different on-board CAN transceivers per channel
Piggyback module socket for up to 4 customer-specific CAN transceivers
Processor Slave DSP TMS320VC33-150 from Texas Instruments (75 MHz, 150 MFLOPS, 75 MIPS)
Handles CAN controller communication
Memory On-board memory 256 k x 32-bit SRAM
Application Fields
4 M x 32-bit flash memory
Dual port memory (DPMEM) 32 k x 32-bit dual-port memory (DPMEM) for communication between PHS-bus master
and slave DSP
Interrupt controller CAN controller interrupt
PHS interrupt support
Various interrupt sources
Standards supported CAN 2.0 A (standard frame format)
CAN 2.0 B (extended frame format)
ISO DIS 11898-2 – high-speed CAN bus
ISO 11519-1 – low-speed CAN bus, fault-tolerant
On-board Transceiver chips MAX3057 ISO11898 high-speed transceiver (up to 2 MBd), ±80 V fault protected
CAN transceivers TJA 1055 fault-tolerant low-speed transceiver supporting transmission rates up to 125 kBd
Software
SN75176 modified RS485 transceiver supporting baud rates up to 500 kBaud
Bus termination resistors (software selectable)
8 bidirectional I/O lines at customization module connectors
Further details Full-CAN controller (BOSCH CC770)
Programmable controller clock
Physical Physical size 340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in.)
Power supply (without piggyback +5 V ±5%, 1.2 A
modules) +12 V ±5% 20 mA
Hardware
Order Information

DS4302 CAN Interface Board DS4302
Relevant Software
Engineering
Required Real-Time Interface (RTI), (p. 56) RTI
Optional RTI CAN Blockset (p. 71) RTICAN_BS
RTI CAN MultiMessage Blockset (p. 74) RTICANMM_BS
Add-On: RTI CAN MultiMessage-J1939 Blockset RTICANMM_J1939_BS
For connection of dSPACE‘s modular hardware

to a CAN FD bus system, see p. 448.
443
2016

Block Diagram
PHS Bus Processor I/O Boards

Board
CAN 4
...
CAN 1
PHS-Bus CAN
Interface Controller
CC770
32k x 32-bit TMS320VC33 ISO 11898

DPMEM DSP Channel 4
.
.
RS485 .
Interrupt Interrupt
Controller Controller Channel 1
Fault-Tolerant
4M x 32-bit
Flash ROM
Piggyback
Module
Power 256k x 32-bit Termination

Supply SRAM Resistor
DS4302
ISA Bus PC
444
2016

Modular Hardware / DS4330 LIN Interface Board
DS4330 LIN Interface Board
Introduction
Interface to LIN bus
Highlights
Application Fields
Connects modular dSPACE real-time

systems to the LIN bus
LIN master and slave support

16 independent LIN channels

Software
Application Areas in Rapid Control Prototyping Application Areas in Hardware-in-the-Loop Simulation
The DS4330 and the corresponding software can be used Using dSPACE Simulator and a DS4330, you can test the
for developing and testing electronic control units (ECUs) LIN network features of an electronic control unit. The
which communicate with Local Interconnect Network (LIN) dSPACE system simulates the LIN nodes, which are con-
actors and sensors. For rapid control prototyping purposes – nected to the LIN bus. The simulated LIN nodes behave in
laboratory-based or vehicle-based – real LIN slaves can be exactly the same way as real bus members (restbus
connected to the prototyping system that simulates the ECU simulation).
under development as the master node.
Hardware
Test Scenarios Comprehensive Software Support
The DS4330 can be used in many different ways. Several The DS4330 provides a LIN interface for the connection of
scenarios are possible: dSPACE systems to LIN buses. You can set up and control
these simulated LIN buses with the RTI LIN MultiMessage
Testing of: Blockset (p. 77).
Engineering
Transmission of message frames The RTI LIN MultiMessage Blockset (supporting LIN standards
Communication timing constraints 1.3, 2.0, 2.1 and 2.2) is an extension for Real-Time Interface
Specification limits and can be used for combining dSPACE systems with LIN
Diagnostic and failure conditions communication networks and for configuring these LIN net-
Energy-saving modes works. With the RTI LIN MultiMessage Blockset you can
handle complex LIN setups, which lets you control and con-
figure all unconditional and event-triggered LIN frames from
one single Simulink® block (configuration via database file).

445
2016

Technical Details
General 16 independent LIN channels

One on-board LIN transceiver per channel

Simulation of up to 16 LIN slaves per LIN channel

Software-selectable individual baud rates from 1000 baud up to 20 kBd for each channel

Piggyback module socket for up to 16 custom LIN transceivers

Transmitting and receiving LIN data from within a Simulink model

Processor Slave DSP IBM PowerPC 405CR, 200 MHz

PowerPC can boot from DPMEM or flash memory (selectable by software)

Memory On-board memory 64 MB SD-RAM, 100 MHz

8 MB flash memory

Dual port memory (DPMEM) 32 k x 32 bit dual-port memory for communication between PHS bus and slave

processor
Interrupt controller UART interrupt for each LIN channel

LIN transceiver wake-up interrupt for each LIN channel

All interrupts can be enabled/disabled separately by software

On-board LIN transceiver Transceiver chip Infineon TLE6259

Integrated pull-up resistors for TXD and RXD lines

On-chip termination resistor for LIN slave applications

2
additional bidirectional I/O lines per channel at customization module connectors
for general purposes
Thermally protected
Further details External 1 kΩ termination resistor for using the LIN channel as a master
(selectable via software)

Physical characteristics Physical size 340 x 125 x 15 mm (13.4 x 4.9 x 0.6 in.)



+12 V ±5%, 750 mA (supplies the VCC12 pin on the interface connector only)

Order Information

DS4330 LIN Interface DS4330

Relevant Software

RTI

Optional RTI LIN MultiMessage Blockset (p. 77)
RTILINMM_BS

446
2016

Introduction
Application Fields
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.
Software
Block Diagram
I/O Boards
Hardware
Engineering
PC
447
2016

Modular Hardware / DS4505 Interface Board
DS4505 Interface Board

Interface to FlexRay or CAN FD bus
Highlights
Connects dSPACE‘s modular hardware to

a FlexRay or a CAN FD bus system via additional
interface modules
Supports up to 4 interface modules


The DS4505 Interface Board lets you connect a dSPACE There are two additional interface modules for the DS4505
system with modular hardware to a FlexRay and/or a CAN Interface Board: the DS4340 FlexRay Interface Module (p.
FD communication system. It is ideally suited for testing 450) to connect to FlexRay buses and the DS4342 CAN FD
applications that involve a dSPACE prototyping system or Interface Module (p. 451) to connect to CAN/CAN FD bus-
dSPACE Simulator. The board can carry up to four interface es. The modular structure lets you use a mix of both modules
modules. on one DS4505.
FlexRay Basics CAN FD Basics

FlexRay is a time-triggered communication system for The CAN FD (FD = Flexible Data Rate) protocol was intro-
in-vehicle applications with demanding communication duced to enhance the classic CAN protocol in terms of data
needs. It is the standard for deterministic, high-performance rates and payload data length. With CAN FD, a multiplied
automotive communication networks. The basic principle data rate allows an average data transmission speed of
of time-triggered systems is that tasks are executed and several Mbit/s and payload lengths of up to 64 bytes (com-
messages are sent according to a predefined schedule. In pared to 8 bytes in a classic CAN).
FlexRay, activities are aligned to a global time base, where-
as in nondeterministic communication protocols such as
CAN, they are mainly event-triggered at run time.
448
2016

Introduction
Technical Details
General Access to a FlexRay or CAN/CAN FD communication bus from a test system or prototyping platform

Supports the DS4340 FlexRay Interface Module (p. 450) and the DS4342 CAN FD Interface Module (p. 451)

Provides 4 slots (for DS4340 or DS4342)

Supports high-performance interfaces via a PHS++ bus

Sub-D 50 connector to connect an external FlexRay or CAN FD bus with DS4505

Host interface One 8-bit or 16-bit ISA slot (for power supply only)

Application Fields
Physical Physical size Full-length ISA board, 340 x 125 x 15 mm (13.4 x 4.9 x 0.59 in)


Power supply +12 V ±5%, 20 mA (if 4 interface modules are inserted)

+5 V ±5%, 150 mA (if no interface modules are inserted)

+5 V ±5%, 650 mA for DS4505 carrying 1 module (total power consumption depends on inserted modules)

Order Information

DS4505 Interface Board DS4505

Software

Included C functions for accessing/controlling the DS4505 –
Required Real-Time Interface (p. 56) RTI

dSPACE FlexRay Configuration Package (p. 80) FCP

RTI CAN MultiMessage Blockset (p. 74) RTICANMM_BS

Hardware
Required DS4340 FlexRay Interface Module (p. 450) DS4340

DS4342 CAN FD Interface Module (p. 451) DS4342

Optional FlexRay Interface Cable for DS4505 FR_CAB2

Engineering
449
2016

DS4340 FlexRay Interface Module

Module for interfacing to FlexRay buses
The DS4340 FlexRay Interface Module can be used with the
DS4505 Interface Board or MicroAutoBox II variants. The
module supports FlexRay protocol specification 2.1 and
offers downward compatibility to previous standards. It
provides a software-configurable, switchable termination
circuit. The configuration is done with the dSPACE FlexRay
Configuration Package, which is used to integrate dSPACE
hardware as simulation or monitoring nodes in a FlexRay
network.
General Supports FlexRay protocol specification 2.1

Supports the DS4505 Interface Board and can be used with MicroAutoBox II 1401/1507, 1401/1511/1514, and 1401/1513/1514

Automatic carrier board detection (MicroAutoBox/DS4501 or DS4505) for optimized interface speed

Molex connectors for direct access to FlexRay bus lines

Switchable termination circuit (software configurable)

Feed-through option for FlexRay bus lines in passive-linear-bus topology

Two FlexRay channels

Hardware Freescale MFR43xx Communication Controller Family

Details Dual PHY Interface with TJA1080

Wake-up support for MicroAutoBox1)

Requires one slot

1)
Hardware modification of MicroAutoBox and DS4340 required. For more information, please contact dSPACE.
450
2016

Introduction
DS4342 CAN FD Interface Module
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 variants. The DS4342 provides two indepen-
dent CAN channels, each of which can be used for CAN FD
or for CAN. Network management functions such as wake-
Application Fields
up and sleep are also included. The DS4342 also provides a
software-configurable, switchable termination circuit.
General 2 CAN/CAN FD channels

Supports the DS4505 Interface Board and can be used with MicroAutoBox II 1401/1507, 1401/1511/1514, and 1401/1513/1514

Automatic detection of Industry Package (IP) for MicroAutoBox 1401/1507 or fast COM mode for MicroAutoBox 1401/1513/1514 and

DS4505 Interface board
Supported by RTI CAN MultiMessage Blockset

Software
Support of ISO CAN FD and nonISO CAN FD

Switchable termination circuit (software configurable)

Capable of ISO 118985 network management

Capable of handling ISO 118982 CAN or CAN FD on every channel

Hardware NXP TJA1145T CAN Transceiver

Details Requires one slot

Hardware
Engineering
451
2016

Modular Hardware / DS5001 Digital Waveform Capture Board
DS5001 Digital Waveform Capture Board

Capturing digital signals
Highlights
Captures digital signals for parameter evaluation

Standard functions for pulse analysis such as PWM

measurement included
Ideally suited to control and hardware-in-the-loop

applications in automotives and drives

The application area of the DS5001 Digital Waveform Cap- Capturing digital signals is a part of most control and hard-
ture Board ranges from automotives through drives to robot- ware-in-the-loop applications. However, with ordinary
ics. The DS5001 is in active use in many hardware-in-the- timing I/O, the speed, resolution, or number of channels
loop and rapid control prototyping applications. It can be often is not sufficient. And typically, complicated analysis
connected to the Engine Position Bus of the DS2211 HIL I/O algorithms are required – and these usually have to be pro-
Board (p. 410). This allows you to perform angle-synchro- grammed in assembler language, which most users would
nous signal capturing, with the DS5001 as either a time-base prefer to avoid.
slave or the master. The board can also be connected to the You can overcome these limitations with the DS5001. The
time-base connector of the DS4002 Timing and Digital I/O board records digital signals at high speed for extremely
Board or other DS5001 boards, and itself function as a flexible evaluation of frequency, phase, duty cycles, and other
time-base master for other boards. 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 character-
istics such as jitter and missing pulses.
452
2016

Introduction
Technical Details
General 16 timing I/O channels (inputs)

Event storage with dual-port memory (DPMEM) and first-in-first-out memory (FIFO)

Interrupt controller

Time-base connector

Interrupt controller Interrupt on predefined number of events

Interrupt on event buffer full

Application Fields
Interrupt on input FIFO full

Timing I/O channels Time resolution 25 ns

Sampling rate Max. 40 MHz

Input frequency Max. 20 MHz

Pulse-width range 25 ns … 53.68 s

Edge detection Separate edge detector for each channel

Detection type Programmable rising and/or falling edge detection

Input voltage range (trigger level) ±10 V (programmable)

Input voltage protection ±35 V (continuous)

Hysteresis 80 mV … 2.8 V (selectable)

Software
Input impedance >12 kΩ / 5 pF

Edge detection Rising and/or falling edge detection (programmable)

Trigger level -10 … +10 V (programmable in 256 steps)

Event storage Dual-port RAM stores up to 512 events per channel

Events include 31-bit time stamp and edge polarity

Access to event storage from processor board

Event counters 3 up counters (32-bit)

Each counter can be assigned to any channel

Counter read and reset from processor board



Hardware



Order Information

DS5001 Digital Waveform Capture Board DS5001

Engineering
453
2016


Included C functions for accessing/controlling the DS5001 (provided with the processor board)
–
Standard functions for pulse analysis (provided with the processor board), such as:
–
PWM duty cycle analysis

Frequency measurement

Phase measurement

Incremental encoder input

RTI


CP5001

Block Diagram
Processor I/O boards

PHS bus board
PHS-bus Counter A Timing I/O Unit

interface
Further
Time Time-base DS5001/
base connector DS2211/
Counter B DS4002
Interrupt
controller Counter C 16
... Chan. 16
.
1 .
.
FIFO
FIFO Edge Com- Input Chan. 1
Controller detector parator protect.
Trigger level
select
Dual-port
memory
Power
supply
DS5001
ISA bus PC
454
2016

Introduction
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
Application Fields
lets you enter the desired trigger levels and
number of periods to include.
Application Example
Wheel Speed Measurement
Automotive control is a typical application field for the
Software
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 Channel 1...16
Hardware
each event and stores its time and polarity. You can easily
CH 1
determine the exact wheel speed with the included
t1 t3 t5 t8 t10 t12 t13
...
frequency analysis functions. Since the DS5001 board stores
CH 16
a complete event history, it is easy to apply special algorithms
t2 t4 t6 t7 t9 t11
for improved measurement quality, such as averaging the
last n pulse periods, where n can be variable. Edge Detect
Channel 1...16
CH
CH 1
1
tt1 tt3 tt5 tt8 tt10 tt12 tt13
Capturing Events ...
... 1 3 5 8 10 12 13
Engineering
Each input signal is captured with its own edge detector, CH 16
CH 16
tt2 tt4 tt6 tt7 tt9 tt11
including programmable edge enables and trigger level. The 2 4 6 7 9 11
times and polarities of the detected events are stored sepa-

Edge Detect
rately for each channel in an event buffer in dual-port RAM. Event RAM
...........................
You can then use this data to perform analysis on the pro- Channel 1
CH 1
Channel 16
t1 t2
cessor board. ...t3
t1 t3 t5 t8 t10
t4 t12 t13
t5 t6
CH 16
t8 t7
t10 t2 t4 t6 t7 t9 t9 t11
t12 t11
t13
...........................
Event RAM
Channel 1 ........................... Channel 16
t1 t2
t3 t4
t5 t6
t8 t7
455
t10 t9
2016
t12 t11
t13
dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de
...........................• www.dspace.com
Modular Hardware / DS5101 Digital Waveform Output Board
DS5101 Digital Waveform Output Board

For generating pulse patterns
Highlights
Generates digital pulse patterns autonomously
25 ns resolution on 16 channels
Standard pulse patterns such as PWM included

Digital pulse patterns are required in almost any control The DS5101 autonomously generates any TTL pulse patterns
application. The demands made on PWM resolution and on up to 16 channels with high accuracy. With a time
flexibility are very high, especially in drives control. With resolution of 25 ns, the DS5101 meets even the toughest
ordinary timing I/O, you come up against the limits very requirements. The ability to change pulse widths in real time
quickly. Digital signals in automotive applications usually combined with various trigger and interrupt mechanisms
require less resolution, but the demands on flexibility can give the DS5101 board unbeatable flexibility and program-
nevertheless be high, for example, for the simulation of mability.
crankshaft signals.
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.
1-phase PWM
3-phase PWM
3-phase/6-channel PWM (includes converted signals)
Incremental sensor simulation
Monoflop signal generation
456
2016

Introduction
Technical Details
General 16 timing I/O channels
External reset input
Interrupt controller
Memory Dual-port memory (DPMEM) DPMEM for program (states) and data (delays)
Stores 512 delay parameters (30 bits) and 128 program states (90 bits) for each channel
Interrupt controller All timing I/O channels share a single physical interrupt to the processor board. Any channel
Application Fields
can generate an interrupt. Interrupt arbitration is performed by software.
Interrupt on external reset
Timing I/O channels Time base 25 ns time resolution
40 MHz internal or 20 ... 40 MHz external common time base
2 MHz maximum output frequency
250 ns ... 26 s pulse widths
Triggering Mutual triggering of all channels
Output channels configurable as input channels for trigger signals
Voltage range TTL input/output level
Output current Max. -15 mA/+64 mA
External reset input TTL input level
Software
Power supply +5 V ±5%, 0,5 A
Order Information
Hardware
DS5101 Digital Waveform Output Board DS5101

Included C functions for accessing/controlling the DS5101 –
Standard pulse patterns –
Intuitive high-level language for programming pulse patterns –
Engineering
Required Real-Time Interface (p. 56) RTI

Optional Connector Panel for DS5101 (p. 504) CP5101
457
2016

Block Diagram
Processor I/O boards

PHS bus board
PHS-bus
interface Channel 16
...
Channel 16
Interrupt
control Channel 1
unit
Swinging
buffer
controller
Channel 1
Reset Controller
logic
Dual-port
memory
Software
trigger / flag
unit External
reset input
Power
supply
DS5101
ISA bus PC
458
2016

Introduction
Working with the DS5101
Programming Language
Intuitive high-level language Conditional branching
Mutual triggering of all channels Synchronized update of parameters in real time
Loop counter Interrupt generation
Application Fields
List of Commands (Excerpt)
Command 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.
LDCTR Loads the 8-bit channel loop counter with a specified value.
Software
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.
Hardware
Engineering
459
2016

Use Case: Incremental Encoder Simulation

Generating Sensor Signals Controlling the Simulation
A typical application is the generation of sensor signals, for As you can see from the program listing below, controlling
example, for hardware-in-the-loop simulations. The incre- the simulated rotation is an easy task. To change the direc-
mental encoder simulated in the first example can be used tion, just set or reset flag 1. In this simulation, the direction
for any number of lines per revolution. The output signals changes after 2000 time units. The speed can be influenced
are phi_0 (channel 1) and phi_90 (channel 2). Each period simply by increasing or decreasing the delay t_enc.
is divided into four sections to ensure synchronous opera-
tion, for example, when the rotation speed is changed.
Program listing for an example of sensor signal generation.
460
2016

Introduction
Use Case: PWM Generation
Generating Digital Signals Connection to the Processor Board
The simulation result below shows the generated digital The processor board transfers new parameters to a buffer
signals for the two switches of a 1-phase PWM inverter. The on the DS5101 board, and all new parameters become
PWM carrier frequency selected is 10 kHz. Any other fre- effective simultaneously. This occurs once at the beginning
quency could be chosen by modifying the delay t_master of each loop on channel 1. The wait statement switches a
in the program. The specified delays can be overwritten at channel to idle state until another channel sends a trigger
Application Fields
any time by applying the syncen mechanism. with the trx command.
Various Commands
In the example, the master clock on channel 1 sends triggers analog inputs and execute the controller code. In the
to channels 2 and 3. The phsint command generates an example, phsint is executed once in a loop on channel 1.
interrupt on the processor board, for example, to sample
Software
Hardware
Engineering
Program listing
for a PWM signal
generation example.
461
2016

Modular Hardware / DS5203 FPGA Board
DS5203 FPGA Board

FPGA programmable per application
Highlights
 Completely user-programmable via the RTI FPGA
Programming Blockset (p. 90)
 Utilizes the Xilinx® System Generator (XSG) Simulink®
Blockset
 Offline simulation in Simulink
 Basic set of I/O drivers on board, I/O extendable
by piggyback modules
 NEW: Two new board variants

The DS5203 FPGA Board can be adapted to various tasks, A field-programmable gate array (FPGA) is a semiconductor
so you can react flexibly to tougher requirements, such as device consisting of logic elements that you can configure.
signal conditioning, using new interfaces, or speeding up The DS5203 FPGA Board features the freely programmable
model parts. FPGAs are especially useful for relieving the FPGA Xilinx® Virtex®-5 with ISE1) support or the powerful
processor board of tasks such as signal preprocessing Xilinx® Kintex®-7 with additional Vivado® support. In addition,
during ECU development. Running at 100 MHz, the DS5203 the board offers 6 ADC, 6 DAC and 16 digital I/O channels,
board is ideal for application fields like engine knocking, cylin- and connection to the processor board via PHS bus. The num-
der pressure analysis and electric drive projects. The DS5203 ber of I/O channels can be increased by piggyback modules.
works closely together with the XSG model library (p. 271).
Programming via the RTI FPGA Programming 4 Variants

Blockset The DS5203 is available with 4 different FPGAs:
The DS5203 FPGA Board is programmed via the RTI FPGA  The DS5203 LX 50 includes a Xilinx® Virtex®-5 LX50T-1C
Programming Blockset (p. 90) from dSPACE and the Xilinx® FPGA, consisting of 46080 logic cells and 48 special
System Generator. These let you develop applications for DSP blocks. This board offers a cost-effective solution
the processor board and the DS5203 together. You can test for smaller applications and starter systems.
the interaction between the processor application and the  The DS5203 SX95 includes a Xilinx® Virtex®-5 SX95T-2C
FPGA application in offline simulation before implementing FPGA, consisting of 94298 logic cells and 640 special DSP
them on the real-time hardware. This lets you react flexibly blocks. The large amount of DSP blocks help by perform-
to new requirements, such as new interfaces or having to ing tasks such as fast, resource-saving multiplication.
accelerate the execution of submodels.  NEW: The DS5203 7K325 includes a Xilinx® Kintex® 7K325
You can also use the RTI FPGA Programming Blockset Hand- FPGA, consisting of 326080 logic cells and 840 special DSP
code Interface to program the DS5203. blocks. The large amount of DSP blocks help by performing
tasks such as fast, resource-saving multiplication.
 NEW: The DS5203 7K410 includes a Xilinx® Kintex® 7K410
FPGA, consisting of 406720 logic cells and1540 special
DSP blocks. The large amount of DSP blocks help by per-
forming tasks such as fast, resource-saving multiplication.
462
2016 1)
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.
Introduction
Technical Details
Specification
Parameter
DS5203 LX50 DS5203 SX95 DS5203 7K325 DS5203 7K410
General User-programmable FPGA

FPGA Xilinx® Virtex®-5 LX50T-1C Xilinx® Virtex®-5 SX95T-2C Xilinx Kintex® 7K325
Xilinx Kintex® 7K410

Logic cells: 46080
Logic cells: 94298 Logic cells: 326080 Logic cells: 406720
(Virtex®-5 slices: (Virtex®-5 slices: 14720; (Kintex®-7 slices: 14720; (Kintex®-7 slices: 14720;
7200; DSP slices: 48) DSP slices: 640) DSP slices: 840) DSP slices: 1540)
Application Fields
Distributed RAM: 480 kbit Distributed RAM: 1520 kbit Distributed RAM: 4000 kbit Distributed RAM: 5663 kbit

Block RAM: 2160 kbit
Block RAM: 8784 kbit Block RAM: 1620 kbit Block RAM: 28620 kbit
Xilinx® software support Only ISE®1)
Vivado®1)

Device timing 100 MHz



Digital input: Threshold adjustable for each channel from 1 V to 7.5 V

Output Digital output: Push-pull drivers; one output voltage can be selected for all channels: 3.3 V or 5 V

Resolution: 14 bit pipelined

Sampling rate: 10 Msps

Software

Output 6 channels

Resolution: 14 bit

Update rate: 10 Msps


Further interfaces Slot for one I/O module for extending the analog and digital I/O (p. 465)

Connection for the APU (angular processing unit) bus

2 connectors for inter-FPGA communication


characteristics Ambient 0 ... 55 ºC (32 ... 131 ºF)

temperature
Hardware

+12 V ±5%, 0.7 A

-12 V ±5%, 0.1 A

Please note that due to the introduction of the Vivado® software, Xilinx® no longer supports the Xilinx System Generator for DSPs in combination
1)
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.
High-Precision Engine Angle Computation Inter-FPGA Communication
Engineering
During hardware-in-the-loop simulation, the DS5203 pro- The DS5203 FPGA Board provides two inter-FPGA-commu-
vides a connection for an APU (angular processing unit) nication connectors. Together, the two connectors provide
bus in addition to the user-programmable FPGA. The APU a 32-bit parallel data bus. Inter-FPGA communication lets
calculates the engine angle with high precision as a basis the user exchange data directly between two FPGA boards
for providing I/O values to the HIL simulation. without a detour via the PHS bus and the processor board.
The DS5203 can be used as a master or a slave. When it is One FPGA application can be triggered by another that is
the APU master, the angle values for the simulation model located on another FPGA board, e.g., to synchronize the
are computed and used on the FPGA itself, and, if neces- applications.
sary, transmitted to other I/O boards via the APU bus. As
the APU slave, it receives the engine angle values from an-
other dSPACE I/O board, such as the DS2211 HIL I/O Board
(p. 410). The angle data can then also be used in the simula-
tion models running on the DS5203.
463
2016

Order Information

DS5203 FPGA Board (LX50) 1)2)
DS5203_LX50

DS5203 FPGA Board (SX95)1)2) DS5203_SX95

DS5203 FPGA Board (7K325) DS5203_7K325

DS5203 FPGA Board (7K410) DS5203_7K410


RTI

RTI FPGA Programming Blockset FPGA Interface (p. 90) or
RTIFPGA_BS

RTI FPGA Programming Blockset Handcode Interface (p. 91)
n RTIFPGA_HC
Xilinx® Vivado® for the DS5203_7K325 and DS5203_7K410
–
Optional XSG Electric Components Library (p. 271)
XSG_ELECTRIC_BS

XSG Utils Library (p. 104)
FPGA_XSG_UTILS

XSG ACMC Library (p. 106)
FPGA_XSG_ACMC


Optional DS5203M1 Multi-I/O Module (p. 465)
DS5203_M1

EV1099: Resolver SC Module for DS5203 (p. 465)
EV1099

DS5203 Inter-FPGA Communication Cable
DS5203_CAB1

1)
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.
For information on standard hardware and software requirements for Xilinx® products, please see www.xilinx.com
2)
The board variants using the Virtex® FPGA do not support RTI FPGA programming but only RTI programming. FPGA applications generated
with Releases older than dSPACE R2013b can still be used.
464
2016

Introduction
DS5203M1 Multi-I/O Module
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.
Application Fields
Technical Details


Threshold for each channel adjustable from 1 V to 7.5 V

Software

Resolution: 14 bit pipelined

Sampling rate: 10 Msps


Output 6 channels

Resolution: 14 bit

Update rate: 10 Msps


Sensor supply Adjustable

Output voltage range: 2 V to 20 V

Hardware
EV1099: Resolver SC Module for DS5203
The EV1099 Resolver SC Module is a transfer element for the The module can be installed in a dSPACE Simulator Full-Size
DS5203 FPGA Board or the DS5203M1 Multi-I/O Module. or Mid-Size. It is connected via a ribbon cable to the DS5203
Engineering
It offers special signal conditioning for electric drive applica- or DS5203M1, which are pin-compatible.
tions, such as transformers for resolver simulation.
Additional features:
Configurable audio transformer for each of the 6 DAC
channels
Switchable 220 Ω resistor for each of the 6 ADC
channels
465
2016

Modular Hardware / SCRAMNet+ Interface
SCRAMNet+ Interface
Interface to SCRAMNet+ networks
Highlights
Connects modular dSPACE systems to SCRAMNet+

networks
Supports standard features of SCRAMNet+

RTI SCRAMNet+ Blockset for MATLAB®/Simulink®


This interface allows dSPACE Simulators to be integrated in With a SCRAMNet+ Interface, dSPACE Simulators and RCP
existing simulator environments where SCRAMNet+ (Shared solutions can take advantage of the very high speed and
RAM Network) is the chosen node-to-node communication deterministic performance of shared memory in a SCRAM-
standard. It enables dSPACE prototyping systems to be the Net+ network. SCRAMNet+ interfaces are available for
platform for distributed control systems and helps you various bus architectures such as VME, PCI, PMC, and
satisfy high-speed requirements when developing real-time CompactPCI, so dSPACE systems can integrate with non-
applications. SCRAMNet+ is ideally suited to applications dSPACE systems at high speed and in real time. Since this
including simulation, telemetry, robotics, data acquisition, interface can share data and interrupts, accurate real-time
instrumentation, industrial process control, digital video, synchronization can be achieved between dSPACE and non-
and virtual reality. dSPACE systems. Data and interrupts are communicated at
memory speeds, a huge improvement over typical message-
passing networks. The result is interprocessor communica-
tion that is 100% deterministic and very low-latency.
SCRAMNet+ Network SCRAMNet+ Blockset

The SCRAMNet+ network is an ultra-fast data communica- A special SCRAMNet+ Blockset for MATLAB/Simulink is avail-
tion system designed for use in real-time computer systems. able for the SCRAMNet+ Interface board. The blockset serves
SCRAMNet+ is optimized for the high-speed transfer of as a graphical interface that allows you to configure the
small packets of data between computers when low- SCRAMNet+ node, read from and write to the SCRAMNet+
latency data transmission and precise timing are critical. 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.
466
2016

Modular Hardware / SCRAMNet+ Interface
Introduction
Technical Details
General Standard fiber-optic media connectors

1 MB shared SCRAMNet+ memory

Auxiliary connector for Fiber Optic Bypass Switch

Supports all standard SCRAMNet+ features

Status LEDs

Application Fields
Software support Multiple protocol support:

Burst

Burst Plus

Platinum

Platinum Plus

Network timeout support

Write-me-last mode support

Control of Fiber-Optic Bypass Switch

Read and write access to entire 1 MB memory

Data type handling

Network interrupt generation

Software
Incoming network interrupt handling

Error interrupt generation and handling

Memory interrupt generation and handling for each 32-bit location

Virtual paging (ability to integrate with any memory configuration)

Supported standards SCRAMNet+

Host interface One 8- or 16-bit ISA slot (for power supply only)

Physical Physical size Full-length ISA board

characteristics Ambient temperature 0 … +70 °C (32 … 158 °F)


Hardware
Order Information

SCRAMNet+ Interface Board Please inquire
Engineering
Included RTLib C driver library
−
RTI

RTI SCRAMNet+ Blockset

Please inquire

Included DS4503 carrier board

−
1 MB SCRAMNet+ rehostable module
−
Standard Fiber Optic Media Card module
−
467
2016

Modular Hardware / PROFIBUS Interface
PROFIBUS Interface
Interface to a PROFIBUS communication bus
Highlights
Connects dSPACE systems to the PROFIBUS Network

Dual-port memory for data exchange with processor

board
Master or slave PROFIBUS modules available


Processing closed-loop and open-loop control information The PROFIBUS Interface is equipped with the PHS++ bus
for machinery and systems with the aid of powerful micro- interface and can therefore communicate with the dSPACE
chips is widespread in modern automation technology. As modular hardware at very high speeds. The maximum
a rule, the processors are connected by one or more com- possible baud rate for PROFIBUS communication is 12 Mbaud.
munications networks. The PROFIBUS interface connects A sample setup with a ControlDesk® experiment comes with
dSPACE Simulator and dSPACE prototyping systems to the interface to explain the basic implementation of dSPACE
PROFIBUS networks to develop controller technologies for modular hardware in PROFIBUS environments.
factory automation, decentralized peripherals, and motion
control, for example.
PROFIBUS
The PROcess-FIeld-BUS is a vendor-independent, open field
bus standard for a wide range of applications in manufac-
turing 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 commu-
nication tasks. It utilizes a nonpowered two-wire (RS485)
network and can have up to 126 nodes.
468
2016

Modular Hardware / PROFIBUS Interface
Introduction
Technical Details
General Direct connection to the field bus

Communication without load on the host system

Dual-port memory for data exchange with processor board

9-pin Sub-D connector for connection to PROFIBUS

C device driver functions for communication

Application Fields
PROFIBUS access and message composing via S-functions, based on dSPACE

examples
Technical data Free potential RS485

Transmission rate 12 Mbaud

Diagnostic interface RS232C, nonisolated

Supported standards PROFIBUS


Physical characteristics Physical size Full-length ISA board

Ambient temperature 0 … +55 °C (32 … 131 °F)


±12 V ±5%

Software
Order Information

PROFIBUS Interface Please inquire
Hardware
Included Hilscher SyCon® configuration software
−
Required dSPACE Software Release with RTI1)
−
dSPACE PROFIBUS Solution1) (DS1005, DS1006, DS1007)
−
1)
Engineering
Included DS4502 carrier board
DS4502

Hilscher Module COM-PB (master) or COM-DPS (slave)
−
469
2016

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
Comprehensive Simulink® block library


The interface to MIL-STD-1553 connects a modular dSPACE The interface to MIL-STD-1553 enables you to connect your
real-time system to a MIL-STD-1553 network. It is used in MIL-STD-1553 network directly to the real-time application
hardware-in-the-loop (HIL) simulation and rapid control running on the dSPACE processor board. It supports the
prototyping (RCP) to test and develop control systems that DS1005, DS1006 and DS1007 Processor Boards, and is also
use MIL-STD-1553. Examples are HIL simulation for satellite multiprocessor-capable.
avionics integration testing and component validation of Each channel can be configured independently as Remote
aircraft flight surface actuator and engine controllers Terminal (RT), Bus Controller (BC), or Bus Monitor (BM).
(FADECs). This interface is based on the industry-proven When configured as Remote Terminal, each channel supports
QPC-1553 module from GE Intelligent Platforms. up to 31 remote terminals, and in BC functionality, schedule
lists are supported, with the ability to change lists dynami-
cally during run time to facilitate fault testing for RTs.
Hardware and Software

The interface is based on the DS4504 PMC Carrier Board, high-speed) bus and a 2-MB dual-port memory (DPMEM).
which acts as a carrier for an Embedded Technology A Compact Flash (CF) card contains the QNX run-time
eXtended (ETX) module and a MIL-STD-1553 PCI Mezzanine operating system and the ETX application. The I/O connec-
Card (PMC). Data exchange between the ETX and the tion to the Simulink model is configured graphically by
dSPACE processor board runs via the PHS++ (peripheral means of the MIL-STD-1553 blockset.
470
2016

Modular Hardware / Interface to MIL-STD-1553
Introduction
Technical Details
General Up to 4 RX/TX single-function dual-redundant MIL-STD-1553B Notice II Channels supported

Each channel can be configured as BC, RT, or BM

Up to 31 RTs supported per RT channel

1 MB of RAM per channel

45-bit message time-tagging

User-selectable direct or transformer output coupling

Application Fields
Bus voltage user-configurable at a static or variable level during run time

Mode code support

BC (bus controller) features BC messaging schedule lists supported

Control of major and minor frame content and timing

User-configurable No Response timeout

User-configurable Late Response timeout

User-configurable minor frame period

Data and mode code transmit and receive

Precise time-stamping of TX and RX data

RT (remote terminal) features Multiple RT simulation (up to 31 RTs) per channel

RT31 configurable as a broadcast node

32 transmit and 32 receive subaddresses (SAs) per RT, 32 words of data per SA

Software
RT node configuration supports changing status word during run time

Blocks for RX/TX of data and mode codes, including broadcast (RT31)

BM (bus monitor) features 45-bit, microsecond resolution time-tagging

Using
the real-time processor of the DS1005, DS1006 or DS1007 Processor Board, up to
100 messages can be monitored and captured simultaneously with the Bus Monitoring Block
Physical connections Transition cable to MIL-STD-1553 jacks provided

Supported standards PMC Mezzanine Card

MIL-STD-1553B Notice II


Physical size Full-length ISA board

Hardware
Ambient temperature 0 ... +70 °C (32 ... 158 °F)

Power supply +5 V ±5%, 7-10 A

Order Information

Interface to MIL-STD-1553 Please inquire
Engineering

RTI

DS4504 MIL-STD-1553B Interface1) (DS1005, DS1006, DS1007)
–
1)

Required DS4504 PMC Carrier Board
DS4504

QPM-1553-2S, QPM-1553-4S (2 or 4 channel module,
–
GE Intelligent Platforms)
CF card with QNX® OS Kontron ETX module
–
471
2016

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
Supports up to 32 transmit and receive channels

Comprehensive Simulink® block library


The ARINC 429 Interface is used to connect dSPACE simu- Easy configuration of each IP module via a setup block

lators and prototyping systems to the ARINC 429 avionics Data manipulation blocks

data bus. It enables dSPACE HIL simulators to be used for Supports advanced testing by inducing predefined

testing aircraft electronics, at both the subsystem and the errors in a message
complete-vehicle level (Integrated Flight Testing facilities), Full software support for C handcoded applications

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.
Hardware and Software ARINC 429 Bus

The interface consists of the IndustryPack (IP) module car- The ARINC 429 specification defines how avionics equipment
rier board DS4501 and the IP-429HD-44P module from GE and systems should communicate with each other. It is an
Intelligent Platforms. On the real-time model side, a Simulink industry standard that is used on virtually all commercial
block library and S-functions are provided to access the IP aircraft. The resulting bus system is the most commonly
module and its receive and transmit channels. The block used data bus for commercial and transport aircraft. It
library provides access to the ARINC 429 bus on raw value employs unidirectional transmission of 32-bit words over
level, i.e., transmit and receive blocks in the model work two twisted pairs. Messages are transmitted at a bit rate of
with 32-bit ARINC 429 words without distinguishing bet- either 12.5 or 100 kilobits per second to other system
ween data bits. elements that monitor the bus messages. It supports one
transmitter and up to 20 receivers per channel.
472
2016

Introduction
Technical Details
General Up to 4 ARINC 429 IP modules supported

8 receive and 8 transmit channels per module

Adjustable receiver thresholds and transmitter output voltages

Application Fields
Automatic slew rate adjustment

Receive features Data rates 12.5 kbit/s

100 kbit/s

Standard input levels ±6.5 to ±13 VDC

Parametric threshold levels ±0.1 to ±13.5 VDC (A to B)

Transmit features Data rates 12.5 kbit/s

100 kbit/s

Standard output level ±10 VDC (A to B)

Parametric output voltages 0 to ±10 VDC (A to B)

Scaling Adding a scaling factor based on the data format type to increase the resolution of the 19-bit

data of a 32-bit ARINC-word
Software
Transmission rates Multiple transmission rates for multiple labels

Error injection Supports BCHI, BCLO, GAP error injections per channel and PARITY error injection per label

Failure simulation Label failure simulation by enabling/disabling labels during run time

Supported standards IndustryPack™

ARINC 429


Physical Physical size Full length ISA board

characteristics Ambient temperature 0 ... +70 °C (32 ... 158 °F)

Power supply +5 V ±5%, 36 mA (plus 77 mA per IP module)

±12 V ±5%, 11 mA per IP module

Hardware
Order Information

ARINC 429 Interface Please inquire
Engineering
Required Real-Time Interface (RTI) (p. 56)1)
RTI

dSPACE ARINC 429 Block library1) (DS1005, DS1006, DS1007)
−
Optional Bus Tool ARINC 2.61 from GE Intelligent Platforms
−
1)

Included DS4501 IP carrier board
DS4501

ARINC IP-429HD-44P module, version 4
−
(GE Intelligent Platforms)2)
For support of further ARINC 429 modules, please contact dSPACE.
2)
473
2016

ARINC 717 Interface

Interface to the ARINC 717 avionics data bus
Highlights
Connects modular dSPACE real-time systems

to the ARINC 717 data bus
Simulink® block library


The ARINC 717 Interface is used to connect dSPACE simu- Easy configuration of each IP module via a setup block
lators and prototyping systems to the ARINC 717 avionics Data manipulation blocks
data bus. ARINC 717 is used in avionics systems to commu- Supports advanced testing by inducing predefined
nicate with flight data recorders. The interface enables errors in a message
dSPACE systems to be integrated with such network com- Full software support for handcoded C applications
munication, a typical example being the HIL simulation of
an aircraft for testing avionics in integrated flight testing
(ITF) applications. The ARINC 717 interface supports multi-
ple channels and even multiple buses, so control applications
can comprise several devices.

The interface consists of the DS4501 IP Carrier Board and
the IP-717-HBP 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 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.
474
2016

Introduction
Technical Details
General Up to 4 IP modules supported

1 RX and 1 TX channel per IP module

Receive features Bit rates 768, 1536, 3072, 6144, 12288 or 24576 bit/sec

Standard input levels ±5 V differential

User-selectable subframe size 64, 128, 256, or 512 words (12-bit word size)

Application Fields
Receive buffer 4 KB

User-selectable receive rate 4 times subframe size received at specified rate

Wrap mode supported User-selectable per channel

Transmit features Bit rates 768, 1536, 3072, 6144, 12288 or 24576 bits/sec

Standard input levels ±5 V differential

User-selectable slew rate 1.5 or 10 µs

User-selectable subframe size 64, 128, 256, or 512 words (12-bit word size)

Receive buffer 4 KB

User-selectable transmission rate
Enable/disable during run time
Supported standards Industry Pack
Software

ARINC 717 HBP (Harvard Bi-Phase)


Physical characteristics Physical size Full length ISA board

Ambient temperature 0 ... +70 °C (32 ... 158 °F)

Power supply +5 V ±5%, 36 mA (plus 83 mA per IP module)

+12 V, 39 mA per IP module

-12 V, 39 mA per IP module

Hardware
Order Information

ARINC 717 Interface Please inquire


RTI

Engineering
DS4501 ARINC 717 Interface (DS1005, DS1006, DS1007)
–

Included DS4501 IP Carrier Board
DS4501

ARINC IP-717-HBP module (GE Intelligent Platforms)
–
475
2016

Modular Hardware / FPGA Base Board
FPGA Base Board

For highresolution signal preprocessing
Highlights
FPGA application-specific-programmable on

a per project basis
Piggyback module with application-specific I/O drivers

S-functions programmed on a per project basis to access

I/O from real-time applications

The FPGA Base Board has been designed for applications The FPGA code and the piggyback module for the
that require very fast, high-resolution signal preprocessing, FPGA Base Board are always tailored to specific applica-
for example: tions, according to customers‘ specifications, and can
High-precision digital capturing of 3-phase PWM be adapted to other projects. Algorithms for real-time
signals. applications with high sampling rates can be shifted to the
Simulation of engine speed/position sensors for electric FPGA (field programmable gate array). The time resolution
motors. of the signals depends on how the FPGA is programmed.
Fast current/voltage measurements, connection of diverse The reference frequency for the control loop is set in the
position encoders and control of AC motors digital frequency synthesizer (DFS). Even with complex FPGA
Electric motor simulation algorithms, the typical working range is 40 ... 80 MHz. The
Connection of dSPACE real-time systems to EtherCAT piggyback module allows flexible integration of I/O drivers
networks as slaves and special combinations of analog/digital inputs/outputs
and bus drivers.
476
2016

Modular Hardware / FPGA Base Board
Introduction
Technical Details
General Customization module site for a piggyback module providing customer-specific I/O adaptations

180
I/O lines from piggyback module to FPGA
18
I/O channels from piggyback module to a Sub-D connector on the board‘s rear bracket
Additional I/O channels available via an additional bracket to a Sub-D connector

FPGA Xilinx® Spartan®-3 XC3S4000

System gates: 4 million

Application Fields
Equivalent logic cells: 62,208

CLBs: 6912

Distributed RAM: 432 kbit

Block RAM: 1728 kbit

96 dedicated multipliers

4 digital clock manager (DCMs)

Host interface One 16-bit ISA slot (power supply only)

Physical Physical size 340 x 125 x approx. 20 mm
(13.4 x 4.9 x approx 0.8 in). The actual height depends on
characteristics the specific piggyback module.
Piggyback module size 123.5 x 114.3 mm (4.86 x 4.5 in)

Ambient temperature 0 ... 70 ºC (32 ... 158 ºF)

Software
Power supply +5 V ±5%, 500 mA (without piggyback module)

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

FPGA Base Board DS5202

Hardware

Required Engineering by dSPACE
See p. 608 (dSPACE Engineering Services)

Required Piggyback module
Please inquire
Engineering
477
2016

Modular Hardware / PWM Measurement Solution
PWM Measurement Solution

Capturing of PWM signals
Highlights
High-precision digital capturing of 3-phase

PWM signals
Fast signal measurement and analysis

RTI blockset for MATLAB®/Simulink®

Purpose Use Case

dSPACE offers you a PWM measurement solution based A typical use case is a hardware-in-the-loop (HIL) simulation,
on the DS5202 FPGA (field programmable gate array) Base where the electric motor including the electronic power
Board. It is specially designed for high-precision digital cap- stage is simulated by means of the dSPACE modular real-
turing of 3-phase PWM signals such as those typically used time hardware. Simulation models like dSPACE Automo-
for controlling a 3-phase AC electric motor. tive Simulation Models – ASM Electric Components Library
Efficient testing of electronic control units (ECUs) for electric (p. 269) are used for simulating electric components. The
machines requires fast measurement and analysis of several gate driver signals (typically PWM signals) coming from a
closely associated signals. The challenge is to capture these controller are measured by the DS5202 PWM measurement
signals with a very short sample time, e.g. <20 µs. solution. The calculated motor current signals are sent back
to the controller by means of analog voltage signals.
Application
The DS5202 PWM solution combined with a simulation is generated and an interrupt is triggered. To measure the
model allows you to measure the signals of up to 4 electric gate time, there are three operating modes to choose from:
machines with up to 8 power switch control signals each, software polling, external interrupt source, and internal pulse
for example, IGBTs (insulated-gate bipolar transistors). The center interrupt source, meaning clock generation based on
combined signals of up to 4 inverter legs can be evaluated the measured PWM signals. If you do not have access to the
for verifying the ECU’s functions. For example, if the dead ECU’s clock rate, PWM-based clock generation is the most
time does not reach the predefined minimum, an error flag suitable way of avoiding beat effects in the simulation.
478
2016

Modular Hardware / PWM Measurement Solution
Introduction
Application Fields
u1 v1 w1
v1 v1
u2 v2
w2
v2 v2
u1 ...
IGBT control signals Model of 3 inverter legs Electric machine model
ECU HIL simulation
Software
Features
Measuring duty cycles and periods of up to 32 PWM Multiple interrupt generation in one period (oversampling)

signals Reducing the sampling rate of generated interrupt signal

Separate group access via Simulink® interface. Capture (downsampling)
mode adjustable for each group independently. Using an external trigger as a latch source for the time

Measuring phase shifts between two half-bridges measurement
Evaluating dead time between adjacent channels Using an external trigger as an interrupt for the real-time

Hardware
Interrupt generation if the measured dead time is model
less than a predefined value High timing resolution

Generating interrupts and triggers to external devices Adjustable debounce time

at the center position of the PWM period
Technical Details
Order Information
Engineering
Timing resolution 25 ns

Digital input
Number of channels 32


Input voltage range 0 ... +15 V

I/O piggyback module for DS5202 PWM application DS5202_PWM

Two adjustable threshold values 2.5 or 7.5 V
Simulink Interface for DS5202 PWM application DS5202_PWM_BS

Input resistance 10 kΩ

Resolution 25 ns ... 400 ns (adjustable)

Digital output
Relevant Software
Number of channels 4 (shared with digital inputs)

Output voltage range 0 ... +5 V

Used for PWM center trigger generation
Frequency range 39 Hz to 40 MHz
Required RealTime Interface (RTI) RTI

479
2016

Modular Hardware / Position Sensor Simulation Solution
Position Sensor Simulation Solution

Simulation of position sensors
Highlights
Simulation of various position sensors

High timing resolution

RTI blockset for MATLAB®/Simulink®

Purpose Use Case

The PSS (position sensor simulation) solution is based on A typical use case is a hardware-in-the-loop (HIL) simu-
the DS5202 FPGA Base Board. It is specially designed for lation incorporating electric motor simulation. The PSS
simulating typical position sensors such as resolvers or solution provides the necessary position signals for
incremental encoders. the ECU.
Application
The board is equipped with four independent angular pro- with a high timing and angular resolution. You can define
cessing units (APUs) that receive the angular velocity from the APU´s offset position freely for every sensor and adjust
the model and calculate the position signal. Since each the board precisely to your requirements by configuring all
APU’s sample time is 25 ns, it provides a position signal the important parameters.
Features
Two digital and two analog sensors (three signals each) Resolver failure simulation:

can be simulated in parallel. Amplitude deviation: (dos – degradation of signal)

Different sensor types are possible Angle deviation: (lot – loss of position tracking)

Analog type: resolver, sinus encoder, user-defined APU-angle-dependent arbitrary waveform generation:

waveform Analog: 16384 values (-10 V ... 10 V)

Digital type: TTL encoder, Hall position sensors, Digital: 8192 values TTL

user-defined waveform High precision and high timing resolution

The analog and digital sensor simulation groups can be On-board signal conditioning

arbitrarily allocated to up to four independent simulated Full differential I/O

shafts (APUs). Four sensors can be simulated per simu-
lated shaft.
480
2016

Introduction
Resolver simulation:
One primary analog input and two modulated
analog outputs (sines and cosines).
Application Fields
Software
Digital incremental encoder simulation:
Hardware
Two 90° phase-shifted digital signals and one
index signal.
Engineering
481
2016

Technical Details
APU (Angular Processing Unit)
Number of independent APU units 4

APU angle precision 32 bit

APU update rate 25 ns / 40 MHz

APU speed range Up to ±292,969 rpm

Analog Sensor Simulation
Number of analog sensors 2

Sensor types Resolver, sine encoder, user-defined waveform

Number of pole pairs 1 ... 16,383

Adjustable angle offset -360 ... +360°

Resolver accuracy 0,1° (depending on the settings)

Resolver transformation ratio 0 ... 16 (typically 0.5)

Resolver Failure Simulation Additional delay for resolver feedback signals Up to 409.6 µs

Amplitude error (degradation of signal (dos)) -100 ... +100%

Phase error (loss of position tracking (lot)) -90 ... +90°

User-defined waveform resolution (16384 values) 0.02197°

Analog Inputs Channels 2 channels

Input range ±30 V (differential)

Resolution 14 bit pipelined

Protection ±60 V

Resolver excitation-coil simulation 220 Ω / 2 W

Analog Output (Cosine/Sine) Channels 4 channels

Output range ±10 V single-ended (±20 V differential or transformer mode)

Resolution 12 bits (of user-specified output range)

Sampling rate 10 MSPS

Output mode Transformer or direct output

Protection ±60 V

Analog Output (Index) Channels 2 channels

Output range ±10 V

Resolution 12 bit


Output mode Single-ended output

Protection ±60 V

482
2016

Introduction
Digital Sensor Simulation
Number of digital densors 2

Application Fields
Sensor types TTL encoder, Hall encoder, user-defined waveform


User-defined waveform resolution 0.0439°

(8,192 values)
Digital Output Channels 6 channels (each with inverted output stage)

Output range 0 ... +5 V

Sample rate 25 ns / 40 MHz

Output current 20 mA

Protection ±60 V

Software
Order Information


I/O piggyback module for DS5202 PSS application DS5202_PSS

Simulink Interface for DS5202 PSS application DS5202_PSS_BS

Relevant Software
Hardware
Required Real-Time Interface (RTI) RTI

Engineering
483
2016

Modular Hardware / AC Motor Control Solution
AC Motor Control Solution

Control of diverse AC motors
Highlights
Fast current/voltage measurements

Control of AC motors, e.g., asynchronous motors (ASMs),
brushless DC motors (BLDCs) and permanent magnet
synchronous motors (PMSMs)
Suitable PWM generation for electric drives

Connection of diverse position encoders

RTI Blockset for MATLAB®/Simulink®

Purpose
The AC Motor Control Solution is based on the DS5202 control prototyping of AC motors requires fast I/O, which is
FPGA Base Board or on the MicroAutoBox with the DS1514 fullfilled by using an FPGA Base Board and the appropriate
FPGA Base Board. piggyback module, with the control algorithms running on
These are specially designed for fast current / voltage mea- the main processor. The interface between the user's control
surements, connecting diverse position encoders and control- model and the AC Motor Control hardware is implemented
ling AC motors such as ASMs, BLDCs and PMSMs. Rapid by using the AC Motor Control Solution RTI Blockset.
Use Case Applications

Typical use cases for the AC Motor Control Solution are Measurements (of phase currents and/or voltages,
highly dynamic control systems for different types of AC and DC link currents or voltages) and ADC starts can
motors. be synchronized to PWM signals.
Some scenarios: Position and speed measurements using typical sen-
Field-oriented control of PMSMs or ASMs sors such as Hall sensors or incremental encoders,
Control of BLDCs resolvers, or typical single/multiturn encoders with
Prototyping new methods for sensorless control serial interfaces (EnDat or SSI)
Using RapidPro Power Unit with suitable modules or Generation of gate driver signals (center-aligned
customer-specific power converters 3/6 PWMs for sinusoidal commutation or PWM signals
for block commutation or advanced customer-specific
To use the AC Motor Control Solution in a vehicle, you can PWM patterns)
install it in the dSPACE AutoBox or use the MicroAutoBox Synchronization of ADC measurement with center-
variant. For stationary use, it can be installed in an expan- aligned PWM signals (regular sampling)
sion box. Model synchronization by interrupt generation at the
center position of the PWM or at user-defined motor
angles.
Trigger signal to external devices at the center position
of the PWM.
484
2016

Introduction
PHS Bus
DS1005/DS1006/
DS1007
Control signals
Application Fields
or
Current signals
Piggyback module
DS5202
used inside
EV1048 MicroAutoBox II
Resolver, SSI,
Hall / Encoder
EnDat
Software
RapidPro Power Unit
RTI Blockset Motor
For more information about installing piggyback modules

with MicroAutoBox II, please see p. 548.
Hardware
Engineering
485
2016

Technical Details (AC Motor Control Solution for Modular System)

Digital input 8 channels, 0 ... 5 V, differential or single-ended. Default: 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
Digital output 10 channels, 0 ... 5 V, single-ended; 6 gate driver signals, 4 generic digital outputs (e.g. PWM synchronization

signals or bit out)
Gate driver frequency 10 Hz ... 1 MHz

12 additional gate driver signals available by using the ACMC Extension Board

ADC 8 channels, software-configurable inpult voltage range (± 5 V, ± 15 V, ± 30 V), differential, 10 MSPS

DAC 2 channels, -10 ... 10 V (single-ended) 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 within 250 Hz steps (software-configurable)
RS422/RS485 SSI or EnDat for connection of single/multi turn encoder

4 RS485 transceivers for connecting 2 serial angle meters (EnDat or SSI interface)

Power supply for sensors 5 V and 12 V, 140 mA

Order Information

DS5202 AC Motor Control DS5202_ACMC

DS5202 ACMC PWM Extension Board DS5202_ACMC_EXT

DS5202 AC Motor Control Blockset DS5202_ACMC_BS


Included with DS5202 FPGA firmware for AC motor control application –


Included with I/O piggyback module Bracket for connection of I/O and mating connectors –
486
2016

Introduction
Technical Details (AC Motor Control Solution for MicroAutoBox II)
Digital input 8 channels, 0 ... 5 V, differential or single-ended, configurable by software

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
Application Fields
Digital output 16 channels, 0 ... 5 V, single-ended to generate gate driver signals, PWM synchronization signals, bit out

8 additional channels by modifying IP-module pins

Gate driver frequency 10 Hz ... 1 MHz

ADC 8 channels, software-configurable inpult voltage range (±5 V, ±15 V, ±30 V), differential, 10 MSPS

DAC 2 channels, -10 ... 10 V (single-ended) 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 (software-configurable)
RS422/RS485 SSI or EnDat for connection of single/multi-turn encoder

4 RS485 transceivers for connection of 2 serial angle meters (EnDat or SSI interface)

Power supply for sensors 12 V: max. 50 mA

5 V: max. 50 mA (use the MicroAutoBox II VSENS-PIN for currents up to 250 mA)

Software
Order Information

DS1553 ACMC Module MABXII_ACMC

MicroAutoBox II AC Motor Control Solution Blockset MABXII_ACMC_BS

Hardware

Included with DS1553 FPGA firmware for AC motor control application –


MicroAutoBox II with DS1514 FPGA Board MicroAutoBox II 1401/1511/1514 MABX_II_1511/14

Engineering
MicroAutoBox II with DS1514 FPGA Board MicroAutoBox II 1401/1513/1514 MABX_II_1513/14

487
2016

Modular Hardware / EMH Solution
EMH Solution
Electric motor simulation
Highlights
High-precision digital capturing of

3-phase PWM signals
Fast signal measurement and analysis

Simulation of various position sensors

High timing resolution

Various additional multipurpose signals

RTI Blockset for MATLAB®/Simulink®

Purpose Use Case

The EMH (electric motor HIL) solution is based on the DS5202 A typical use case is a hardware-in-the-loop (HIL) simulation
FPGA Base Board. It gives you all the I/O channels that are where the electric motor including the electronic power
needed for HIL simulation of electric motors, such as high- stage is simulated by means of the dSPACE modular real-time
precision digital capturing of 3-phase PWM signals and hardware. Simulation models like dSPACE Automotive Simu-
position sensor simulation, plus several digital and analog lation Models – ASM Electric Components Library (p. 269) are
I/O channels. It combines the features of the DS5202 PWM used for simulating the electric components. The gate driver
and PSS solutions with many additional multipurpose chan- signals (typically PWM signals) coming from a controller are
nels, and enables efficient testing of electronic control units measured by the DS5202 EMH solution, and calculated
(ECUs) for electric motors on a single I/O board. 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.
Application
The DS5202 EMH solution combined with a simulation The current feedback signals for the ECU can be simulated
model allows you to measure the signals of up to 2 electric by using the board’s fast analog output channels. For posi-
machines with up to 8 power switch control signals each, tion sensor simulation, the board is equipped with four
for example, IGBTs (insulated-gate bipolar transistors). There independent angular processing units (APUs) that receive the
is a choice of three operating modes: software polling, angular velocity from the model and calculate the position
external interrupt source, and internal pulse center interrupt signal. Since each APU’s sample time is 25 ns, it provides a
source, meaning clock generation based on the measured position signal with a high timing and angular resolution.
PWM signals, which is the most suitable way of avoiding
beat effects.
488
2016

Introduction
PHS bus
DS1005/DS1006/DS1007 Processor Board
DS5202
Gate control signals
Application Fields
I/O module
Current signals ECU
Hall/encoder
Resolver
RTI Blockset
Software
PWM Measurement
Features
Measuring duty cycles and periods of up to 16 PWM Oversampling and downsampling for interrupt generation

signals Using an external trigger as a latch source for the time

Separate access by groups of 8 channels via Simulink® measurement and interrupt for the real-time model
interface. Capture mode adjustable for each group 16 channels can alternatively be used as general purpose

Hardware
independently inputs (digital or PWM inputs)
Evaluating dead time between adjacent channels High timing resolution

Generating interrupts and triggers to external devices Adjustable debounce time

at the center position of the PWM period Measuring phase shifts between two half-bridges

Position Sensor Simulation

Features Engineering
One digital and one analog sensor (three signals each), All sensor simulation groups can be arbitrarily allocated

one protocol-based sensor and three independent angle- to up to four independent simulated shafts (APUs).
based digital signals can be simulated in parallel. Resolver failure simulation (please refer to PSS solution)

Different sensor types are possible: APU-angle-dependent arbitrary waveform generation

Analog type: resolver, sinus encoder, user-defined (please refer to PSS solution, p. 480)
waveform High precision and high timing resolution

Digital type: TTL encoder, Hall position sensors, On-board signal conditioning

user-defined waveform Full differential I/O for all analog signals

Protocol type: SSI, Hiperface® or EnDat sensor simulation
489
2016

Multipurpose Channels
Features
7 analog output channels Channels of the PWM measurement and position sensor
4 analog input channels simulation can alternatively be used as standard multi
10 digital output channels purpose I/O.
1 digital input
Shared I/O
3 analog output channels 3 digital/PWM output channels

2 analog inputs channels RS485 full duplex UARTS used for serial sensor simula-

16 digital/PWM input channels tion or LTI ServoOne TWINsync communication
6 digital output channels
Technical Details – PWM Measurement
Number of channels 16

Resolution Max. 12.5 ns (80 Mhz) - 400 ns (adjustable)

Center-aligned capture groups 2 (each group has 8 channels)

Input voltage range 0 ... +30 V

Adjustable thresholds +1 ... +8.5 V

Input resistance 24 kΩ

Protection ±50 V

490
2016

Introduction
Technical Details – Position Sensor Simulation
APU (Angular Processing Unit)
Number of independent APU units 4

Application Fields
APU angle precision 32 bit

APU update rate 25 ns / 40 MHz

APU speed range Up to ±292,969 rpm

Analog Sensor Simulation
Number of Analog Sensors 1

Sensor types Resolver, sine encoder, user defined waveform

Software

Adjustable angle offset -360 ... +360°

Resolver accuracy 0.1° (depending on the settings)

Resolver transformation ratio 0 ... 16 (typ. 0.5)

Resolver Failure Simulation Additional delay for resolver feedback signals Up to 409.6 µs
Amplitude error (dos ... degradation of signal) -100 ... +100%
Phase error (lot ... loss of position tracking) -90 ... +90°

User defined waveform resolution (16,384 values) 0.02197°

Analog Input (Resolver Excitation Input) Channels 1 channel

Input range ±30 V (differential)
Hardware

Resolution 14 bit pipelined


Protection ±50 V

Resolver excitation-coil simulation 220 Ω / 2 W

Analog Output (Cosine / Sine) Channels 2 channels

Output range ±10 V single ended (±20 V differential / transformer mode)

Resolution 12 bit (of user specified output range)


Output mode Transformer or direct output
Engineering

Protection ±50 V

Analog Output (Index) Channels 1 channel

Output range ±10 V single ended (±20 V differential)

Resolution 12 bit


Output mode Direct output (with inverted output stage)

Protection ±50 V

491
2016

Digital Sensor Simulation
Number of digital sensors 1 (+3
independent angle based outputs)
Sensor types TTL encoder, hall encoder, user defined waveform; (+3 independent angle-based outputs)


User defined waveform resolution (8,192 values) 0.0439°

Digital Output Channels 6 channels (3 channels with inverted output stage)

Output range 0 ... +5V

Sample rate 25 ns / 40 MHz

Output current 20 mA

Protection ± 50 V

Serial Sensor Simulation
Number of serial sensors 1

Sensor types SSI-Encoder, Hiperface Encoder, EnDAT Encoder

Number of multi turn bits 0 to 14

Number of single turn bits 1 to 18

RS485 Channels 2 full-duplex channels

Maximum data rate Up to 10 Mbps

Protection ±50 V

Technical Details – Multipurpose Channels

Analog outputs 6 channels; ±10 V output voltage range;

12 bit; 10 MSPS; differential; Protection ±50 V
1 channel; ±10 V output voltage range;

14 bit; 1 MSPS; single ended; Protection ±50 V
3 channels; ±10 V output voltage range;

12 bit; 10 MSPS; Protection ±50 V; shared with analog sensor simulation
Analog inputs 4 channels; ±30 V input voltage range;

16 bit; 1 MSPS; differential; Protection ±50 V
2 channels; ±30 V
input voltage range;
14 bit; 10 MSPS; differential; Protection ±50 V; shared with resolver simulation
Digital inputs 1 channel; 0 ... +30 V; Protection ±50V

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
Global adjustable threshold voltage +1 ... +8.5 V
Digital outputs 10 channels; 0 ... +5V output voltage range; Protection ±50 V

6 channels; 0 ... +5 V output voltage range; Protection ±50 V; shared with digital sensor

simulation
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 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
492
2016

Introduction
Order Information


I/O piggyback module for DS5202 EMH application DS5202_EMH

Simulink Interface for DS5202 EMH application DS5202_EMH_BS

Application Fields
Relevant Software


Software
Hardware
Engineering
493
2016

Modular Hardware / EtherCAT Slave Interface
EtherCAT Slave Interface

Slave interface to an EtherCAT communication bus
Highlights
Connects dSPACE real-time systems to EtherCAT

networks as slaves
Dual-port memory for data exchange with processor

board
RTI EtherCAT Blockset for MATLAB®/Simulink®


The dSPACE EtherCAT slave interface connects a dSPACE The dSPACE EtherCAT slave interface enables you to take
real-time system to the Ethernet fieldbus EtherCAT as a advantage of the very high performance of an EtherCAT
slave. Typical use cases for the EtherCAT slave interface are network, which supports 100 Mbit/s and cycle times down
real-time applications in automation technology, such as to 50 μs.
process automation or test benches.
EtherCAT Hardware and Software

EtherCAT is an open, high-performance, Ethernet-based The EtherCAT slave interface consists of the DS5202 FPGA
fieldbus system and is especially designed for automation Base Board with a piggyback module, which carries up to
applications which require short cycle times and low com- two Beckhoff EtherCAT modules FB1111-0140. The bracket
munication jitter. The EtherCAT slave device reads the data features two RJ45 plug sockets for connection to the
addressed to it and also inserts input data while the telegram EtherCAT network.
passes through. The frames are only delayed by a fraction The EtherCAT blockset mainly consists of a base library and a
of a microsecond in each node, and many nodes can be template model generator. A model containing all the neces-
addressed with just one frame. EtherCAT is an international sary blocks is generated from a configuration M-structure
standard (for more information, see www.ethercat.org). that has to be created by the user.
494
2016

Modular Hardware / EtherCAT Slave Interface
Introduction
Technical Details
General Direct connection to the field bus

Dual-port memory for data exchange with processor board

Two RJ45 connectors for connection to the network

Two slave modules

Object dictionary can be created according to CiA DS404

Cyclic communication Up to 6 sync managers per module whose type (input/output) can be defined freely

Application Fields
Static PDO mapping and PDO assignment

7 KB can be used for cyclic communication (3-buffer mode)

CAN application layer over EtherCAT communication Input and output mailbox with 512 bytes each

Template model generation Template model and device description file (DDF) are generated according to configuration script

and base library
Ensures consistency between DDF and template model

Generation process contains consistency checks on user‘s configuration

Multirate modeling Each sync manager block can be placed in its own task

EtherCAT interrupts (distributed clocks, sync manager interrupts) are available to synchronize

the model to EtherCAT events
Supported standards EtherCAT


Software
Physical Physical size Full-length ISA board

characteristics 2 slots required (3 slots when using two connector adapters)

Power supply +5 V ±5%

Order Information

EtherCAT Slave Interface Please inquire
Hardware


Included EtherCAT Slave Blockset
–
RTI

Engineering
Included FPGA Base Board
DS5202

I/O piggyback module for EtherCAT
–
Two Beckhoff EtherCAT modules FB1111-0140
–
Bracket for connection to EtherCAT network
–
495
2016

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
Data transmission for customer-specific bus system

Simulink® block library


The 100 Mbit/s Ethernet Interface connects a modular The dSPACE Ethernet Solutions supports variable length
dSPACE real-time system to an Ethernet network. It enables frames for sending and receiving with datagram up to a
you to transmit data between dSPACE processor boards payload size of 65507 bytes. It also supports TCP (Transmis-
(DS1005, DS1006, DS1007 or multiprocessor system) and sion Control Protocol) single point-to-point communication.
a remote computer system. Its application areas are hard- The UDP/IP and TCP/IP protocols are executed on the ETX.
ware-in-the-loop simulation and rapid control prototyping, The dynamic or static IP address of the ETX module comes
where simultaneous communication runs via one or more with auto negotiations features. Your Ethernet configuration
network nodes. Data transmission between the processor is downloaded to DS4504 and initialized by startup.
board and a customer-specific bus system can also be imple-
mented by using an appropriate gateway computer con-
nected to the Ethernet network.

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.
496
2016

Modular Hardware / 100 Mbit/s Ethernet Interface (UDP/IP, TCP/IP)
Introduction
Technical Details
General DS4504 ETX carrier board with ETX module

Simultaneous communication with one or more networks

Communication with processor board via PHS++ (Peripheral High Speed) bus

Multiprocessor-capable

Receive/transmit features Dynamic or static IP address with auto negotiation features

TCP single point-to-point (client/server) communication

Application Fields
Variable length frames for sending and receiving

Support of datagram up to payload size of 65507 bytes

Sending and receiving (multiple) TCP and UDP frames to user-defined IP addresses and ports

Physical Physical size 95 x 114 mm (3.7 x 4.7 in)

characteristics Ambient temperature 0 ... +60 °C (32 ... 140 °F)

Power supply +5 V ±5%, 6-9 A

Order Information
Software
100 Mbit/s Ethernet Interface Please inquire

RTI

DS4504 Ethernet Basic Blockset1)
DS4504_ETH_SOL

1)
Hardware
Required DS4504 PMC Carrier Board
DS4504

Kontron ETX module
DS4504_ETX_CD166_2GB

DS381 Ethernet Connector Board
DS381

Engineering
For an overview of dSPACE products for establishing

an Ethernet connection, please see p. 92.
497
2016

Modular Hardware / Additional I/O Solutions
Additional I/O Solutions

I/O to your specifications
Highlights
Solutions for I/O and buses not covered by

our standard boards
Development of customer-specific I/O boards

for non-standard I/O
Programming of advanced I/O functions and

Simulink® S-functions
Key Benefits I/O Solutions

The list of I/O solutions which dSPACE has developed in The following pages give just a few examples of dSPACE’s
response to customer requirements is extensive. The need additional I/O solutions:
for such solutions arises when situations cannot be covered
by our off-the-shelf boards. Some I/O solutions establish DS1006 Advanced Support Package

connections to field-bus-based systems and industrial or 10 Mbit/s Ethernet Interface (UDP/IP)

aerospace buses. In general, I/O solutions typically consist Programmable Generic Interface (PGI1)

of integrated hardware and software. Battery Cell Voltage Measurement and Balancing

Resolver Interface

You can also create your own solution based on the DS4201
Prototying Board (p. 440), or dSPACE can provide a solution
for you.
dSPACE Engineering Services (p. 608)
Order Information

Additional I/O solutions Please contact dSPACE if you are interested in additional I/O solutions.
498
2016

Introduction
DS1006 Advanced Support Package
Uses the 4th core of the DS1006 Processor Board for

a Linux application to establish an Ethernet interface or
to implement customer-specific solutions
Application Fields
Hardware Details
DS921 connector bracket for direct mounting
on the DS1006 Processor Board
1 GBit/s Ethernet interface
2 USB interfaces
The DS921 can be used in conjunction with the DS911
Gigalink Module (p. 385) on the same DS1006.
Software Details
Interface software based on a Linux application
Software
Data exchange between real-time application and
Linux application
10 Mbit/s Ethernet Interface (UDP/IP)
Hardware
Connects dSPACE’s modular hardware to Ethernet

bus (UDP/IP)
Hardware Details
Carrier hardware DS4502 with additional Ethernet
communication module (10 Mbit)
Dual-port memory for data exchange with master
processor
Engineering
9-pin Sub-D connector with RJ45 adapter for connec-
tion to Ethernet network
Software Details
Suitable for MotionDesk Multi-PC Interface Kit
UDP/IP protocol stack executed by module firmware
(without master processor load)
C functions for UDP/IP communication

Simulink S-function blockset available
499
2016

Programmable Generic Interface (PGI1)

Generic interface box for decentralized connection of

sensors and actuators to dSPACE systems via various
serial interfaces and protocols (250 Mbit/s LVDS inter-
face for PHS-, MicroAutoBox-, and MicroLabBox-based
dSPACE systems, or Ethernet for SCALEXIO-based
dSPACE systems (p. 318)
Emulation of sensor signals (e.g., of yaw rate or crash

sensors) with hardware-in-the-loop (HIL) simulation
Highly flexible adaptation to customer requirements

via piggyback modules and special FPGA firmware
Platform
PHS- and MicroAutoBox- MicroLabBox SCALEXIO®

Solution based systems (Configuration via (Configuration via
(Configuration via Simulink Blockset) ConfigurationDesk)
Simulink Blockset)
SPI Master Solution (supports up to 4 masters)  – –

SPI Slave Solution (supports up to 16 slaves)  – –
I²C 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)
500
2016

Introduction
Battery Cell Voltage Measurement and
Balancing
Application Areas
The Battery Cell Voltage Measurement and Balancing system
Application Fields
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’
Software
mode gives users complete freedom to balance cells indi-
vidually 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
Hardware
provides various safety features. These include warnings
about hardware, communication and synchronization errors,
and also about overheating, isolation faults, and cell under-
voltages and overvoltages.
Engineering
501
2016

Technical Details
Modular system supporting 4 to approx. 200 cells, in- Plug-on modules for quick replacement of balancing

stallable in a vehicle resistances. Resistance values of up to 10 Ω
24 cell voltages per module S-function-based Simulink® blockset (RTI Ethernet

24 cell temperatures per module (UDP) blockset additionally required)
Intersil® ISL78600 BMS IC Two balancing modes:

Cell voltage measured with up to ±2 mV accuracy Manual mode with full user control
Synchronized measurement of cell voltages, tempera- Configurable automatic mode
tures and current – independent of the number of cells Comprehensive error detection features

High sampling rate of 1 kSPS 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. 538).
For battery simulation via dSPACE´s Automotive

Simulation Models, see p. 268.
502
2016

Introduction
Resolver Interface
Connects dSPACE’s modular hardware to resolver sen-

sors
DS4501 IP Carrier Board hosting an IP module for

resolver-to-digital conversion from TEWS Technologies
Application Fields
(TIP150-41)
Hardware Details
DS4501 supports up to 4 IP modules
Each IP module can support 2 resolver sensors
Supports adaptable signal conditioning
Excitation signal can be set from 2 kHz ... 20 kHz,
11.8 Vrms (max), 70 mA
Detection of lost signals
Software
Software Details If you would like to simulate a resolver, please see
Simulink block library p. 480 for the Position Sensor Simulation Solution based
Configuration of each IP Module via a setup block on the FPGA Base Board.
Synchronous or asynchronous reading of resolver
If you would like to control an AC motor with a resolver,
channels
see p. 484 for the AC Motor Control Solution based on
Supports multiple range options
the FPGA Base Board, which provides both capabilities.
Supports single- or dual-channel reading
Hardware
Engineering
503
2016

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

Access digital signals via standard Sub-D connectors

Sub-D connectors are grouped according to I/O

channels or functional units
LED panels indicate the status of the board‘s digital

signals
All Panels at a Glance

Connector/LED
Connector Panel LED Panel
Board BNC Connectors Sub-D Connectors Combi Panel
Width1) Width1) Width1)
DS2001 5 ADC inputs – 2 MU – –
DS2002 32 ADC inputs – 10 MU – –
DS2003 32 ADC inputs, – 10 MU – –
1 trigger
DS2004 16 ADC inputs, − 7 MU – –
4 triggers
DS2101 5 DAC outputs – 2 MU – –
DS2102 6 DAC outputs – 2 MU – –
DS2103 32 DAC output – 10 MU – –
DS2201 20 ADC inputs, Digital I/O capture/ 10 MU 4 MU –
8 DAC outputs compare
DS2302 6 DAC/ADC Outputs/ Digital I/O 3 MU – –
Inputs
DS3001 – 5 incremental encoders 2 MU – –
DS3002 – 6 incremental encoders 3 MU – –
DS4002 8 timers, Digital I/O 4 MU – 12 MU
2 triggers
DS4003 – 3 digital I/O 4 MU – 7 MU2)
DS5001 16 waveform inputs – 5 MU – –
DS5101 16 waveform outputs, – 5 MU – –
1 reset
1)
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.
2)
Each CLP4003 serves only one of the three ports (32 lines).
504
2016

Introduction
Physical Dimensions and Weights
Connector Panel LED Panel Connector/LED Combi Panel

Board Size (w x h x d, without Approx. Size (w x h x d, without Approx. Size (w x h x d, Approx.
enclosure) weight enclosure) weight without enclosure) weight
DS2001 61 x 129 x 51 mm 0.45 kg − − − −
Application Fields
(2.4 x 5.1 x 2 in) (1 lb)
DS2002 305 x 129 x 51 mm 1.9 kg − − − −
(12 x 5.1 x 2 in) (4.1 lb)
DS2003 305 x 129 x 51 mm 1.9 kg − − − −
(12 x 5.1 x 2 in) (4.1 lb)
DS2004 213 x 129 x 51 mm 1.2 kg − − − −
(8.4 x 5.1 x 2 in) (2.6 lb)
DS2101 61 x 129 x 51 mm 0.2 kg − − − −
(2.4 x 5.1 x 2 in) (0.45 lb)
DS2102 61 x 129 x 51 mm 0.25 kg − − − −
(2.4 x 5.1 x 2 in) (0.55 lb)
DS2103 305 x 129 x 51 mm 0.9 kg − − − −
Software
(12 x 5.1 x 2 in) (2 lb)
DS2201 305 x 129 x 51 mm 1.7 kg 122 x 129 x 40 mm 0.2 kg − −
(12 x 5.1 x 2 in) (3.7 lb) (4.8 x 5.1 x 1.6 in) (0.4 lb)
DS2302 91 x 129 x 51 mm 0.7 kg − − − −
(3.6 x 5.1 x 2 in) (1.5 lb)
DS3001 61 x 129 x 43 mm 0.35 kg − − − −
(2.4 x 5.1 x 1.7 in) (0.8 lb)
DS3002 91 x 129 x 43 mm 1.1 kg − − − −
(3.6 x 5.1 x 1.7 in) (2.4 lb)
DS4002 122 x 129 x 51 mm 0.45 kg − − 365 x 129 x 51 mm 0.8 kg
Hardware
(4.8 x 5.1 x 2 in) (1 lb) (14.4 x 5.1 x 2 in) (1.8 lb)
DS4003 122 x 129 x 43 mm 0.9 kg − − 213 x 129 x 43 mm 1) 0.6 kg
(4.8 x 5.1 x 1.7 in) (2 lb) (8.4 x 5.1 x 1.7 in) (1.3 lb)
DS5001 152 x 129 x 51 mm 0.5 kg − − − −
(6 x 5.1 x 2 in) (1.1 lb)
DS5101 152 x 129 x 51 mm 0.5 kg − − − −
(6 x 5.1 x 2 in) (1.1 lb)
1)
(LED only
Engineering
505
2016

Order Information

Connector Panel DS2001 High-Speed A/D Board CP2001

DS2002 Multi-Channel A/D Board CP2002

DS2003 Multi-Channel A/D Board CP2003

DS2004 High-Speed A/D Board CP2004

DS2101 D/A Board CP2101

DS2102 High-Resolution D/A Board CP2102

DS2103 Multi-Channel D/A Board CP2103

DS2201 Multi-I/O Board CP2201

DS2302 Direct Digital Synthesis Board CP2302

DS3001 Incremental Encoder Interface Board CP3001

DS3002 Incremental Encoder Interface Board CP3002

DS4002 Timing and Digital I/O Board CP4002

DS4003 Digital I/O Board CP4003

DS5001 Digital Waveform Capture Board CP5001

DS5101 Digital Waveform Output Board CP5101

LED Panel DS2201 Multi-I/O Board LP2201

Connector/LED DS4002 Timing and Digital I/O Board CLP4002

Combi Panel DS4003 Digital I/O Board CLP40031)

1)
Order Information

Required 19‘‘ rack for connector and LED panels (14 MU) CP_Rack

(only one of these is required) 19‘‘ desktop box for connector and LED panels (14 MU) CP_Desk

506
2016

Introduction
Enclosure Options
Rack or Desktop Box?
There are two enclosure options for installing your
connector panel or LED panel:
19‘‘ rack (16.8‘‘ or 14 measurement units
Application Fields
(MU) usable, height 3 U)
19‘‘ desktop box (16.8‘‘ or 14 measurement units (MU)

usable, depth 2‘‘/51 mm without connector)
Software
Hardware
Engineering
507
2016

Accessories / Expansion Boxes
Expansion Boxes for Modular Hardware

Boxes for expanding the host PC for dSPACE systems
Highlights
Space for 3, 9 or 19 dSPACE boards

Including Link Board for connection to host PC

Several options for connection to host

AutoBoot option for stand-alone operation

Low noise emission and efficient vibration handling

Technical Details: PX4 Expansion Box

Chassis Desktop box

4 full-size 16-bit ISA slots

1 slot reserved for Link Board

1 additional slot required if AutoBoot option is used

Low-noise fan cooling

Can be used for rapid control prototyping only

Power supply 100 ... 240 V AC, 50 ... 60 Hz

80 W

Maximum output current1) 10 A at 5 V

3 A at 12 V

0.8 A at -12 V

Grounding Circuit ground is connected to the chassis and through that to the power

system‘s protective ground.

Weight (without boards) 3.5 kg (7.7 lb)

Ambient temperature2) 0 ... 50 °C (32 ... 122 °F)

Humidity 0 ... 95%, noncondensing

1)
The sum of the output currents of the rails must not exceed the maximum output power.
2)
The dSPACE processor and I/O boards have different maximum ambient temperatures. When they are installed together, the lowest maximum
ambient temperature is applicable.
508
2016

Introduction
Chassis Desktop box

19‘‘ rack-mount version available (height: 4 U, 4 HE)


Application Fields
1 slot reserved for Link Board or slot CPU board for Ethernet connection




250 W


10 A at 12 V

1 A at -12 V

Grounding Circuit ground is connected to the chassis and through that to the power

Physical characteristics Physical size 183 (includes 6 mm rubber feet) x 343 x 430 mm (7.2 x 13.5 x 16.9 in)


Software
Ambient temperature 2)
0 ... 50 °C (32 ... 122 °F)


1)
2)
Hardware
Chassis Desktop box

19‘‘ rack-mount version available (height: 4 U, 4 HE)


1 slot reserved for Link Board or slot CPU board for Ethernet connection




400 W at 100 ... 170 V AC

450 W at 170 ... 240 V AC

Engineering

12 A at 12 V

4 A at -12 V

Grounding Circuit
ground is connected to the chassis and through that to the power
Physical characteristics Physical size 183 (includes 6 mm rubber feet) x 443 x 535 mm (7.2 x 17.4 x 21.1 in)


Ambient temperature 2)
0 ... 50 °C (32 ...122 °F)


1)
2)
509
2016

Order Information
Order Number
Product
Ethernet Interface1) PCMCIA Link
PX4 – PX4/814/815

PX10 Desktop Box PX10N1
PX10/814/815

PX10 Rack-Mount Version PX10N1/Rack
PX10/814/815/Rack

PX20 Desktop Box PX20N1
PX20/814/815

PX20 Rack-Mount Version PX20N1/Rack
PX20/814/815/Rack

1)
Implemented via the host PC‘s own Ethernet port.
Order Information
Order Number
Product
PCI Bus Link ExpressCard: DS821 PCI Express
PX4 PX4/814/817/Opto
PX4/814/821
PX4/814/819/Opto

PX10 Desktop Box PX10/814/817/Opto
PX10/814/821
PX10/814/819/Opto

PX10 Rack-Mount Version PX10/814/817/Rack/Opto
PX10/814/821/Rack
PX10/814/819/Rack/Opto

PX20 Desktop Box PX20/814/817/Opto
PX20/814/821
PX20/814/819/Opto

PX20 Rack-Mount Version PX20/814/817/Rack/Opto
PX20/814/821/Rack
PX20/814/819/Rack/Opto

510
2016

Introduction
Connection to the Host PC
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
Application Fields
or optical link. There are Link Boards for connecting host
PCs with ISA, PCI, PCI Express, PCMCIA, ExpressCard or
Ethernet connections (p. 516).
Software
Hardware
Engineering
511
2016

Accessories / AutoBox
AutoBox/TandemAutoBox
Expansion boxes for invehicle use
Highlights
Robust housing

Power supply via car battery

For 12 V, 24 V and 48 V electrical systems

Improved cold start behavior


AutoBox is the ideal enclosure for using your modular AutoBox is a robust box for mounting processor boards and
dSPACE real-time system to carry out in-vehicle control I/O boards. It provides space for dSPACE hardware (7 slots
experiments such as test drives in the development of in the AutoBox, 15 slots in the Tandem-AutoBox). Designed
powertrains, chassis control or advanced driver assistance for in-vehicle use, AutoBox can operate with 12 V, 24 V
systems. You can install AutoBox quite easily in your test and 48 V power supplies under rough environmental con-
car, e.g., in the trunk or the passenger cabin. ditions.
512
2016

Introduction
Technical Details
Specification
Parameter
AutoBox Tandem-AutoBox
General Chassis Compact aluminum chassis, shock mounts with rubber shoes

Slots 7 full-size 16-bit ISA slots

1 slot reserved for link board or slot CPU board The rightmost slot is recommended for a short

for Ethernet connection (both not required for card like a link board or a slot CPU board for
Application Fields
PHS-bus systems based on DS1007) Ethernet connection.1)
Cooling Temperature-controlled fan with dust filter
Temperature-controlled fan with dust filter

Power supply Input voltage 10 V ... 60 V DC normal operating range

6 V ... 10 V DC undervoltage crank condition, time-limited (> 10 s at 6 V DC, measured

at input connector)
Load dump protection2) 60 V ... 70 V DC

Fully operational, not time-limited

Meets transient test case of 48 V vehicle onboard power supply system

70 V ... 100 V DC2)

Delayed shutdown depending on input overvoltage level and load
Reverse polarity protection up to -100 V DC2)
n
Max. input current 25 A at ≥ 10 V input voltage
40 A at ≥ 10 V input voltage

Software
Input protection Adaptive overcurrent/short-circuit protection

Start-up current Max. 6 A

Soft start

230 ms at 12 V DC start-up time

Quiescent current < 1 mA with remote off at 12 V

< 3 mA with remote off at 48 V

Max. output currents3) 40 A, +5 V

10 A, +12 V

3 A, -12 V

Max. output power 300 W

Hardware
Efficiency 85%
within input voltage operation range
Approx. 90
% at 48 V input voltage
Input/output isolation2) 100 V

Power input connector 7-pin male connector

Remote control General Overvoltage-protected remote on/off input. Overvoltage protection of the remote pin is also 100 V.

Input resistance at remote input 44 kΩ tied to GND
Remote on voltage >4V

Remote off voltage <1V

Power input connector 7-pin male connector

Max. 20 µH differential mode inductance for the supply cabling

Engineering
Status LEDs 1 multi-color LED on the bracket of the power supply board

3 multi-color LEDs on the component side of the power supply board

1)
A link board or a slot CPU board is not required for PHS-bus systems based on DS1007.
2)
The maximum voltage between any input pins or any output pins and output ground must not exceed 100 V.
3)
The sum of the output currents must not exceed the maximum output power of the supply rails.
513
2016

Specification
Parameter
AutoBox Tandem-AutoBox
Shock and vibration ISO 16750 – 3:2012/4.2.2 Mechanical test of shock resistance

resistance Test conditions:

Shock direction: six spatial directions

Acceleration: 50 g/6 ms; half-sinusoidal

Number of shocks: 10 per direction

Operating

ISO 16750-3:2012/4.1.2.4 Mechanical test of vibration resistance

n
Test IV Test conditions (-3 dB):
Test conditions (-6 dB):

Broad band noise, 1 h per axis/3 spatial axes
Broad band noise, 1 h per axis/3 spatial axes

RMS acceleration 19.2 m/s2
RMS acceleration 13.54 m/s2

Operating
Operating

Mounting positions Horizontal position (with shock mounts1) at the bottom)

Grounding Circuit ground is connected to the backplane ground, which is isolated from the vehicle battery

ground
Physical size 195 x 220 x 480 mm (7.7 x 8.6 x 18.9 in)
195 x 415 x 495 mm (7.7 x 16.3 x 19.5 in)

incl. shock mounts incl. shock mounts
Weight (without boards) Approx. 6.5 kg (14.3 lbs)
Approx. 10.8 kg (23.8 lbs)

Ambient temperature2) 0 ... 55 °C (32 ... 131 °F)
0 ... 55 °C (32 ... 131 °F)

1)
Shock mounts must be regularly inspected for visible signs of wear or damage and have to be replaced if necessary.
2)
ambient temperature applies.
514
2016

Introduction
Order Information
Order Number
Product Only AutoBox

Ethernet
(without host PCMCIA Link PCI Bus Link PCI Express Link ExpressCard Link
Interface
interface)
AutoBox ABX_BOX_ONLY
n ABX_N1
n ABX/814/815
n ABX/814/817/Opto
n ABX/814/819/Opto
n ABX/814/821
n
(NetKit)
Application Fields
Tandem TABX_BOX_ONLY n TABX_N1
n TABX/814/815
n TABX/814/817/Opto
n TABX/814/819/Opto
n TABX/814/821
n
AutoBox (NetKit)
Software
Hardware
Engineering
515
2016

Accessories / Link Boards
Link Boards
Connecting a host PC with dSPACE systems
Highlights
Connection via different link types

(ISA, PCI, PCI Express, PCMCIA, ExpressCard or Ethernet)
Partitioning the peripheral high-speed (PHS) bus

Several Connection Options

There are several options for connecting an Expansion Box There are Link Boards for connecting host PCs via ISA,
or AutoBox to your host PC/notebook: The physical con- PCI, PCI express, PCMCIA, ExpressCard or Ethernet with
nection is established via a high-speed serial or optical link. 100 megabit/s technology1).
Host PC AutoBox/
Expansion Box
Ethernet Ethernet Slot CPU

Interface
High speed serial link

PCMCIA DS815 DS814
Optical connection
PCI bus DS817 DS814
Optical connection
PCI Express DS819 DS814
High speed serial link

ExpressCard DS821 DS814
516 1)
This is the capability of the hardware components and circuits of our products. Depending on the software, the achievable
2016 performance figures can deviate significantly from this hardware specification.

Accessories / Link Boards
Introduction
Partitioning the PHS Bus with the DS802 PHS Link Board
Modular I/O
With the DS802 PHS Link Board, you can spatially partition Board is for adding and removing a simulator’s slave systems
the PHS bus by arranging the I/O boards in several expansion in response to changing tasks. Slave systems can be replaced
boxes. The box which contains the processor board is the within one simulator or exchanged between simulators. This
Application Fields
master box. Boxes which contain only I/O boards are setup is ideal for all applications that do not need processing
slave boxes. One DS802 must be installed in the master box power in every expansion box and ensures optimal utilization
and one in every slave box. The DS802 boards provide the of your simulator resources. Master-slave systems can of
necessary link between the boxes via fiberoptic cable (up course be combined with multiprocessor systems.
to 100 m). A typical use scenario for the DS802 PHS Link
Slave Box
I/O
PHS
Software
Optical DS802
interconnection
I/O
Master Box
DS802
Processor PHS Slave Box
Board
With the DS802 PHS Link Board, you I/O DS802 PHS I/O
can partition the PHS bus by arranging

the I/O boards in several expansion Slave Box
boxes up to distances of 100 m apart. Gigalink

DS802 PHS I/O
Hardware
Only the master box contains a processor
board, ensuring optimal utilization of (Additional slave boxes)
your simulator resources.
Engineering
517
2016

Accessories / DS830 MultiLink Panel
DS830 MultiLink Panel

Connection of several dSPACE systems to one host PC
Highlights
Three variants: For up to 4, 8, and 16 connections

Support of ISA, PCMCIA, and PCI host connection

Application Areas Only One Slot Needed

Flexibility is crucial when it comes to extending the To connect the DS830 MultiLink Panel to your host PC, you
topology of your dSPACE system. With the DS830 MultiLink need only one PCI express, ExpressCard, PCMCIA or PCI slot.
Panel, you have the advanced option of linking up to This link features a transfer rate of 100 Mbit/s. Depending
16 dSPACE systems to only one host PC. The linked systems on your cable length requirements for the system to be
might be expansion boxes, AutoBoxes or MicroAuto- linked, you can establish a connection via a crossed patch
Boxes1). Your benefit: All parts of the dSPACE system are cable or fiber-optic cable. To connect the DS830 to the host
under the supervision of only one host PC. PC as well as to the dSPACE boxes, you can use any combi-
nation 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 MicroAuto-
Box1) via a patch cable.
DS830 MultiLink Panel
1) 1)
...
518
2016 1)
Does not apply to the MicroAutoBox II. The MicroAutoBox II offers an Ethernet host interface.

Accessories / DS830 MultiLink Panel
Introduction
Technical Details
Specification
Parameter
DS830/4 DS830/8 DS830/16
Physical connection Host PC connection: High-speed up-link interface (100 Mbit/s)

Host PC connection requires only one dSPACE link board (p. 516)

Expansion hardware connection: High-speed down-link interface (100 Mbit/s)

Link medium: Fiber-optic cable (multi mode 50/125 μm) or crossed patch cable (twisted pair CAT5 STP)

Application Fields
Connectable boxes Up to 4 expansion boxes
Up to 8 expansion boxes Up to 16 expansion boxes

and/or MicroAutoBoxes and/or MicroAutoBoxes and/or MicroAutoBoxes
Protocol High-speed serial link (proprietary)

Max. transfer rate 100 Mbit/s1)

Status LEDs Various LEDs displaying the current status of each connection and the power supply

Physical characteristics Enclosure Aluminum box

Physical size 201.6 x 56.0 x 108.6 mm
288.0 x 56.0 x 108.6 mm
460.8 x 56.0 x 108.6 mm

(7.9 x 2.2 x 4.3 in) (11.3 x 2.2 x 4.3 in) (18.1 x 2.2 x 4.3 in)
Approx. weight 0.75 kg (1.65 lb.)
n 1.10 kg (2.43 lb.)
n 1.70 kg (3.75 lb.)
n

Active cooling (fan)

Power consumption 16 W 24 W 40 W
Software

Power supply +6 V ... +58 V DC

Power supply via mains socket or a car battery (power supply cables are part of the DS830

hardware package)
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.
Order Information
Hardware
DS830/4 MultiLink Panel DS830-4



Relevant Hardware
Engineering
Optional Expansion Boxes
See p. 508
Link Boards
See p. 516
AutoBoxes
See p. 512
519
2016

Simulator Hardware / dSPACE Simulator MidSize
dSPACE Simulator MidSize

Standardized, offtheshelf HIL simulator based on DS2202 or DS2211 HIL I/O Board
Highlights
For ECU function and integration tests

Ideally tailored for testing powertrain,

vehicle dynamics and body ECUs
Signal conditioning, load simulation and

electrical failure simulation
Open and scalable

Open Hardware Concept Typical Fields of Application

dSPACE Simulator Mid-Size is a ready-to-use, standard Engine, transmission, vehicle dynamics and body
hardware-in-the-loop (HIL) simulator for testing automo- electronics HIL
tive ECUs systematically and automatically. Open-loop or closed-loop environment
The simulation model runs on the processor hardware Realistic unit tests
(single-processor or multiprocessor systems). dSPACE Simu- Function integration tests, release tests, and ECU
lator Mid-Size generates and measures I/O signals via the diagnostics tests
integrated dSPACE I/O boards. The function range is comple- Automated testing
mented by load and failure simulation. Real-time simulation
Electric drives applications (combined with Electric Motor
HIL Solution (p. 488) or DS5203 FPGA Board (p. 462))
Hardware Details Connection to Host PC

The hardware of dSPACE Simulator Mid-Size is mounted in All dSPACE software for experiment setup and control or
a 19” desktop rack (standard height: 6 -12 U). test automation runs on your PC or notebook. The dSPACE
The DS1005 PPC Board and the DS1006 Processor Board can Simulator hardware is connected to your PC via link boards
be used as processor boards. The DS2202 or DS2211 HIL (p. 516).
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 measure-
ment can be added on request.
520
2016

Simulator Hardware / dSPACE Simulator Mid-Size
Introduction
Hardware Summary1)
Hardware Description
Form factor 19” desktop rack

Processor hardware DS1005 PPC Board or


I/O hardware DS2202 HIL I/O Board or


Additional I/O optional
Application Fields

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 Three 90-pin connectors for each load/FIU unit

Additional connectors for additional I/O optional

Break-out box 
Software
OBDII diagnostic connector / Sub-D connector with optional CARB adapter

connection to diagnostic tools CAN connector

Truck-application-capable (24 V/36 V) 
48 V-capable 
Power supply (remote-controlled) One or two power supplies for simulating 1-or 2-voltage systems

 included
 optional
Examples of Rack Variants
Hardware
dSPACE Simulator Mid-Size Single Mid-Size (6 HU) Double Mid-Size (12 HU)
DS1005 PPC Board or  
DS2202 HIL I/O Board or  (1 x)  (2 x)
Failure insertion units for actuator signals  
Load cards  
Power supply  
Second power supply – 
Engineering
Free ISA slots for expansion 1 (PX5 version, only for DS1005 PPC Board)
2 (PX10 version), 12 (PX20 version)

Height units 6
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.
521
2016

Hardware Components
Signal Conditioning Load Capabilities
On-board for DS2202/DS2211 HIL I/O Board signals Five load boards (per load/FIU unit), 10 single-ended
Spare slots for additional signal conditioning (e.g., loads or 5 double-ended loads each
current measurement for direct injection applications, Cascading of loads/FIU units with additional DS2211/
lambda probe simulation or signal conditioning for DS2202 boards
additional I/O boards) Extendable by electrically equivalent loads or low-power
resistor loads (2 W maximum continuous power per load)
Front connector for measurement or connection of real
loads
6 A maximum load current per pin (real loads)
LED indicators displaying current load states (display
mode selectable)
Rack for Load and FIU simulation with
external connectors for real loads
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 Connectors

Simulation of car battery Three 90-pin connectors for the ECU
Programmable switched-mode power supply One Sub-D CARB connector (SAE J1962) for diagnostic
Remote-controlled tools (an adapter to the standard CARB connector
Up to two power supply units for 2-voltage systems is optionally available)
VBat1: 0 ... 30 V output voltage range One CAN connector for access to the CAN bus
VBat2: 0 ... 60 V output voltage range Jacks for battery voltage (for power supplies 1 and 2)
48 V and truck-capable using VBat2 and ground
Three switched battery rails for each battery voltage, External load connectors
e.g., main relay, ECU-controlled high rail
16 A maximum current for each rail of first battery
voltage
6 A maximum current for each rail of second battery
voltage
522
2016

Introduction
Failure Insertion Units
A standard dSPACE Simulator Mid-Size supports electrical Simulation of short circuits: from ECU pins to ground

failure simulation on all ECU output pins connected to the or battery voltages
HIL I/O Board. A hardware extension allows electrical failures Simulation of cross-wired short circuits between ECU

to be simulated on ECU inputs as well. The host PC controls pins via common fail planes
both types of failure simulation via an RS232 interface. Simultaneous activation of multiple failures (latch mode)

Application Fields
ECU outputs (per load/FIU unit1)): DS791 failure insertion dSPACE Simulator Mid-Size is also available without FIU

units (FIUs) cards on request
ECU inputs: optional DS793/DS794 failure insertion units
Remote-controlled with ControlDesk® Failure Simulation For more information on High-Current Failure Simulation,
and automated with AutomationDesk please see p. 532.
Broken wire simulation (open circuit)
Failure Simulation Overview
Software
dSPACE Simulator Mid-Size Actuator-FIU Sensor-FIU (Optional)
FIU cards DS791
DS793/DS794

Number of cards per load/FIU unit 5
Up to 2

Number of channels per card 10
Up to 81

Switch type Relay
CMOS switch

Max. continuous current 6A
0.5 A

Possible failure types Cable break  
Short circuit to ground  
Short circuit to battery  
Hardware
voltage VBAT1 or VBAT2
Short circuit to another ECU  
pin via common plane
Simulation of loose contact – 
or switch bouncing
 included
– not available
Engineering
Other Hardware Components
Break-out box (optional)
Expandability
Two or more HIL I/O Boards2) Customer-specific modifications/extensions possible,

Integration of additional dSPACE I/O board possible for example larger 19" rack with break-out boxes,
Signal conditioning for additional I/O boards ECU subracks, real load drawers, etc.
Custom signal conditioning 1- or 2-voltage systems

Connection of real loads, dummy resistive loads or
electrical equivalent loads
The number of load/FIU units depends on the number of HIL I/O Boards.
1)
Requires larger 19" rack.

2) 523
2016

Simulator Hardware / dSPACE Simulator FullSize
dSPACE Simulator FullSize

Modular simulator concept, with offtheshelf
components according to your needs
Highlights
HIL systems tailored to your needs

No limit regarding application range

For testing complex single ECUs to large ECU

networks in any kind of application field
Flexible and open hardware concept

Freely expandable by any dSPACE I/O board

High current applications (hybrid drives)

Hardware Details Typical Fields of Application

dSPACE Simulator Full-Size is mounted in a 19” cabinet Engine, powertrain, chassis, and body
whose height depends on your requirements. The dSPACE Comprehensive closed-loop tests on ECUs, release/
processor boards and I/O boards are mounted in a stan- acceptance tests
dard PX20 Expansion Box (p. 508). The PX20 Expansion Networked ECUs
Box provides 20 slots for dSPACE boards. An additional Special requirements, e.g., with high system flexibility,
Expansion Box can be integrated on request. Several PX20 or high current applications
Expansion Boxes can be integrated in a multirack system, Truck applications
so you never face restrictions on expandability. Racing applications (Formula One, rally)
Electric motor simulation for hybrid or electric powertrains
and electric steering systems
Battery management systems
Mechanical test benches
Open Hardware Concept Connection to Host PC

The simulation model runs on the processor hardware All dSPACE software for setting up and controlling experi-
(single-processor or multiprocessor systems). dSPACE Simula- ments or test automation runs on your host PC or notebook.
tor generates and measures I/O signals via the integrated The dSPACE Simulator hardware is connected to your PC
dSPACE I/O boards. The signal conditioning, loads, failure via Link Boards (p. 516).
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.
524
2016

Simulator Hardware / dSPACE Simulator FullSize
Introduction
Hardware Summary1)
Hardware Description
Form factor 19” cabinet, 17 ... 42 U

Processor hardware DS1005 PPC Board or

DS1006 Processor Board or


I/O hardware Any number and type of dSPACE I/O boards

Application Fields
Signal conditioning 
Substitute loads 
Realload connector 
Failure insertion unit 
Integration of simulator extensions (p. 529) 
Integration of thirdparty hardware, e.g., load panels 
ECU connectors One or more 90pin connectors for each ECU (standardized)

Additional connectors optional

Breakout box 
OBDII diagnostic connector / connection to diagnostic tools Standard 16pin CARB connector
Diagnostic connectors (CAN, Kline)
Software
Others on request
Truck applicationscapable (24 V/36 V) 
48 Vcapable 
Power supply (remote controlled) One or two power supplies for simulating 1 or 2voltage systems

 included
 optional
Hardware
Engineering
1)
525
2016

Simulator Hardware / dSPACE Simulator Full-Size
Hardware Components
RSIM module
Current measurement boards FIU 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 Signal Conditioning

Single-processor or multiprocessor systems
Signal conditioning for all dSPACE I/O boards
Freely expandable by any dSPACE I/O board (Modular
Supports almost any signal type: e.g., digital in,
Hardware, p. 372), according to your requirements digital out, analog in, analog out, relay simulation, cur-
PX20 Expansion Box for modular hardware (processor
rent sink/source, LVDT simulation, resistance simulation
and I/O boards) and linear lambda probe simulation
Modular signal conditioning concept (customer-specific
Further modules on request
configuration)
Expandable, e.g., with hardware for failure insertion and

load simulation (customer-specific configuration)
526
2016

Introduction
Expandability Power Supply
Maximum flexibility through modular concept Simulation of car battery
Minimum hardware modification when requirements Programmable switched-mode power supply
change Remote-controlled
Supersets with spare signals, allowing tests on several 48 V and truck-capable: 0 ... 60 V voltage range
ECU variants, even after ECU pinout changes
Application Fields
All signals accessible on terminal strips for additional
measurement tasks and for flexible response to chang-
ing specifications
Clear and transparent system architecture
Multirack systems possible
Other Hardware Components Load Capabilities
Software
Break-out box (optional, integrated in cabinet or external) Modular load concept (customer-specific configuration)
Optional inclusion of third-party hardware; e.g., load Support of single-ended and double-ended loads
panels, signal routing units, GPIB instruments Resistive loads or other kinds of equivalent loads
Power switch modules (p. 530) Connection of electrically equivalent loads or low-
power resistive loads
Connection of real loads, can optionally be integrated
in the cabinet
Integration of customers’ load panels
Hardware
High-speed electronic loads (e.g. for emulation of
electric motor)
Failure Insertion Units

Modular FIU concept (customer-specific configuration) Simulation of cross-wired short circuits between ECU pins

Failure insertion unit (FIU) for ECU inputs and outputs Simultaneous activation of multiple failures (latch mode)

Engineering
Remote-controlled with ControlDesk Failure Simulation
(or optionally with AutomationDesk) For more information on High-Current Failure Simulation
Broken wire simulation (open circuit) please see p. 532
Simulation of shorts: shorts from ECU pins to ground,
battery voltage, or switched rail
527
2016

Failure Simulation
Failure Simulation Variant 1 Failure Simulation Variant 2
The standard variant for failure simulation on dSPACE Simu- The second failure simulation variant uses a central relay
lator Full-Size supports failure simulation on all ECU input switching matrix (DS293) for failure simulation on ECU
and output pins. All digital and analog I/O boards from inputs and outputs. 5 different system potentials (for exam-
dSPACE are supported by failure simulation. The relay boards ple, Terminal 30, Terminal 31, Terminal 15) can be switched
(DS291) for failure simulation can be used on their own in on three different rails via load modules (DS282). Further
for failure simulation on sensor signals (ECU inputs) or in devices that can be connected include various measure-
conjunction with load boards (DS281) on actuator signals ment devices (Meas0-4), an electronic source (Source), and
(ECU outputs). Failure relays are controlled via a serial RS232. Rsim modules for transition impedance. Failure simulation
is controlled via a CAN interface.
Failure Simulation Summary
dSPACE Simulator Full-Size Failure Simulation Variant 1 Failure Simulation Variant 2

FIU cards DS291
DS282

Number of cards per simulator Configurable
Configurable

Number of channels per card 10
10

Switch type Relay
Relay

Central modules – 1 x DS293

Simulation of transition impedance – 1 x DS289 Rsim Module (simulates a

resistance in the range 1 Ω ...131 kΩ
in steps of 1 Ω)
Max. continuous current 8A
8A

Possible failure types Cable break  
Short circuit to ground  
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
528
2016

Simulator Hardware / Simulator Extensions
Simulator Extensions1)
Introduction
Examples of simulator extensions
Highlights
Application Fields
Power switch

CAN gateway

Bus FIU

Electric drives

Custom adaptation

Break-out boxes

Software
Tailor-made solutions
Further simulator-specific hardware can be integrated into The list shown below is typical of many application areas,
your dSPACE Simulator in addition to the modular hardware and you can also add or remove as many components as
listed in this catalog. This simulator-specific hardware can you like.
include real system components, as well as measurement Interfaces to diagnostic and calibration hardware to
and diagnostic tools. The components and tools can be built supplement the default interfaces
and integrated by dSPACE, or you can do it yourself. Real system components
dSPACE Simulator Full-Size can be equipped with simulator- Break-out boxes
Hardware
specific hardware for optimum tailoring to your specific Failure insertion units
needs. dSPACE Simulator Mid-Size can also be similarly Programmable power supplies
equipped to a certain extent. Power switch module
Signal conditioning
Simulation of linear lambda probes
CAN gateway
Electronic loads
Battery cell voltage emulation
Others
Engineering
1)
529
2016

Examples of Simulator Extensions

Customized Interfaces to Diagnostic and Real System Components
Calibration Hardware In some cases, the real system components (such as injec-
Many companies already have their own diagnostic and tion valves, hydraulic components, and sensors) have to
calibration hardware to perform tasks such as reading out be integrated into dSPACE Simulator. This is necessary, for
internal ECU variables from the failure memory. If you do example, if these components come from different suppliers
not intend to run this functionality on dSPACE Simulator, the for one and the same ECU and have to be checked together
hardware is connected to dSPACE Simulator via appropriate with the ECU within the simulated environment. Moreover,
interfaces, which might in some cases need a little engineer- not every vehicle component can be simulated precisely
ing. You can connect any kind of measuring device, digital enough with a justifiable amount of time and money, and
scope, and diagnostic device you like with special protocols some ECUs require real loads at their outputs in order to
such as GPIB or RS232. function at all.
Power Switch Module

ECUs consume power even when the vehicle is parked. power switch module can therefore handle two power sup-
Many modern ECUs have a sleep mode to avoid draining the ply lines to simulate different vehicle electrical systems within
vehicle’s electrical system unnecessarily. Some ECUs therefore dSPACE Simulator. Even the sequence when a vehicle is
contain a CAN transceiver capable of wake-up/sleep mode, starting up can be simulated.
which allows the ECU to run only if it is needed and switches A measurement unit allows the precise current measurement
it off otherwise. Power switch modules provide the possibil- of each ECU supply line in different current ranges, even
ity to connect each ECU to the standard battery terminals in the microampere range. For example, current consump-
(e. g. T30, T15, T50) and to measure the current consumption during ECU sleep mode can be compared with normal
tion of each ECU separately in different current ranges from operation mode consumption. The module is controlled by
µA up to 50 A. Moreover, systems with networked ECUs software via a CAN interface.
often require different power supply voltage levels. Each
Programmable Power Supplies Break-Out Boxes

The programmable power supply unit supplies the compo- An optional break-out box makes all ECU pins directly
nents to be tested and allows the simulation of real volt- accessible. This simplifies the measurement and input of
ages such as a vehicle’s battery voltage during start-up. signals. The break-out boxes can be integrated into dSPACE
The power supply unit is remote-controlled from within Simulator, or take the form of external desktop boxes.
the real-time model. Third-party break-out boxes can also be included.
Various power supplies are available for different applica-
tions, for example:
0 ... 20 V (e.g., passenger cars)
0 ... 60 V
530
2016

Introduction
CAN Gateway
In large-scale CAN networks, the testing of bus communica- Simulator. Signal manipulation by software allows you
tion plays a key role. Engineers need to test the behavior to manipulate any CAN messages from any ECU, with a
of ECUs and distributed functions when an expected CAN predefined effect on the other ECUs in the CAN network.
message fails to arrive or contains unexpected signals. The CAN software (RTI CAN MultiMessage Blockset, p. 74)
To simulate errors, a CAN gateway module is inserted into offers a huge range of typical error situations right up to
Application Fields
the CAN network (see graphic). Each ECU can be connected message or individual signal level.
individually to one of the two CAN controllers in the dSPACE
CAN gateway software
Signal manipulation
Signal
manipulation
Software
Rx Tx Rx Tx
CAN CAN
controller 1 controller 2
Hardware
ECU 1 ECU 2 ECU n
CAN gateway hardware

CAN gateway for simulating errors in large ECU networks.
Simulation of Linear Lambda Probes
Engineering
LSU (Lambda-Sonde universal, universal lambda probe) is a The LSU module allows Nernst cell voltage to be generated
signal conditioning module for dSPACE Simulator Full-Size on four independent channels, according to pump current
and Mid-Size that simulates the behavior of linear lambda and Nernst cell inner resistance. The module functions as a
probes. These probes measure the air-fuel ratio in a car’s linear probe or as a jump probe. Parameters such as maxi-
exhaust system. The engine ECU reacts by varying the injec- mum/minimum Nernst cell voltage can be adjusted.
tion time so that the catalytic converter can operate at an
optimal performance rate.
531
2016

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 Supports 4 bus channels in parallel

Usable for dSPACE Simulator Mid-Size and Full-Size as well as

HIL systems based on expansion boxes
Suitable for differential bus sytems (FlexRay, CAN, etc.)

Relay-based

Software n Uses a specialized ControlDesk® Next Generation failure pattern (p. 137)
Failure insertion options Short circuit to ground and to any user-defined potential (typically UBAT)

Open circuit

Varying termination resistance

Switching cross short-circuits

High-Current Failure Simulation

Our high-current failure simulation unit on dSPACE Simula- The FIU is controlled from ControlDesk® Next Generation via
tor supports failure simulation on ECU inputs and outputs. a serial RS232 or CAN and can be combined with dSPACE
One FIU controller card (DS5355) supports up to 19 signal Simulator Mid-Size and Full-Size.
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.
High-Current FIU for dSPACE Simulator

FIU cards DS5355/DS5390

Number of cards per simulator Configurable

Number of channels per card Up to 19

Switch type Relay

Max. continuous current 50 A

Possible failure types Cable break 
Short circuit to ground 
Short circuit to battery voltage 
Short circuit to another ECU pin via common fail plane 
 included
532
2016

Introduction
External Failure Insertion Unit
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
Application Fields
actuator failure simulation and also for sensor failure simula-
tion. The external FIU can optionally be equipped with an These failure patterns can be activated and processed with
integrated Break-Out-Box (BOB). AutomationDesk (p. 172). You simply integrate the needed
For designing and controlling the failure patterns, the Fail- failure pattern into you test sequence. During the execu-
ure Simulation Model of ControlDesk® Next Generation tion of the test sequence, the failure pattern is activated
is used (p. 137). on the ECU.
Technical Details
Software
No. of cards per rack 9

No. of channels per card 10

Rack variants 90 channels

(each with BreakOutBox (BOB) optional) 180 channels

270 channels

Switch type Relay

Control RS232 interface via Failure Simulation Module of ControlDesk Next Generation

Connection interface Front: female Hypertac connector for connection to ECU

Hardware
Rear:

Male hypertac connector for connection to simulator hardware (cable length max 1.5 m)

Plug connector for VBat and GND

Max. continuous current 8 A per channel

Possible failure types Cable break

Short circuit to ground

Short circuit to battery voltage

Short circuit to another ECU pin via common fail plane

Max. failure patterns 20 at the same time

Physical characteristics (depend on the variant) Form factor: 39 U

Engineering
External power supply 12 V / 100 W


External Failure Simulation with BreakOut Box EXTFIU90PINS_B

(90, 180 or 270 channels) EXTFIU180PINS_B

EXTFIU270PINS_B

External Failure Simulation without BreakOut Box EXTFIU90PINS

(90, 180 or 270 channels) EXTFIU180PINS

EXTFIU270PINS

533
2016

Electronic Load Emulation

Combination with dSPACE Simulator and SCALEXIO
dSPACE offers two variants of electronic load modules for Electronic load emulation covering a voltage range up to
different voltage ranges. The DS5380 (up to 30 V) and the 800V is possible on request.
DS5381 (up to 60 V) can be used for HIL simulation with
dSPACE Simulator (p. 520) or a SCALEXIO system (p. 318).
DS5380 Electronic Load Module (Voltage Range: 30 V)

Electronic Load Module
For the hardware-in-the-loop emulation of electrical ma- combined with the DS5203 FPGA Board (p. 462) used in a
chines, such as motors or generators, dSPACE offers the dSPACE Simulator or the DS2655 FPGA Base Board (p. 335)
Electronic Load Module. The module is optimized for high- used with SCALEXIO. In combination with the XSG Electric
speed operation as required for emulating electric motors Components Library (p. 271), they provide the fast reaction
such as those in electric steering systems. It can work as both times required for controlling electrical machines. In both
a current sink and a current source to provide bidirectional cases the FPGA computes parts of the simulation model for
current flow, i.e., it generates or consumes real current on the electrical machine, e.g., from the XSG Electric Compo-
ECU motor outputs. The Electronic Load Module can be nents Library, and operates the Electronic Load Module.
Key Features Technical Details

Current sink and source capability The Electronic Load Module DS5380 contains two indepen-
High-speed current regulation ideal for loading PWM dent load channels, which can control a unipolar current
power stages through its output stage. It provides high-speed current
Simulation of current ripple regulation of less than 5 µs. Each module can provide con-
Different types of electric motors tinuous current of 30 A and 300 W, and a maximum voltage
Remote-controlled by standard 10 V analog signals 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 mo-
tor simulation.
For further information, please refer to

DS5203 FPGA Board (p. 462)
DS2655 FPGA Board (p. 335)
XSG Electric Components Library (p. 271)
534
2016

Introduction
DS5381 Electronic Load Module (Voltage Range: up to 60 V)
This dSPACE Electronic Load Module emulates motor and The module is perfect for emulating three-phase electric
generator currents at voltages of up to 60 V for the hard- motor units. Energy recuperation is also included to boost
ware-in-the-loop (HIL) simulation of electric motors. Highly the energy efficiency of the overall system. Typical test ap-
dynamic switching between the current and voltage control plication areas are electrically supported steering, starter and
modes enables emulation of floating brushless DC (BLDC) generator systems, and mild hybrid drives. Several loads can
motor phases without additional booster components. be operated in parallel to achieve higher electric currents.
Application Fields
With a voltage range up to 60 V, the module is also ideal
for use with higher on-board vehicle voltages of 48 V.
Power Recovery Operation Modes

The Electronic Load Module DS5381 uses the same supply The Electric Load Module can be operated in three diffe
voltage as the device under test (ECU). It is equipped with rent modes:
bidirectional working voltage regulators so that the current Current control mode (typically used for motor
Software
that is sunk on one pin can be sourced to another pin. This applications, not BLDC motors)
means that the effective power which is simulated on the Voltage control mode (general-purpose applications)
“Load” pins can be much higher than the power consump- Mixed current and voltage control mode (BLDC motor
tion of the electronic load. applications)
The mode parameter can be set from the host via protocol.
Hardware
Engineering
535
2016

DC-link+
+
ECU
FPGA + MOSFET driver
Microcontroller +
MOSFET driver
E-load
Battery
type-B
-
DC-link-
dSPACE host system ECU diagnostics
DS5831 Electronic Load Module Data Sheet

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
536
2016

Introduction
Electronic Load Emulation (Voltage Range: up to 800 V)
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 and safer to operate. Tests can be run at a very early stage,
power stages, testing at signal level is not enough. Testing even if the real drive motor is not yet available. Moreover,
Application Fields
at electrical power level is essential. One way is to operate it is also possible to simulate different motor types. Unlike
a real drive motor on a test bench. Another is to simulate mechanical test benches, these simulators have no restric-
the electric motor at the electrical power level. This involves tions on dynamic processes.
simulating the electrical behavior of a real motor by map- The electronic load emulator covers voltages of more than
ping the real terminal voltages and currents and feeding 800 V and power outputs of up to 100 kW. Thus, it is suit-
them to the ECU. Compared with a mechanical drive test able for the HIL simulation of current and future electrical
bench, a purely electrical test bench of this kind is easier drive systems.
Software
How the Electronic Load Emulator Works Applications
The electronic load emulator emulates the variable, active The concept of the electronic load emulator can be used
parts of the voltages uEMK induced in the motor coils, while for simulating all types of motor. The physical properties of
the inductive behavior of the motor coils is represented each motor, such as motor inductivity, torque generation
by equivalent substitute inductivities LMotor. The induced and power consumption, are represented very realistically.
voltages uEMK are calculated in real time by an electric motor For variable inductivities (such as in an interior permanent
model and implemented by the electronic load simulator. magnet or IPM motor, or with saturation effects), mean values
have to be used in the load emulator due to the constant
Hardware
substitute inductivities. Nevertheless, correct representa-
How the Electronic Load Emulator is Implemented tion of the torque and
The load emulator uses inverters from the ServoOne series the power is possible.
by LTi. The electric motor model for computing the induced Any desired hybrid
voltages is implemented on a dSPACE real-time system by and electrical vehicle
means of Simulink®. configuration can be
The model components that can be simulated include simulated by using
the drivetrain. Various sensor and actuator simulations different electric motor
are added to the real-time system for this, according to models in conjunction
Engineering
project-specific requirements. A hybrid ECU requires at with variable drivetrain
least one appropriate simulation of an engine speed sensor models (for example,
(such as a resolver). Automotive Simulation
Models from dSPACE).
The concept
is also suit-
able for vari-
ous industrial
HIL applica-
tions.
537
2016

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 voltage is galvanically isolated, allowing the modules
The number of these controllable buffer amplifier boards to be connected in series up to a voltage of 800 V. A refer-
is configured to match the battery type. The boards supply ence value step is corrected completely in less than 500 µs.
a continuously adjustable voltage, in the range 0 to 6 V. Fast data transmission means that a change to all the cell's
This relatively wide range means that damaged cells can be voltages takes less than 1 ms.
emulated. For example, a voltage higher than the nominal The maximum current that can be supplied or sunk is 1 A,
voltage simulates a cell's increased internal resistance dur- which enables testing of passive and active cell balancing
ing charging. strategies. For special requirements, up to four modules can
The voltage is output with a precision of ±1.5 mV across be connected in parallel to quadruple the maximum current.
the entire working temperature range, and with a precision dSPACE's Automotive Simulation Models are ideal battery
of better than ±1 mV within a reduced temperature range. simulation models, see p. 258.
Compact Systems
For battery management solutions dSPACE offers compact To meet safety regulations, a safety compartment prevents
systems with one 19'' Full-Size Simulator rack including all accidental contact with the ECU, preventing harm due to
required components. The systems contains: high voltages. With everything combined in one system,
Up to 200 cells for battery voltage emulation users do not have to think about the ECU connection, but
The real-time computing system can concentrate on their project.
A safety compartment for the ECU
538
2016

Introduction
Technical Data
EV1077 Battery Cell Voltage Emulation Board1)

Hardware structure 32 cells per 19" 3-U module


Resolution 120 µV

Application Fields
Precision (across working temperature range) ±1.5 mV

Working temperature (environment) 10 ... 50 °C

Maximum current (sink/source) 1 A, switchable in parallel

Isolation 60 V between the cells of a module

1000 V between cell and environment

Connection Ethernet, e.g., as interface to SCALEXIO

Maximum update rate for all cells 1 kHz

Fault simulation Broken wire between ECU and battery

Short circuits between cells

1)
Technical modifications possible.
Software
Hardware
Engineering
539
2016

MicroLabBox Hardware / MicroLabBox
MicroLabBox
Compact prototyping unit for the laboratory
Highlights
Compact all-in-one development system

for laboratory purposes
Dual-core real-time processor at 2 GHz


More than 100 channels of high-performance I/O

Dedicated electric motor control features

Ethernet and CAN bus interfaces

Easy I/O access via integrated connector panel


With MicroLabBox, dSPACE introduces a fully new system High computation power combined with very low I/O la-
category: a compact development system for the laboratory tencies provide great real-time performance. A program-
that combines compact size and cost-effectiveness with mable FPGA gives you a high degree of flexibility and lets
high performance and versatility. MicroLabBox lets you set you run even extremely fast control loops, as required in
up your control, test or measurement applications quickly applications such as electric motor control or active noise
and easily, and helps you turn your new control concepts and vibration cancellation.
into reality. More than 100 I/O channels of different types MicroLabBox is supported by a comprehensive dSPACE
make MicroLabBox a versatile system that can be used software package (see options on p. 543), including, e.g.,
in mechatronic research and development areas, such Real-Time Interface (RTI) for Simulink® for model-based I/O
as robotics, medical engineering, electric drives control, integration and the experiment software ControlDesk® Next
renewable energy, vehicle engineering, or aerospace. Generation, which provides access to the real-time applica-
tion during run time by means of graphical instruments.
Two Connector Panel Variants

MicroLabBox is available in two connector panel variants
(see p. 542), 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 in-
formation is shown on the units themselves and is referred
to in the I/O blockset of RTI.
540
2016

Introduction
Technical Details
MicroLabBox Front Panel Variant Top Panel Variant

Processor Real-time Freescale QorlQ P5020, dual-core, 2 GHz

processor 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 communi Freescale QorlQ P1011 800 MHz for communication with host PC

cation co-processor
Application Fields
Memory 1 GB DRAM

128 MB flash memory

Boot time Autonomous booting of applications from flash (depending on application size), ~5 s for a 5 MB application

Inter Host interface Integrated Gigabit Ethernet host interface

faces Ethernet real- Integrated low-latency Gigabit Ethernet I/O interface

time I/O interface
USB interface USB
2.0 interface for data logging ("flight recorder") and booting applications via USB mass storage device
(max. 32 GB supported)
CAN interface 2 CAN channels (partial networking supported)

Serial interface 2 x UART (RS232/422/485) interface

LVDS interface 1 x LVDS interface to connect with the Programmable Generic Interface PGI1

Software
Programmable FPGA1) Xilinx® Kintex®-7 XC7K325T FPGA

Analog Resolution and type 8 14-bit channels, 10 Msps, differential; functionality: free running mode

input 24
16-bit channels, 1 Msps, differential; functionality: single conversion and burst conversion mode with different
trigger and interrupt options
Input voltage range -10 ... 10 V

Analog Resolution and type 16 16-bit channels, 1 Msps, settling time: 1 µs

output Output voltage range -10 ... 10 V

Output current ± 8 mA

Digital I/O 48
bidirectional channels, 2.5/3.3/5 V (single-ended); functionality: bit I/O, PWM generation and measurement
(10 ns resolution), pulse generation and measurement (10 ns resolution), 4 x SPI Master
Hardware
12 bidirectional channels (RS422/485 type) to connect sensors with differential interfaces

Electric motor Seperate 2 x Resolver interface

control I/O interfaces
functionality Functionality 6 x Encoder sensor input

on digital I/O 2 x Hall sensor input

channels 2 x EnDat interface

2 x SSI interface2)

Synchronous multi-channel PWM

Block commutational PWM

Sensor supply 1 x 12 V, max. 3 W/250 mA (fixed)

1 x 2 ... 20 V, max. 1 W/200 mA (variable)

Engineering
Feedback elements Programmable buzzer

Programmable status LEDs

Theft protection Kensington® lock

Cooling Active cooling (temperature-controlled fan)

Physical connections 4 x Sub-D 50 I/O connectors
2 x Sub-D 50 I/O connectors

48 x BNC I/O connectors


3 x RJ45 for Ethernet (host and I/O)

USB Type A (for data logging)

2 x 2 banana connectors for sensor supply

Power supply

1)
User-programmable via RTI FPGA Programming Blockset (p. 90). Using the RTI FPGA Programming Blockset requires additional software.
2)
SSI interface support is planned for a later release.
541
2016

MicroLabBox Front Panel Variant Top Panel Variant

Physical Enclosure size Approx. 310 x 250 x 110 mm (12.2 x 9.8 x 4.3 in)
Approx. 310 x 250 x 115 mm (12.2 x 9.8 x 4.5 in)

characteristics Temperature 0 ... 50 °C (ambient temperature)


Power consumption 125 W

Panel Variants
MicroLabBox, front panel variant MicroLabBox, top panel variant
542
2016

Introduction
Order Information

MicroLabBox, front panel variant MLBX_1302F

MicroLabBox, top panel variant MLBX_1302T

Application Fields

Included Data retrieval utility for flight recorder read-out
–
Comprehensive C libraries (e.g., digital I/O support)
–
Required For Simulink
®
-based use cases: Real-Time Interface (RTI) RTI

GNU C Compiler for Power PC
MLBX_COMP

Optional ControlDesk® Next Generation
See p. 122
For multi-core applications: ControlDesk Next Generation –
CDNG_MP

Multiprocessor Module
Software
For multi-core applications: RTI-MP
RTI_MP

RTI CAN Blockset
RTICAN_BS

RTICANMM_BS

RTI_EMC_BS

RTI_USB_FR_BS

RTI_ETH_BS

RTI FPGA Programming Blockset
See p. 91
PLATFORM_API

Hardware
Included Ethernet patch cable (HSL_PATCH) for host connection
–
Power supply cable
–
Set of Sub-D plugs
–
Case for storage and transportation
–
Optional RapidPro SC Unit
See p. 577
RapidPro Power Unit
See p. 579
Engineering
543
2016

MicroLabBox
Block Diagram
+
Ethernet PC Controller U
-
Ethernet
USB 2.0
switch
PGI
Interface
RAM
256 MB
Host
communication Interrupt
co-processor Interrupt
Controller
(P1011)
controller
Flash Real-time
64 MB clock (RTC)
Timer A (32 bit)

Timer A (32
Timer bit)bit)
B (32
Local bus
Timer B (32
Timer bit)bit)
D (32
RAM
Timer D (32 bit)
2 x 512 MB
Real-time
processor
(P5020)
Flash
128 MB
DS1202
DS1302
RAM
Sensor
2 x 18 MB
supply
I/O FPGA
I/O CPLD
ADC DIG I/O Resolver
DAC UART LED Buzzer CAN
Connector panel
544
2016

Introduction
Use Cases (Examples)
Developing Control Strategies for Electric Motors
MicroLabBox is ideal for developing control functions for net synchronous motors (PMSM). The RTI blocks for electric
many different electric motors, such as asynchronous motor control (p. 547) ensure convenient and comprehensive
motors, brushless DC (BLDC) motors, and permanent mag- configuration options for the I/O interfaces.
Application Fields
Control signals
Current measurement
Software
MicroLabBox
Resolver / EnDat
Hall / Encoder /
Power signals
RapidPro Power Unit
(optional)
Hardware
RTI Blockset Motor
Rapid Control Prototyping in Robotics

Its numerous interfaces make MicroLabBox ideal for many calculates the control algorithm and sends the controller
kinds of robotics applications. In this example, MicroLabBox output with position and velocity data back to the robot.
replaces the robot's position controller and receives the Thus, you can implement and test different control algo-
Engineering
robot's incremental encoder signals for determining the rithms very quickly.
current position of the robot. Then, the real-time processor Support and Maintenance
Control Signals
MicroLabBox
545
2016

Active Noise Cancellation and Vibration Damping

Applications in active noise cancellation (ANC: e.g., for tion speaker or the point in space designated for noise
hi-fi headphones, cell phones or a passenger car cabin) cancelling. MicroLabBox's fast real-time processor and low-
and vibration damping (e.g., for reducing wear and tear or latency I/O access make it the right tool for developing
industrial plant noise) pose a particularly great challenge new algorithms for active noise reduction and vibration
for signal processing. For ANC applications, for example, reduction. MicroLabBox achieves control loops of only a
the anti-noise has to be calculated and generated before few microseconds. If the requirements are even higher, the
the original noise reaches the respective noise cancella- algorithms can always be offloaded to the integrated FPGA.
Anti-noise
Amplifier
D/A
and filter
Amplifier
A/D
and filter
MicroLabBox Microphones Source

of noise
Developing and Testing Medical Devices

Safety and reliability play a crucial role in the development external errors on the signal and makes it possible to
of medical devices. New functions must have an optimal achieve a high signal quality. During or after the devel-
design and undergo extensive testing. In many cases, cap- opment of the medical device, MicroLabBox can also be
turing and preprocessing signals is an integral part of func- used as a testing system. With it, you can reproducibly
tion development. With MicroLabBox, you can outsource simulate many different environment conditions, e.g.,
extensive and computation-intensive signal preprocessing based on test algorithms or existing measurement data.
tasks, such as filtering or signal analysis, to an integrated This increases the medical device's maturity, saves time,
FPGA. Connecting BNC cables directly to MicroLabBox reduces costs, and minimizes the risks compared to tests
for processing analog signals minimizes the influence of on a living organism.
Blood flow sensors

(atrial, ventricular)
A/D
D/A
Pulse
control
DO
Pacemaker
MicroLabBox
Heart
546
2016

Introduction
RTI Electric Motor Control Blockset
Electric motor controls play an important role in numerous flow® from MathWorks. The blockset provides access to
application fields such as automotives, robotics, medical the electric motor control I/O functionalities of MicroLab-
engineering, and many more. The RTI Electric Motor Control Box and lets you configure these easily and conveniently.
Application Fields
Blockset, an extension of Real-Time Interface (RTI), see p. Simulink-based control models can be easily connected
56, is a user-friendly software interface which provides a with the required I/O interfaces and then be tested on
link between your real-time hardware platform MicroLabBox MicroLabBox in a real environment with different sensors
and the development software MATLAB®/Simulink®/State- and actuators.
The included blocks enable you to:

 Access and configure dedicated I/O functions for multi-
channel PWM and block-commutated PWM outputs,
Hall sensor inputs, incremental encoder, resolver, EnDat
and SSI1) interfaces. This lets you measure the position
Software
of a motor's rotor, its speed, or both, and generate the
required output signals.
 Implement control strategies for electric motors with
up to 6 phases and 16 pole pairs
 Control 2 or even more independent electric motors at
the same time
 Combine 2 sensors to extrapolate the position of the
motor's rotor
Hardware
 Generate events for algorithm execution triggered by
specified motor positions
Engineering
Essential electric drive functionalities of MicroLabBox under
control with the RTI Electric Motor Control Blockset.
Order Information

RTI Electric Motor Control Blockset  RTI_EMC_BS
1)
SSI interface support is planned for a later release.
547
2016

MicroAutoBox Hardware / MicroAutoBox II
MicroAutoBox® II
Compact, standalone prototyping unit
Highlights
Comprehensive I/O incl. CAN, CAN FD, LIN, K/L-Line,

FlexRay, Ethernet, and LVDS/bypass interfaces
Robust and compact design ideal for in-vehicle use

MicroAutoBox Embedded PC (p. 555)

AC Motor Control Solution (p. 560)

Multistage watchdog mechanism (p. 554)

NEW: XSG Advanced Engine Control Library (p. 559)

NEW: DS1514 variants with Simulink®-programmable

Xilinx® Kintex®-7 FPGA (p. 553)

MicroAutoBox is a real-time system for performing fast The special strength of the MicroAutoBox hardware is its
function prototyping in fullpass and bypass scenarios. unique combination of high performance, comprehensive
It operates without user intervention, just like an ECU. automotive I/O, and an extremely compact and robust design
MicroAutoBox can be used for many different rapid (extreme shock and vibration tests according to ISO 16750-
control prototyping (RCP) applications such as: 3:2007, see p. 564) – all for a favorable price. This lets you equip
several vehicles or a whole test fleet to check the reliability
Powertrain
of your control functions. With dSPACE's combination of
Chassis control
comprehensive software and hardware support, you can also
Body control
keep overall system costs low. In addition to the standard
Advanced driver assistance systems (ADAS)
I/O, MicroAutoBox offers variants with FPGA functionality for
Electric drives control
application-specific I/O extensions and for user-programmable
X-by-wire applications
FPGA applications. Moreover, there are MicroAutoBox variants
Aerospace applications
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. 555) can be integrated into the
MicroAutoBox II.
More Features Five Standard Variants

MicroAutoBox can start up autonomously after power-up, MicroAutoBox is available in five standard variants, each
with ECU-like boot-up times. A PC or notebook can be with different interfaces and I/O functionalities. An ideal
easily connected (hot-plugged) for application download, extension for the MicroAutoBox is the RapidPro hardware
model parameterization, and data analysis via Ethernet. (p. 554) with its off-the-shelf signal conditioning and power
Application programs are stored in nonvolatile memory. stage modules. All standard variants can integrate an
MicroAutoBox contains signal conditioning for automotive additional Embedded PC (p. 555).
signal levels and an integrated flight recorder for long-term
data acquisition (incl. support of USB mass storage devices).
548
2016

Technical Details
Introduction
MicroAutoBox II 1401/1507 1401/1511 1401/1513 1401/1511/1514 1401/1513/1514

Processor IBM PPC 750GL, 900 MHz (incl. 1 MB level 2 cache)

Memory 16 MB main memory

6 MB memory exclusively for communication between MicroAutoBox and PC/notebook

16 MB nonvolatile flash memory containing code section and flight recorder data

Clock/calendar function for time-stamping flight recorder data

Application Fields
Boot time Depending on flash application size. Measurement examples: 1 MB application: 160 ms; 3 MB application: 340 ms

Inter Host interface 100/1000 Mbit/s Ethernet connection (TCP/IP). Fully compatible with standard network infrastructure. LEMO connector.

faces Optional XCP on Ethernet interface to support third-party calibration and measurement tools

Ethernet real-time 100/1000 Mbit/s Ethernet connection (UDP/IP; TCP/IP on request). RTI Ethernet (UDP) Blockset (optional) for read/write

I/O interface access. LEMO connector.
USB interface USB 2.0 interface for long-term data acquisition with USB mass storage devices. LEMO connector.

CAN interface 4 CAN channels
6 CAN channels
4 CAN channels
6 CAN channels

(partial networking (partial networking
supported) supported)
Serial interface 2 x RS232 interface
3 x RS232 interface
2 x RS232 interface
3 x RS232 interface

(based on CAN 2 x serial interface usable as K/L-Line or LIN
3 x serial interface

processor)
Software
interface usable as K/L-Line or usable as K/L-Line or usable as K/L-Line or
LIN interface LIN interface LIN interface
ECU interface 3 x dual-port
2 x dual-port memory interface

memory interface
IP module slot for 2 slots1) for FlexRay2)
– – 2 slots1) for FlexRay2) or CAN FD modules

FlexRay and CAN FD or CAN FD modules
Programmable FPGA – – – Xilinx® Kintex®-7 (XC7K325T)
Analog Resolution – 16 16-bit channels 32 16-bit channels 16 16-bit channels3) 32 16-bit channels3)

input Sampling 16 parallel channels 16 parallel channels 16 parallel channels 16 parallel channels

with 1 Msps with 1 Msps with 1 Msps with 1 Msps
– conversion rate conversion rate conversion rate conversion rate
Hardware
16 multiplexed 16 multiplexed
channels with 200 channels with 200
Ksps conversion rate Ksps conversion rate
Input voltage range – 0 ... 5 V
-10 ... 10 V 0 ... 5 V -10 ... 10 V
Analog Resolution – 4 12-bit channels
8 16-bit channels 4 12-bit channels3) 8 16-bit channels3)
output Output voltage range – 0 ... 4.5 V
-10 ... 10 V 0 ... 4.5 V -10 ... 10 V
Output current – 5 mA max.
8 mA max. 5 mA max. 8 mA max.
Digital General FPGA-based digital I/O

I/O RTI software support for bit I/O, frequency, and PWM generation/measurements

Bit I/O 40 inputs
24 inputs 40 inputs3) 24 inputs3)
Engineering
– 4) 40 outputs, 5 mA
24 outputs, 5 mA 40 outputs, 5 mA 24 outputs, 5 mA
output current output current output current3) output current3)
Input / output logic levels: 5 V or levels up to 40 V (depending on VDrive), selectable

PWM generation/ – All channels fully configurable as frequency or PWM inputs/outputs

measurement PWM frequency 0.0003 Hz ... 150 KHz, duty cycle 0 ... 100%, up to 21-bit resolution

Onboard sensors Motion sensing with 3-axis accelerometer. Pressure sensing for altitude indication.

Signal conditioning Signal conditioning for automotive signal levels, no power driver included

Overvoltage protection; overcurrent and short circuit protection

Physical connections LEMO connectors for 2 ECU interfaces, Ethernet I/O interface, USB interface, and Ethernet host interface

Ethernet host interface (100/1000 Mbit/s, TCP/IP) for notebook/PC connection (for program load, experiment

configuration, signal monitoring, and flight recorder read-out)
Integrated Ethernet switch

Additional 78-pin
ZIF connector for I/O signals, mechanically secured, Sub-D connector for power supply

Sub-D connector
1)
IP module slot. Can also be used for other IP modules such as an ARINC interface module (via dSPACE Engineering Services).
2)
i.e., 4 FlexRay channels, combination with CAN FD possible. 549
3)
Additional channels with DS1552 (p. 558). 2016
4)
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).
MicroAutoBox II 1401/1507 1401/1511 1401/1513 1401/1511/1514 1401/1513/1514

Physical Enclosure material Cast aluminum box
charac Enclosure size Approx. 200 x 225 x 50 mm Approx. 200 x 225 x 95 mm

teristics (7.9 x 8.9 x 2.0 in) (7.9 x 8.9 x 3.8 in)
Temperature Operating (case) temperature: -40 ... +85 °C (-40 ... +185 °F)

Storage temperature: -55 ... +125 °C (-67 ... +257 °F)

Power supply 6 ... 40 V input power supply, protected against overvoltage and reverse polarity

Power Max. 25 W
Max. 50 W

consumption
Order Information

MicroAutoBox II 1401/1507 MABX_II_1507



MicroAutoBox II 1401/1511/1514 MABX_II_1511/14

MicroAutoBox II 1401/1513/1514 MABX_II_1513/14


Included Data retrieval utility for flight recorder read-out
–
Comprehensive C libraries (e.g., digital I/O support)
–
Required Real-Time Interface (RTI)
RTI

Microtec PowerPC C Compiler
CCPPPC

Optional ControlDesk® Next Generation

See p. 120
RTI CAN Blockset
RTICAN_BS

RTICANMM_BS

RTILINMM_BS

FCP

RTI Bypass Blockset
RTIBYPASS_BS

RTI AUTOSAR Blockset
See p. 86
RTI Ethernet (UDP) Blockset
RTI_ETH/UDP_BS

RTI_USB_FR_BS

AutomationDesk
AUD

RTI FPGA Programming Blockset1)
See p. 90
RTI DS1552 I/O Extension Blockset (p. 558)
RTI1552_I/O_EXT_ BS

MABXII Cylinder Pressure Indication Solution (p. 558)
MABXII_CPI_CPU

MicroAutoBox II AC Motor Control Solution Blockset
MABXII_ACMC_BS

RTI Watchdog Blockset (p. 554)
RTI_WATCHDOG_BS

XSG AC Motor Control Library
FPGA_XSG_ACMC

XSG Utils Library
FPGA_XSG_UTILS

NEW: XSG Advanced Engine Control Library (p. 107)
FPGA_XSG_ENGCON

NEW: V2X Solution (p. 100)
V2X_SOL

1)
Using the RTI FPGA Programming Blockset requires additional software, i.a. Xilinx products, please see p. 90.
®
550
2016

Introduction
Included One Ethernet Interface Cable (ETH_CAB1) is already included –
with each purchased MicroAutoBox II.
Optional DS4340 FlexRay Interface Module (p. 562)
DS4340

DS4342 CAN FD Interface Module (p. 563)
DS4342

FlexRay interface cable for MicroAutoBox II 1401/1507
FR_CAB1

Application Fields
FlexRay interface cable for MicroAutoBox II
FR_CAB3

1401/1511/1514 and 1401/1513/1514
Ethernet interface cable (LEMO to RJ45 connector), 5 m
ETH_CAB1

Electrically isolated Ethernet interface cable (300 Vrms,
ETH_CAB2

LEMO to RJ45 connector)
Ethernet cable to connect MicroAutoBox II and DCI-GSI2
ETH_CAB3

Ethernet interface cable (LEMO to RJ45 connector), 10 m
ETH_CAB4

USB interface cable (LEMO to USB connector) for connection USB_CAB13

to mass storage devices ("flight recorder")
LVDS link cable to connect MicroAutoBox and DCI-GSI1 or
LVDS_CAB1

DPMEM PODs (LEMO-1S to ZIF crimp contacts)
Software
LVDS link cable LEMO-1S to LEMO-1S, 5 m, 85 °C
LVDS_CAB15

MicroAutoBox Break-Out Box (p. 566)
DS1541

DS1552 Multi-I/O Module (p. 558)
DS1552

DS1553 ACMC Module (p. 560)
MABXII_ACMC

MicroAutoBox Embedded PC (p. 555)
See p. 555

Digital I/O extension for MABX II 1401/1507
MABXII_1507_DIO_SOL

MicroAutoBox II RapidPro Joining Plate (p. 554)
RAPIDPRO_MABX_KIT

Hardware
Engineering
551
2016

MicroAutoBox II 1401/1513/1514
Block Diagram
Ethernet Con-
host nector
interface (LEMO)
IBM PPC
750 GL 6 MB
communic.
memory
16 MB
16 MB flash
local RAM (non-volatile)
Clock/
calendar
64-Bit Global Bus
Performance
timer
Watchdog
Con-
USB nector
(LEMO)
Con-
ECU
nector
interface
(LEMO)
Con-
ECU
nector
interface
(LEMO)
Ethernet Con-
I/O nector
interface (LEMO)
Signal Generation/ Signal

Measurement Conditioning
CAN/LIN/serial Physical
module CAN/serial
module CAN/serial
I/O Connector
module CAN/serial
Local Bus/Intermodule Bus
Signal
Digital I/O
conditioning
(FPGA-based)
& protection
Signal
32-channel conditioning
16-bit ADC & protection
8-channel Signal driver

16-bit DAC & protection
Signal Generation/ Signal

Measurement Conditioning
IP module slot
(e.g., for FlexRay
or CAN FD)
I/O Connector
IP module slot
(e.g., for FlexRay
or CAN FD) Optional signal
conditioning on DS1552
Programmable FPGA or DS1553
FPGA extension slot Add-On Modules1)
552
2016 1)
The modules are optional, see pp. 557-561.

Introduction
Variants with DS1513 I/O Board with More CAN NEW: Variants with DS1514 I/O Board for Even More
Channels and More Analog I/O FPGA Performance
MicroAutoBox II now has even more CAN channels and also The variants 1401/1511/1514 and 1401/1513/1514 of
more analog inputs and outputs. The DS1513 I/O Board MicroAutoBox II have a very powerful Xilinx® Kintex®-7 FPGA
increases the number of CAN channels to 6, making the board (XC7K325T) that is freely programmable and can
Application Fields
MicroAutoBox II ideal for automotive function prototyping solve even the toughest prototyping tasks. Applications that
for electric/hybrid drives and for commercial vehicles. Its require extremely fast control loops can be run directly on
high number of analog inputs and outputs (32 x ADC, 8 x the FPGA. This includes calculations for combustion engine
DAC) provides additional flexibility for connecting sensors and electric motor control, noise and vibration suppression,
and actuators in areas such as combustion engines and and also computation-intensive signal preprocessing, to
vehicle dynamics controllers. The CAN interfaces are easy name a few examples.
to configure in Simulink® via the dSPACE blocksets RTI CAN dSPACE offers various plug-on boards that provide the re-
and RTI CAN MultiMessage (RTI = Real-Time Interface), quired I/O interfaces for numerous fields. While the DS1552
allowing quick, efficient configuration of the CAN network Multi-I/O Module (p. 558) with its comprehensive analog and
topology. The hardware of the new CAN interfaces sup- digital I/O can be used in a broad spectrum of application
Software
ports partial networking. This means that energy can be scenarios, the DS1553 (p. 560) with its interfaces for Hall,
saved by switching some CAN nodes off selectively while incremental encoder, resolver, EnDat and SSI sensors focuses
others are still active. mainly on the control of electric motors. The integrated Kin-
tex-7 FPGA of the new MicroAutoBox II variants supports the
Bypass-Based Prototyping1) new Xilinx® Vivado® tool chain. It can be programmed directly
from Simulink via the RTI FPGA Programming Blockset and
the Xilinx® System Generator for DSP Blockset. In addition,
there are two standard modules that can also expand the
Existing ECU
Hardware
system with FlexRay and CAN FD interfaces (DS4340 FlexRay
Interface Module, DS4342 CAN FD Interface Module). With
the 1401/1513/1514 variant, up to 10 independent CAN
channels can be used within a single MicroAutoBox.
Additional I/O I/O
MicroAutoBox II and AUTOSAR2)

In bypass-based prototyping, existing ECU software is op- MicroAutoBox II provides a comprehensive AUTOSAR real-
timized or partially revised. In this example, an automotive time operating system with low I/O latencies, similar to those
ECU is connected to the MicroAutoBox via an ECU inter- of production ECUs. It supports AUTOSAR versions 3.x and
Engineering
face. The original ECU executes all the functions that will 4.x. Compliance with AUTOSAR OS Scalability Class 1 ensures
remain unchanged, while the new algorithms are calcu- a high degree of compatibility with the AUTOSAR standard.
lated in the MicroAutoBox. The necessary input data and In addition, the most important basic software services, such
results are exchanged between the MicroAutoBox and the as the ECU State Manager (EcuM), NVRAM Manager (NvM),
original ECU. If your existing ECU already features the I/O and AUTOSAR CAN Stack, are supported.
data required by the new control strategy, you only need AUTOSAR application software can therefore be used in
an appropriate ECU interface and the MicroAutoBox for a realistic AUTOSAR environment for rapid control pro-
controller prototyping. If your algorithm requires additional totyping, benchmarking, and tests, long before the first
data, you can use the I/O interfaces of the MicroAutoBox prototypes of a production ECU become available.
or RapidPro, to directly connect new sensors or actuators
to the vehicle bus.
1)
To perform bypass-based prototyping, the RTI Bypass Blockset (p. 64) is required. 553
2)
For AUTOSAR compliant development, the RTI AUTOSAR Blockset (p. 86) is required. 2016

Multistage Watchdog Mechanism for More Safety

Overview Key Benefits
MicroAutoBox II has a multistage watchdog mechanism that Activating a predefined system behavior (e.g., system
performs run-time monitoring with configurable timeout reboot) in critical states
behavior. When critical states occur, the system responds Easy configuration directly in the Simulink model increases
immediately and in a defined manner. This gives you an efficiency. Same user experience as with any other RTI
added layer of safety when experimenting with prototype blockset.
vehicles in road and fleet tests. Two-stage watchdog concept (FPGA-based hardware
watchdog and configurable
The run-time watchdog can easily be programmed and inte- software watchdogs on the
grated into controller models via the RTI Watchdog Blockset. CPU) for setting up task-
Configuration and execution blocks for watchdog functional- specific monitoring
ity can be added to a model by simply dragging them from Configurable watchdog
the blockset library into a Simulink diagram. timeout functionality helps
monitor and analyze root
causes
All MicroAutoBox II vari-
ants supported
RTI Watchdog Blockset

Order Information
Product Order Information

RTI Watchdog Blockset RTI_WATCHDOG_BS

Combining MicroAutoBox and RapidPro

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.
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 com-
pact 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 RAPIDPRO_MABX_KIT

554
2016 1)
Shock and vibration ratings depend on the stack size. Please contact dSPACE for more information.

Introduction
MicroAutoBox Embedded PC
All Integrated
MicroAutoBox II with MicroAutoBox Embedded PC is a com- tainment, telematics and image processing applications.
pact, shock- and vibration-proof system for in-vehicle use The integrated Ethernet switch lets the host PC access both
that combines two powerful hardware units. While the actual units via the same Ethernet connection. Different startup
control functions are being computed on the real-time proto- and shutdown options are provided: for example, you can
typing unit of the MicroAutoBox, additional applications such remote-control both units either synchronously via the igni-
Application Fields
as telematics, digital road maps and camera-based object tion switch or completely independently of each other.
detection can run on the integrated MicroAutoBox Embedded The MicroAutoBox Embedded PC is an extension for the
PC. With all these possibilities, the system provides immense MicroAutoBox II. There are two hardware options (see
potential for developing advanced driver assistance, info- below).
Embedded PC with Intel® Atom™ N270 Embedded PC with Intel® Core™ i7-3517UE
Intel
Atom N270/1.6 GHz (passive cooling without fan)
® ™
Intel®
Core™ i7 dualcore processor, 2 x 1.7/2.8 GHz, 4 MB cache
2 GB RAM,
(temperaturecontrolled fan)
64 GB 2.5'' SATA SSD
8 GB DDR3 RAM

4 x USB 2.0
128 GB flash memory (64 GB integrated plus 64 GB userexchangeable

via CFAST card)
Software
Optional: Variant with 576 GB flash memory (512 GB integrated plus 64 GB
userexchangable via CFAST card)
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

Rearside ExpressCard slot, e.g., to support FireWire or customerspecific hardware

Temperature range: 0 ... +60 °C (+32 ... +140 °F)

Windows® 7 or Ubuntu/Linux operating system

Hardware
DS1511
In Out
I/O Board
I/O connector
FPGA
DS1401 Processor
Processor
Board Ethernet Host Ethernet I/O
USB 2.0, DVI-I, Power connectors
Gbit Ethernet PCIe

3 x Ethernet, 2 x USB 3.0, 2 x
COM Express
Switch Mini Card
processor
module,
Intel® Core™ 128 GB
Engineering
MicroAutoBox II 1401/1511
i7 dual-core, flash memory Express Embedded PC
2 x 1.7/2.8 GHz, (64 GB Card
8 GB DDR3 integrated
RAM plus 64 GB Example:
exchange-
able via MicroAutoBox II 1401/1511 and
CFAST
Embedded PC
CFAST card) MicroAutoBox Embedded PC with
Intel® Core™ i73517UE.
Order Information

MicroAutoBox Embedded PC with Intel Atom N270
® ™
MABXII_EMB_PC, Option: IA16_S64

MicroAutoBox Embedded PC with Intel® Core™ i73517UE (128 GB flash memory) MABXII_EMB_PC, Option: I7_S64C64

MicroAutoBox Embedded PC with Intel® Core™ i73517UE (576 GB flash memory) MABXII_EMB_PC, Option: I7_S512C64

WLAN PCIe Mini Module for 802.11 b/g/n EMB_PC_WLAN

555
2016

MicroAutoBox II 1401/1513/1514 and

Embedded PC with Intel® Core™ i73517UE
Block Diagram
UBat = 7 … 32 V Remote control inputs
RS232, 16-bit 16-bit

CAN DIO PCIe Mini Card ExpressCard CFAST
LIN ADC DAC
FPGA and IP modules Power supply unit

Power supply unit
I/O-Piggyback Remote control COM Express
module processor module,
Intel Core™ i7 dual-core
®
FPGA IP module 1 IBM PowerPC, 128 GB flash memory processor,

900 MHz, (64 GB integrated plus 64 GB 2 x 1.7/2.8 GHz,
1 MB cache exchangeable via 8 GB DDR3 RAM
IP module 2
CFAST card)
(e.g., FlexRay)
USB data LVDS Ethernet Ethernet 2 x USB 3.0,

Gbit Ethernet DVI-I
storage interface I/O host 2 x USB 2.0
MicroAutoBox II 1401/1513/1514 Embedded PC unit
Gbit Ethernet switch
3 x Gbit Ethernet
556
2016

Introduction
I/O Extensions for the SimulinkProgrammable FPGA1)
Flexible Extension Two I/O Modules Available
The FPGA technology integrated in MicroAutoBox II The DS1552 Multi-I/O Module (p. 558) is a universal
addresses new use scenarios with varying I/O requirements. I/O module which offers many powerful I/O converters
For greater flexibility, the I/O converters are sourced out to and several interfaces. For example, it can be used for
separate add-on modules, which can easily be integrated into FPGA-based cylinder pressure indication.
the MicroAutoBox II 1401/1511/1514 and 1401/1513/1514 The DS1553 ACMC Module (p. 560) is an I/O module
Application Fields
(only one module at a time). It is easy to change the mod- with I/O optimized for the control of various electric drives.
ules later on.
FPGA I/O Extension Module

DS1552 Multi-I/O DS1553 AC Motor
I/O connector
In Out Module Control Module
Software
FPGA
DS1514 (programmable)
FPGA Board
DS1401
Processor
Processor Board
I/O connector
MicroAutoBox II 1401/1511/1514
FPGA and 1401/1513/1514
DS1511 or
DS1513 The FPGA I/O extension modules are easy
In Out
I/O Board to integrate into the MicroAutoBox II
Hardware
1401/1511/1514 and 1401/1513/1514.
Programming Options
Customer-Specific Solution
DS1552 Multi-I/O Module DS1553 ACMC Module via dSPACE Engineering
Services
Dedicated RTI blockset   optional
optional
Engineering
®
Xilinx tools plus RTI FPGA Programming Blockset
1)
 2)
VHDL  – optional
1)
Using the RTI FPGA Programming Blockset requires additional software, i.a. Xilinx® products,
please see p. 90. 557
2)
XSG AC Motor Control Library required for the I/O framework. 2016

DS1552 MultiI/O Module

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 convert-
ers and different serial interfaces. It is easy to install in the
MicroAutoBox II 1401/1511/1514 and 1401/1513/1514.
There are different use cases:
Use Case 1: Use Case 2:

User-Specific FPGA Programming Additional I/O Channels for the Standard I/O
The DS1552 provides I/O interfaces for the user-pro- You can supplement the standard I/O interfaces of the
grammable FPGA in the MicroAutoBox II. The FPGA is MicroAutoBox II with additional I/O channels (configurable
programmed by model-based design with the RTI FPGA with RTI DS1552 I/O Extension Blockset). The FPGA is not
Programming Blockset1), in VDHL or via dSPACE Engineer- user-programmable, and Xilinx® tools are not needed in this
ing Services. 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 RTI DS1552 I/O Extension Blockset
Generator blockset in an XSG model with RTI blocks.
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 angle-
synchronous pressure measurement with 0.1° max. resolu-
tion. The evaluation of the pressure values can be controlled
by several algorithms, e.g., released heat, combustion mass
center, indicated mean effective pressure.
1)
Using the RTI FPGA Programming Blockset requires additional software, i.a. Xilinx® products, please see p. 90.
558
2016

Introduction
NEW: Use Case 4:
Advanced Control Design for Combustion Engines
with Dedicated XSG Solution
The XSG Advanced Engine Control Library (p. 107) enables the
implementation of controller functionalities in both the CPU
and the FPGA of the MicroAutoBox II 1401/1513/1514, which
Application Fields
in this case is combined with the DS1552 Multi-I/O Module.
The library therefore provides lots of ready-to-use, configu-
rable elements for common engine control functionalities
like crank and cam signal processing, ignition and injection
control, and even cylinder pressure indication. As the func-
tions do not require manual FPGA programming, users do not
have to deal with complex signal preprocessing and can fully
concentrate on developing new control algorithms. This smart
combination with the XSG Library upgrades MicroAutoBox
to a very compact and powerful RCP system, which already
Software
today offers a comfortable and tool-assisted in-cycle control FPGA functionalities within the XSG Advanced
for combustion engines. Moreover, the XSG Advanced Engine Engine Control Blockset.
Control Solution is designed as an open XSG blockset that
enables the user to gain detailed insights into the algorithms
and to modify them wherever it is necessary.
I/O Resources of the DS1552
Specification
Hardware
Parameter
Accessible via the RTI FPGA Programming Blockset2) Accessible via the RTI DS1552 I/O Extension Blockset
Analog input 8 parallel, 16bit, 1 Msps analog input channels (0 ... 5 V input range)

16 multiplexed, 16bit, 200 Ksps analog input channels (±10 V input range)

Sensor supply, 2...20 V configurable
–
Analog output 4 16bit analog output channels (0 ... 5 V output range)

Digital I/O 16 input channels

16 output channels, 5 mA output current

Input / output logic levels: 5 V or levels up to 40 V (depending on VDrive), selectable

8 bidirectional channels, logic level selectable (3.3 V or 5 V),
–
Engineering
45 mA output current
Order Information

DS1552 MultiI/O Module DS1552

RTI FPGA Programming Blockset1) RTI_FPGA_BS1)

RTI DS1552 I/O Extension Blockset RTI1552_I/O_EXT_BS

MABXII Cylinder Pressure Indication Solution MABXII_CPI_CPU

NEW: XSG Advanced Engine Control Library (p. 107) FPGA_XSG_ENGCON

1)
559
2016

DS1553 AC Motor Control Module

Electric Drives Control
The DS1553 AC Motor Control Module is an I/O piggyback
module with I/O that is optimized for controlling various
electric drives. It provides interfaces for Hall, incremental
encoder, resolver, EnDat and SSI sensors, and can be installed in
MicroAutoBox II 1401/1511/1514 or 1401/1513/1514.
There are two different use cases:
Use Case 1: Use Case 2:

User-Specific FPGA Programming AC Motor Control Solution
The DS1553 provides I/O interfaces for the user-programma- The MicroAutoBox II AC Motor Control Solution uses the
ble FPGA of MicroAutoBox II. The XSG AC Motor Control DS1553 module in conjunction with a dedicated FPGA firm-
Library (p. 106) enables the implementation of controller ware and provides a comprehensive and easy-to- use RTI
functionalities in both the CPU and the FPGA. With its ready- blockset for controlling various electric drives. All modeling
to-use, configurable elements for common electric drives is performed on the processor via MATLAB® Simulink® – no
control, users do not have to deal with complex signal pre- FPGA programming by the user required.
processing and can fully concentrate on developing new
control algorithms.
Use Case 1: XSG AC Motor Control Library Use Case 2: MicroAutoBox II AC Motor Control Solution Blockset
560
2016

Introduction
I/O Resources of the DS1553
Digital input 8 channels, 0 ... 5 V, differential or single-ended, software-configurable

Digital output 16 channels, 0 ... 5 V, single-ended to generate gate driver signals, PWM synchronization signals, bit out

8 additional channels by modifying IP-module pins

Application Fields
Analog input 8 channels, software-configurable input voltage range (±5 V, ±15 V, ±30 V), differential, 10 Msps

Analog output 2 channels, -10 ... 10 V (single-ended) 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 (software-configurable)
RS422/RS485 4 RS485 transceivers for connecting 2 serial angle meters (e.g., EnDat or SSI interface)

Power supply for sensors 12 V: max. 50 mA

5 V: max. 50 mA (use the MicroAutoBox II VSENS-PIN for currents up to 250 mA)

Order Information
Software
DS1553 AC Motor Control Module MABXII_ACMC

MicroAutoBox II AC Motor Control Solution Blockset MABXII_ACMC_BS

RTI FPGA Programming Blockset1) RTI_FPGA_BS

XSG AC Motor Control Library including XSG Utils Library and XSG AC Motor FPGA_XSG_ACMC

Control Interface Library
1)
Hardware
Engineering
561
2016

DS4340 FlexRay Interface Module

FlexRay Interface Module
The FlexRay Interface Module can be used with
MicroAutoBox II 1401/1511/1514, 1401/1507, and
1401/1513/1514. The module supports FlexRay protocol
specification 2.1 and is downward-compatible with previous
standards. It provides a hardware-configurable, switchable
termination circuit.
General Supports the FlexRay protocol specification 2.1

For use with MicroAutoBox II 1401/1507, 1401/1511/1514, and 1401/1513/1514

Communication via Industry Package (IP) mechanism (for MicroAutoBox 1401/1507) or via fast COM mode

(for MicroAutoBox 1401/1511/1514 and 1401/1513/1514)
Molex connectors for direct access to FlexRay bus lines

Switchable termination circuit (hardware-configurable)

Feed-through possibility for FlexRay bus lines in passive-linear-bus topology

Two FlexRay channels

Hardware details Freescale MFR43xx Communication Controller Family

Dual PHY Interface with TJA1080

For wake-up, hardware modification of the MicroAutoBox and the DS4340 is required.

Order Information

DS4340 FlexRay Interface Module DS4340

562
2016

Introduction
DS4342 CAN FD Interface Module
Module for Interfacing CAN FD Buses
The dSPACE DS4342 CAN FD Interface Module
(FD=Flexible Data Rate) can be used with MicroAutoBox II
1401/1511/1514, 1401/1507, and 1401/1513/1514. The
DS4342 provides two independent CAN channels, each
of which can be used for CAN FD or for CAN. Network
Application Fields
management functions such as wake-up and sleep are
also included.
General 2 CAN FD channels

For
use with MicroAutoBox II 1401/1507, 1401/1511/1514, and 1401/1513/1514
Automatic detection of Industry Package (IP, for MicroAutoBox 1401/1507) or fast COM mode (for MicroAutoBox 1401/1513/1514)

Supported by RTI CAN MultiMessage Blockset

Suited for ISO 118985 network management

Suited for handling ISO 118982 CAN or CAN FD on every channel

Hardware details NXP TJA1145T CAN Transceiver

Software
Requires one additional slot

Order Information

DS4342 CAN FD Interface Module DS4342

Hardware
Engineering
563
2016

Certifications
Standards Robustness Tests
Like all dSPACE hardware products, MicroAutoBox meets To verify their reliability under realistic operating condi-
the requirements of the European Committee for Electro tions, the standard MicroAutoBox variants were exposed
technical Standardization (CENELEC) and is therefore to shock and vibration tests during which they continuously
CE-compliant. executed a program.
Characteristics Applied Standard1) Description

Electromagnetic EN 61326-1, Table 2 Immunity standard for industrial environments
compatibility (EMC) CISPR 11, EN 55011 Group 1, Class A Emission standard for industrial environments
RTCA/DO160G: Dec. 2010: Environmental conditions and test procedures for airborne equipment: Conducted RF
Section 21.4 Emissions, Category: B, L, M&H1)
RTCA/DO160G: Dec. 2010: Environmental conditions and test procedures for airborne equipment: Radiated RF
Section 21.5 Emissions, Category: M1)
Vibration ISO 16750-3:2007 / 4.1.2.4 Test IV Test conditions: Broadband noise, 4h per axis, RMS acceleration 27.8 m/s2
DO-160F.8 / B1 Test Conditions Test conditions: Broadband noise, 2h per axis, based on DO160F Section 8, Category B1
EN 60068-2-6 Test conditions: swept sine, 1 octave per minute, 3-axis test / 5 ... 2000 Hz, up to 5 g,
2 sweeps per axis / operating
Shock ISO 16750-3:2007 / 4.2.2 Linear shock (1/2 sine pulse), 6-axis / 500 m/s², 6 ms, 10 pulses per axis / operating
RTCA / DO-160F Section 7 Test 7.2 Operational shocks test (standard): sawtooth wave, 6-axis / 200 m/s2, 11 ms, 10 pulses per
Category A, Test type R axis / operating
RTCA / DO-160F Section 7 Test 7.2 Operational shocks test (low frequency): sawtooth wave, 6-axis / 200 m/s2, 20 ms,
Category D, Test type R 10 pulses per axis / operating
1)
For more detailed information about test conditions and tested variants, please inquire.
Engineering Services
I/O Specifications Custom-Specific Signal Conditioning
dSPACE offers engineering services to adapt the I/O and The signal conditioning portion of MicroAutoBox can also
signal conditioning of MicroAutoBox to your specifications. be adapted to your requirements: for example, if filter
For I/O, dSPACE offers predeveloped, verified designs that circuits or amplifiers have to be integrated. And if you want
can easily be integrated in MicroAutoBox. In general, these to include your own signal conditioning concepts, dSPACE
modules do not have to be modified to suit your application, will integrate your designs in the board layout. You can even
which saves development time and reduces engineering completely design the segment yourself.
costs. The same I/O modules can of course be integrated
several times. dSPACE will also include the I/O circuit designs MicroAutoBox with ARINC Interface for Aerospace
you provide, such as company-specific CAN controllers, Applications (Example of Add-On I/O Solutions)
ASIC, or plug-on devices, and will also design new circuits An ARINC interface can be integrated (by dSPACE
according to your specifications. For the MicroAutoBox II Engineering Services) on the IP module slots offered
1401/1511/1514 and 1401/1513/1514, dSPACE offers engi- by MicroAutoBox II 1401/1511/1514, 1401/1507, and
neering services for hardware/software interface integration 1401/1513/1514.
via FPGA programming.
564
2016

Introduction
MicroAutoBox II Software Support
Real-Time Interface
The Real-Time Interface (RTI) library provides the link between It provides a blockset that implements the functionality
dSPACE MicroAutoBox II and the development software and I/O capabilities of MicroAutoBox II in your Simulink
MATLAB®/Simulink®/Stateflow® from MathWorks®. controller models.
Application Fields
MicroAutoBox II RTI Blockset
The latest MicroAutoBox II Blockset covers the additional
I/O functionalities of the variants 1401/1511/1514 and
1401/1513/1514, 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.
Software
Hardware
Wellstructured and ready for use with
new and previous MicroAutoBox variants:
the MicroAutoBox II RTI Blockset.
RTI Blocks for Variant 1401/1513/1514

The RTI blockset includes the I/O functions available
with MicroAutoBox II. All I/O is intuitively organized and
Engineering
structured so that you can easily find the I/O you require.
All I/O is easy to access via a well

organized, intuitive structure.
565
2016

MicroAutoBox Hardware / MicroAutoBox BreakOut Box
MicroAutoBox BreakOut Box1)

Universal desktop connection panel for MicroAutoBox
Highlights
Fast and flexible signal connection

Checking and reconnecting signals without changing

an existing cabling harness
For use with all MicroAutoBox variants

Key Benefits
The MicroAutoBox Break-Out Box provides easy access The Break-Out Box can be used with all MicroAutoBox
to all signals on the I/O connectors of the MicroAutoBox variants.
(p. 548). You can observe signals and/or reconnect them
without changing an existing cable harness.
Terminal points Knife disconnectors
Connector to
Connector to sensors and
MicroAutoBox actuators
1)
Devices connected to the MicroAutoBox Break-Out Box can feed in high currents and high voltages which can be dangerous for
566 the user. Under all circumstances, you must observe all the safety precautions described in the documentation of the MicroAutoBox
2016 Break-Out Box and of the devices connected.

MicroAutoBox Hardware / MicroAutoBox Break-Out Box
Introduction
Technical Details
General I/O connectors: a) for connection to MicroAutoBox II and b) for connection to

an existing cable harness
Knife disconnectors to interrupt the signal path

Application Fields
Physical size 341 x 224 x 61 mm (13.4 x 8.8 x 2.4 in.)

Ambient temperature 0 ... +70 °C (+32 ... +158 °F)

Order Information

MicroAutoBox Break-Out Box DS1541

Relevant Hardware
Software
Included One connection cable to MicroAutoBox is already included –
with each purchased MicroAutoBox Break-Out Box.
Required MicroAutoBox II
See p. 550

Hardware
Engineering
567
2016

RapidPro Hardware / Introduction
RapidPro Hardware
Flexible hardware for rapid control prototyping
Highlights
Scalable, modular, and configurable system architecture
Compact and robust enclosure

For in-vehicle, laboratory, and test bench use

Comprehensive software support

Application-specific configurations for common

application areas (p. 572)
Advances for engine control: Any-crank/cam technolo-

gies and start/stop development support
Signal Conditioning and Power Stages Intelligent I/O Subsystems

The wide variety of sensors and actuators used in the The functions being developed and integrated into cars are
automotive field, especially during the prototyping phase, growing in complexity and volume. The acquisition and gener-
means that each sensor or actuator often requires its own ation of I/O signals is also growing in complexity, for example,
signal conditioning and power stage circuits. The flexibility in engine management applications. Moreover, sophisticated
and intelligent assistance provided by RapidPro will help you algorithms usually need to be processed in a minimum of time.
achieve challenging tasks for signal conditioning and power All these demanding tasks need to be performed within a
stages with high efficiency. standard prototyping environment with intelligent tools for
For details, see Use Scenario A (p. 570) assistance. With RapidPro you can build an intelligent I/O
subsystem based on an MPC565 microcontroller.
For details, see Use Scenario B (p. 571)

The RapidPro hardware works as an extension to dSPACE The RapidPro hardware can be used for various applications.
prototyping systems. Its enclosure is designed so that you can To get you started working easily, dSPACE offers off-the-
use the RapidPro units separately or connect several of them shelf, predefined configurations for common application
to build a stack to use as one physical unit. Off-the-shelf areas such as:
hardware- and software-configurable signal conditioning Engine control
(SC) and power stage (PS) modules (p. 585) can be installed Body control
in the units to set up individual systems that optimally fit Chassis control
the needs of a particular application. The modular Transmission control
concept, using modules that are hardware- and software- Electric motor control
configurable, means that all components can be reused,
reconfigured, or extended with a minimum of effort, for
example in later projects or if requirements change.
568
2016

Introduction
1 2
Application Fields
3 4
Several RapidPro units can be connected for use as RapidPro modules (p. 585) can be easily installed in
one physical unit. and removed from the units.
Software
Engineering Services for RapidPro
To assist you with your function prototyping activities,
dSPACE offers specific engineering services (see also p. 608)
for RapidPro hardware:
Hardware
System design and configuration

Mapping of actuators and sensors to signal conditioning

(SC) and power stage (PS) modules
Specification and assembly of wiring harnesses

Development of customer-specific SC and PS modules

Template Simulink®/Real-Time Interface (RTI) models

Commissioning and system introduction onsite

Engineering
569
2016

Use Scenario A
Signal Conditioning and Power Stages for dSPACE
Prototyping Systems
The RapidPro SC Unit and the RapidPro Power Unit (equipped lamps, and relays require high current and/or high voltage
with the relevant SC and PS modules, p. 585) can be used output drivers. The RapidPro Power Unit provides your
as separate units in conjunction with prototyping systems prototyping system with the necessary power stages.
(MicroAutoBox, MicroLabBox, Modular Hardware includ- Automotive protection and extensive diagnostic capabilities are
ing DS1005 and DS1007 plus I/O boards, Single-Board especially important for power stages, for example, in safety-
Hardware). The RapidPro SC Unit supports your proto- critical applications. Using dSPACE‘s ConfigurationDesk®
typing system wherever demanding signal conditioning software (p. 48) you can easily configure the unit and carry
tasks such as signal protection, amplification, attenu- out diagnostics. In this use scenario, the RapidPro hardware
ation, filtering, and electrical isolation have to be per- can be used for developing control applications in fields such
formed. In turn, actuators like drives, valves, injectors, as engine, transmission, chassis, body, and drives control.
dSPACE Prototyping Systems
Analog and
digital signals + SPI
USB
RapidPro RapidPro
SC Unit 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.
570
2016

Introduction
Use Scenario B
Intelligent I/O Subsystems for dSPACE Prototyping
Systems
Applications such as engine management need to ac- An integrated Unit Connection Bus (UCB) allows you to
quire complex I/O signals, for example, for crankshaft connect several RapidPro SC or Power Units directly to
and camshaft positions, and to generate complex sig- the Control Unit without external wiring. Communication
nals for ignition and injection independently of the RCP between the RapidPro Control Unit and the prototyping
Application Fields
system’s main processor and the model’s simulation step system is performed via a high-speed link. A RapidPro Con-
size. Offloading specific, time-critical tasks like these to trol Unit Blockset (p. 575) for MicroAutoBox and modular
a dedicated microcontroller decisively reduces the main DS1005- or DS1007-based systems is available as an I/O
processor’s load. The RapidPro Control Unit variant with Real-Time Interface (RTI) for Simulink. dSPACE‘s Configura-
MPC565 is used in this scenario as a slave microcontroller tionDesk (p. 48) provides intuitive configuration of the unit
to extend existing prototyping systems with additional and diagnostics handling. In this use scenario, the RapidPro
I/O functionality. The RapidPro Control Unit variant can hardware can be used for developing control applications
be used together with the MicroAutoBox or a modular in fields such as engine, transmissions, chassis, body, and
DS1005- or DS1007-based system (with DS4121 ECU drives control.
Interface Board) or can additionally be combined with other
Software
RapidPro units.
dSPACE Prototyping Systems
LVDS link
Hardware
RapidPro
Power Unit
USB
RapidPro
Control Unit
with MPC565
Hardware configuration
Engineering
Actuators 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.
571
2016

Application-Specific Configurations
RapidPro’s predefined configurations cover a wide range of dSPACE also provides dedicated Simulink® startup mod-
typical signal conditioning and power stage tasks in vari- els for the configurations. These include all the available
ous application areas. For example, the configurations for I/O signals which are already configured in corresponding
engine control prototyping let you run engines with up to tasks (e.g. angle-synchronous tasks for engine control). This
6 cylinders and all modern sensors and actuators, and the enables a fast startup and lets you concentrate fully on
configuration for electric motor control serves as a flex- your primary task of developing control algorithms for your
ible inverter stage during the prototyping phase of diverse application. If your specific I/O requirements differ from the
AC electric motors. Each configuration consists of selected setups, this is no problem at all. You can adapt one of the
RapidPro power and signal conditioning modules (p. 585) ready-made configurations or build a new RapidPro system
installed in the corresponding number of RapidPro units. from scratch. Either way, RapidPro will help you solve your
A RapidPro Control Unit is used whenever complex I/O sig- specific signal conditioning and power stage task.
nals need to be captured or generated, or a large number
of I/O signals are involved. For further information, please contact dSPACE.
Overview of RapidPro Configurations

Application RapidPro Control Unit RapidPro SC Unit RapidPro Power Unit
Engine control 10 analog inputs
– 6 high-side outputs

Basic configuration 2 lambda inputs
12 low-side outputs

(based on Use Scenario B) 6 crank/camshaft inputs
2 DC motor outputs

8 digital inputs
(opt. 2 direct injection outputs)
7 digital outputs

Engine control 2 lambda inputs
30 analog inputs
6 direct injection outputs

Advanced configuration for 4 knock sensor inputs
16 digital outputs
6 high-side outputs

6 cylinders 6 crank/camshaft inputs
4 sensor supply outputs
24 low-side outputs

(based on Use Scenario B) 8 digital inputs
2 DC motor outputs

(2 RapidPro Power Units needed)
Body control – 24 digital inputs
6 low-side outputs

Basic configuration 10 analog inputs
18 high-side outputs

(based on Use Scenario A) 8 digital outputs
2 full-bridge outputs

Body control 32 digital inputs
28 digital inputs
6 low-side outputs

Advanced configuration (opt. 4 sensor supply outputs) 10 analog inputs
24 high-side outputs

(based on Use Scenario B) 2 full-bridge outputs

Chassis control – 14 analog inputs
12 low-side outputs

Basic configuration 16 digital inputs

(based on Use Scenario A) 8 digital outputs

4 sensor supply outputs

Chassis control 16 digital outputs
16 digital outputs
18 low-side outputs

Advanced configuration 4 sensor supply outputs
2 full-brige outputs


Transmission control 20 analog sensors
– 12 low-side outputs

6 high-side outputs


Electric motor control – – 6 digital motor control inputs

2 digital brake chopper inputs

3 motor phase half-brigde outputs

1 brake chopper half-bridge output

3 analog outputs for motor current

measurement
572
2016

Introduction
Basic Configuration for Chassis Control
14 analog sensors 12 low-side drivers

 Temperature  Proportional valves
 Pressure  Valves for hydraulic control
 Acceleration
Application Fields
 Level sensors
4 x sensor supply 2 full bridge driver

 Sensors  DC motor
 Parts  Stepper motor
 Devices
16 digital inputs Power Unit 8 digital outputs

 Level sensors
SC Unit
 PWM outputs
 Various switches  Relay driver
 Wheel speed sensors  Flexible controls
Software
The basic configuration for chassis control is based on Use Scenario A (p. 570) and offers all the sensors and actuators needed for chassis
control development.
Advanced Configuration for Engine Control
Up to 30 analog sensors 6 inputs for camshaft 6 solenoid valve drivers

and crankshaft Solenoid injection valves
 Temperature
Speed and position of
 Pressure
Hardware
camshaft and crankshaft
 Throttle position
 Air mass flow 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
4 knock sensor inputs Power Unit
Engineering
SC Unit
6 high-side drivers
Control Unit  Relays
 Valves
16 digital inputs
 Switches
 Brake and clutch pedal 4 x sensor supply 16 digital outputs
 Neutral gear  Sensors  PWM outputs
 Cruise control  Parts  Relay drives
 …  Devices  Flexible controls
The advanced configuration for engine control is based on Use Scenario B (p. 571) and is suitable for engine control development for up
to 6 cylinders.
573
2016

Application Areas for RapidPro Modules
To cover today´s variety of sensors and actuators, the project, and home-made solutions are no longer necessary.
RapidPro hardware consists of ready-made and easy-to-insert The RapidPro signal conditioning and power stage modules
hardware- and software-configurable interface modules for (p. 585) can be easily combined to cover a wide range of
the highest degree of flexibility. Changes in the sensor and application fields.
actuator setup are no longer a risk for your development
Available Signal Conditioning Application Fields

and Power Stage Modules Engine Control Transmission Chassis Body Control Drives
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  
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 
574
2016

Introduction
RTI RapidPro Control Unit Blockset
In conjunction with the MPC565-based RapidPro Control Unit Functionalities can be combined with each other in realtime
(Use Scenario B, p. 571), a generic Real-Time Interface (RTI) applications, e.g., drives and engine functionalities. When
Blockset for Simulink is available for MicroAutoBox and modu- combining the MPC565-based RapidPro Control Unit and
lar DS1005- or DS1007-based systems. The blockset provides MicroAutoBox or the modular DS1005 or DS1007-based
extensive standard I/O functionalities (PWM, bit I/O, A/D) system, you gain additional functionalities for engine control
Application Fields
including incremental encoder interface and stepper motor compared to using the MicroAutoBox on its own:
control, as well as diagnostic functionalities and special func-
tionalities for engine, chassis and drives control. Examples:
Crankshaft signal measurement

Engine speed and status

Camshaft signal measurement

Injection and ignition pulse generation

Angle-synchronized task triggers

Reading diagnostic data of modules

Software
Checking the status of a carrier board

Any-crank/cam technologies with fully configurable,

map-based setup of crank/cam wheel geometry The RTI RapidPro
Support of crank sensors with rotation detection Control Unit Blockset
for HEV and start/stop system development for MicroAutoBox and
n Fast, ECU-like engine synchronization DS1005 or DS1007.
Hardware
MicroAutoBox plus RapidPro Control Unit
Topic Examples of extended functionality

Crankshaft control Crankshaft signals with up to 3600 pulses per wheel with or without gaps

Camshaft control Support of virtually every type of camshaft wheel

Phase measurement of camshaft position

Up to 4 camshaft wheels at a time

Injection control Generation of peak-and-hold pulse patterns (up to three phases)

Up to 15 injection pulses for one injection cycle
Engineering

Common Up to 12 channels for injection plus 12 channels for ignition simultaneously

High engine angle resolution of 0.1°

4 periodical and 16 absolute angle-based interrupts per engine cycle

575
2016

RapidPro Hardware / Hardware Overview
Hardware Overview
Component Description Further Use Use
Information Scenario Scenario
A (p. 570) B (p. 571)
RapidPro SC Unit Signal conditioning unit
p. 577  
Slots for up to 8 signal conditioning modules

USB interface for hardware configuration via ConfigurationDesk®

RapidPro Power Unit Power stage unit

p. 579  
Slots for up to 6 power stage modules

USB interface for hardware configuration via ConfigurationDesk

RapidPro Control Unit Intelligent I/O subunit for adding additional I/O functionality
p. 582 – 
with MPC565 to the dSPACE prototyping system
MPC565 microcontroller module

Up to 6 signal conditioning modules

Up to 2 communication modules

USB interface for hardware configuration via ConfigurationDesk

LVDS interface for high-speed slave communication with

MicroAutoBox or DS1005 (via DS4121)
SC Modules 4-channel sensor supply module
p. 586  
4-channel differential analog input module
p. 586  
10-channel analog input module
p. 586  
8-channel digital input module
p. 586  
8-channel digital output module
p. 586  
Crankshaft/camshaft sensor input module
p. 586  
2-channel exhaust gas oxygen sensor module for Bosch LSU
p. 586  
4.2, 4.9, and LSU ADV broadband lambda probes
4-channel knock sensor module
p. 586 – 
8-channel thermocouple sensor input module
p. 586 – 
2-channel exhaust gas oxygen sensor module for DENSO
p. 587  
broadband lambda probes
8-channel digital out module with push-pull functionality
p. 587  
Further modules are under development

PS modules 2-channel full-bridge driver module
p. 587  
6-channel low side driver module
p. 587  
6-channel high side driver module
p. 588  
1-channel, high-current, full-bridge driver module
p. 588  
2-channel, high-current, half-bridge driver module
p. 588  
2-channel direct-injection driver module1)
p. 588  
1-channel, high-current, full-bridge driver module for
p. 589  
12 V and 24 V applications
2-channel, high-current, half-bridge driver module for
p. 589  
12 V and 24 V applications
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
1)
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.
576
2016

RapidPro Hardware / RapidPro SC Unit
RapidPro SC Unit
Introduction
Flexible signal conditioning unit
Highlights
Application Fields
Signal conditioning for dSPACE prototyping systems

Easily adaptable to different sensor types via

configurable modules
Slots for up to 8 signal conditioning modules

Wide supply range (6 V to 60 V), reverse and overvolt-

age-protected
Software
Application Areas pact enclosure and an advanced mechanical concept. It
The RapidPro SC Unit in conjunction with the standard SC is not only suited to in-vehicle use, but also to the labora-
modules (p. 586) or customer-specific modules lets you tory and the test bench. All inputs and outputs are auto-
adapt almost any type of sensor (for example, temperature, motive-protected. A RapidPro SC Unit can be equipped
pressure, and crankshaft and camshaft sensors) to specific with single- and/or multi-channel SC modules mounted
prototyping systems. 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
Hardware
Key Benefits an enable/disable input. A USB interface is available for
The RapidPro SC Unit is highly modular, flexible, intelli- communicating with the host PC. dSPACE‘s Configura-
gent, and especially designed for rapid control prototyping tionDesk (p. 48) provides easy configuration of the unit and
in automotive applications. It comes with a robust, com- diagnostics handling.
Technical Details
Engineering
General 8 slots for configurable, analog or digital signal conditioning modules (SC modules, p. 586)

Support of modules with different form factors

Up to 64 channels per unit (for example, 40 analog plus 24 digital I/O or 40 digital plus 24 analog I/O)

Unit Connection Bus for use with RapidPro Control Unit (p. 582)

Onboard A/D converter to display I/O signals
of the installed SC modules
Internal temperature and voltage monitoring

Remote control input to switch the unit on or off

Enable/disable input to switch all outputs of a unit on or off

Software support Configuration Configuration of the SC modules from a host PC via ConfigurationDesk (p. 48)

Diagnostics Diagnostics handling via ConfigurationDesk

Electrical Power supply +6 … +60 V DC

characteristics Load dump protection up to +100 V

Reverse voltage protection up to 100 V

577
2016

RapidPro Hardware / RapidPro SC Unit
Technical Details
Mechanical Enclosure Aluminum enclosure with cooling fins (no fan)

characteristics Advanced mechanical concept with special coulter clips for easy installation and

module locking
Enclosure designed for flexible assembly (stack or single unit)

Physical size (with cover and base plate) 200 x 225 x 35 mm (7.87 x 8.86 x 1. 38 in)

Physical size (without cover and base plate) 172 x 225 x 25 mm (6.77 x 8.86 x 0.98 in)
Environmental Ambient temperature -40 … +85 ºC (-40 … +185 ºF)

characteristics
Vibration resistance1) EN 60068-2-6 Test conditions: n
Swept sine, 1 octave per minute, 3-axis test
5 ... 2000 Hz, 5 g (crossover 13 Hz), 2 sweeps

Operating

ISO 16750-3:2007 / 4.1.2.4 Test IV Test conditions: n

Broadband noise, 2 h per axis / 3 spatial axes
RMS acceleration: 27.8 m/s2

Operating

Shock resistance1) EN 60068-2-27 Test conditions: n
Acceleration: 15 g/11 ms; 100 g/5 ms

Operating

ISO 16750-3:2007 / 4.2.2 Test conditions: n


Operating

1)
Order Information

RapidPro SC Unit RAPIDPRO_1621 (please inquire)


Required ConfigurationDesk (p. 48) CFD-C


Required SC Modules See p. 585
If the DS1664 2-channel direct injection driver module is used with USB_CAB12 (USB PC to LEMO cable with galvanic

RapidPro (Power Unit), electrically safe host PC interface cables (up to isolation, 4.5 m)
300 V DC/ACRMS and 600 V peak) are mandatory for all connected Further cables: please inquire.

systems such as RapidPro, MicroAutoBox, and DS1005. You must
perform all the safety precautions described in the documentation.
Optional RapidPro Power Unit (p. 579) RAPIDPRO_1651 (please inquire)

RapidPro Control Unit with MPC565 (p. 582) RAPIDPRO_1601 (please inquire)

Front connectors for RapidPro SC Unit RPS_F1F2

Rear connectors for RapidPro SC Unit RPS_R1R2

Crimping tool for RapidPro systems RAPIDPRO_CRIMP

RapidPro Break-Out Box for SC Unit (p. 590); 2 x connection cable DS1687

RapidPro SC Unit (F1/F2) and BOB (F1/F2), 0.5 m
USB PC to LEMO cable, 3 m USB_CAB6

578
2016

RapidPro Hardware / RapidPro Power Unit
RapidPro Power Unit
Introduction
Flexible power stage unit
Highlights
Application Fields
Power stages for dSPACE prototyping systems

Easily adaptable to different actuators via

configurable modules
Slots for up to 6 power stage modules

Wide supply range (6 V to 60 V), reverse and over-

voltage-protected

Software
The RapidPro Power Unit, in conjunction with the standard The RapidPro Power Unit is based on the same advanced
PS modules (p. 585) or customer-specific modules, lets you architecture as the RapidPro SC Unit (p. 577). The main
adapt many different types of actuators (for example, drives, difference is that the power unit is designed to support
injectors, valves, relays, ohmic loads) to specific prototyping high current signals for driving actuators. The carrier board
systems. offers space for up to six power stage modules (p. 585),
with or without current feedback. Each RapidPro Power
Unit can have up to 48 power driver channels. The whole
Hardware
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. dSPACE‘s
ConfigurationDesk (p. 48) provides easy configuration of
the unit and extensive diagnostics handling.
Engineering
579
2016

Technical Details
General 6 slots for configurable power stage modules (PS modules) (p. 585)


Up to 48 power stage channels per power unit

Unit Connection Bus for use with RapidPro Control Unit (p. 582)

USB interface for communication with host PC

SPI interface for diagnostics with MicroAutoBox



Enable/disable input to switch all outputs of a unit on or off

Defined “powered-off” state during initialization and booting

Software support Configuration Configuration of the PS modules from a host PC via ConfigurationDesk (p. 48)


Interactive diagnostics feedback to the model via RTI blockset (p. 575)

Electrical Power supply +6 ... +60 V DC

characteristics Load dump protection up to +100 V

Reverse voltage protection up to -100 V

Mechanical Enclosure Aluminum enclosure with cooling fins (no fan)

characteristics Advanced mechanical concept with special coulter clips for easy installation and module locking



(with cover and base plate)

(without cover and base plate)
Environmental Ambient temperature -40 ... +85 ºC (-40 … +185 ºF)

characteristics
Vibration resistance1) EN 60068-2-6 Test conditions: n
Swept sine, 1 octave per minute, 3-axis test

Operating

ISO 16750-3:2007 / 4.1.2.4 Test IV n Test conditions: n Broadband noise, 2 h per axis / 3 spatial axes
RMS acceleration: 27.8 m/s2

Operating

Shock resistance1) EN 60068-2-27 Test conditions: n
n Acceleration: 15 g/11 ms; 100 g/5 ms
n Operating
ISO 16750-3:2007 / 4.2.2 Test conditions: n


Operating

1)
Order Information

RapidPro Power Unit RAPIDPRO_1651 (please inquire)

580
2016

Introduction


Optional Real-Time Interface (RTI), (p. 56) RTI

Application Fields
Required PS Modules See p. 585
If the DS1664 2-channel direct injection driver module USB_CAB12 (USB PC to LEMO cable with galvanic

is used with RapidPro, electrically safe host PC interface isolation, 4.5 m)
cables (up to 300 V DC/ACRMS and 600 V peak) are Further cables: please inquire.

mandatory for all connected systems such as RapidPro,
MicroAutoBox, and DS1005. You must perform all the
safety precautions described in the documentation.
Optional RapidPro SC Unit (p. 577) RAPIDPRO_1621 (please inquire)

RapidPro Control Unit, MPC565-based (p. 582) RAPIDPRO_1601 (please inquire)

Front connectors for RapidPro Power Unit RPP_F1F2

Software
Rear connectors for RapidPro Power Unit RPP_R1R2


RapidPro Break-Out Box for Power Unit (p. 590); DS1688

2 x connection cable RapidPro Power Unit (F1/F2)
and BOB (F1/F2), 0.5 m

Hardware
Engineering
581
2016

RapidPro Hardware / RapidPro Control Unit with MPC565
RapidPro Control Unit with MPC565

Intelligent I/O subsystem for dSPACE prototyping systems
Highlights
MPC565 microcontroller module

Complex I/O signal generation and acquisition

Up to 6 signal conditioning modules

USB configuration interface

LVDS slave communication interface

Powerful FPGA

Application Areas
The MPC565-based RapidPro Control Unit can be used cations such as engine or vehicle dynamics control,
as an intelligent I/O subunit to provide existing proto- complex I/O tasks can be shifted from the prototyping
typing systems – such as MicroAutoBox or AutoBox (in- system to the RapidPro Control Unit. The RapidPro Control
cluding the DS1005 PPC Board or the DS1007 PPP Pro- Unit also provides space for signal conditioning modules,
cessor Board and the DS4121 ECU Interface Board) – so that different sensors can be adapted to a specific
with additional I/O functionality. For example, in appli- prototyping system.
Key Benefits
The MPC565-based RapidPro Control Unit is based on Control Unit can be used separately or in combination with
the same architecture as the RapidPro SC Unit (p. 577). the other units to build an intelligent I/O subsystem tailored
Additionally, the RapidPro Control Unit is equipped with to a particular application. An integrated Unit Connection
a powerful microcontroller module, including an MPC565 Bus allows you to connect several RapidPro SC or Power
microcontroller, which is dedicated to handling complex I/O Units directly to the Control Unit without external wiring.
tasks. The carrier board provides space for up to six signal Efficient configuration of a single control unit or a stack
conditioning modules (SC modules, p. 585) and two com- and diagnostics handling are provided by ConfigurationDesk
munication (COM) modules. The signal conditioning modules (p. 48) via the USB configuration interface connected to
are the same modules as for the SC Unit. The USB configura- the host PC. Interactive diagnostics with feedback to the
tion interface module is used for communication with the model can be performed with the RTI RapidPro Control Unit
host PC. The LVDS slave interface module enables high- Blockset (p. 575). This blockset also provides extensive stan-
speed communication with dSPACE prototyping systems dard I/O functionalities such as PWM, bit I/O, A/D and special
(MicroAutoBox or DS1005 or DS1007 via DS4121). The RapidPro functionalities for engine, chassis and drives control.
582
2016

Introduction
Technical Details
General 6 slots for configurable, analog or digital signal conditioning modules (SC modules) (p. 585)


2 slots for communication interface modules (USB configuration interface module,

Application Fields
LVDS slave interface module)
Unit Connection Bus to expand RapidPro Control Unit with several RapidPro Power

and/or SC Units


Power management, sleep, and wake-up via prototyping system

Support of table-based algorithm for wider coverage of crank/cam wheel architectures, e.g.,

asynchronous crank wheels for 3-cylinder engines
Support of crank speed sensors with rotation detection for start/stop development

Microcontroller module MPC565, 56 MHz

4 MB external SRAM, 16 MB external flash

Onboard FPGA for additional functionality

48-channel time processing unit (TPU)

Software
40-channel bit I/O

22-channel multi I/O timer (MIOS)

2 queued A/D converters with internal sample/hold

40 A/D converter channels (10-bit resolution, 4 µs conversion time per channel)

Software support Configuration Configuration of connected units and modules from a host PC via ConfigurationDesk (p. 48)


Interactive diagnostics feedback to the model via RTI RapidPro Control Unit Blockset (p. 575)

I/O Real-Time Interface RTI RapidPro Control Unit Blockset (p. 575)

Electrical characteristics Power supply +6 ... +60 V DC

Load dump protection up to +100 V

Hardware
Voltage reverse protection up to -100 V

Mechanical characteristics Enclosure Aluminum enclosure with cooling fins (no fan)

Advanced mechanical concept with special coulter clips for easy installation and module locking



(with cover and base plate)

(without cover and base plate)
Environmental Ambient temperature -40 ... +85 ºC (-40 ... +185 ºF)

characteristics
Engineering
Vibration resistance1) EN 60068-2-6 Test conditions: n Swept sine, 1 octave per minute, 3-axis test


Operating

ISO 16750-3:2007 / 4.1.2.4 Test conditions: n Broadband noise, 2 h per axis / 3 spatial axes
Test IV RMS acceleration: 27.8 m/s2
Operating
Shock resistance1) EN 60068-2-27 Test conditions: n Shock direction: six spatial directions
Acceleration: 15 g/11 ms; 100 g/5 ms
Operating
ISO 16750-3:2007 / 4.2.2 n Test conditions: n Shock direction: six spatial directions


Operating

1)
583
2016

Order Information

RapidPro Control Unit with MPC565 RAPIDPRO_1601 (please inquire)

Stack: RAPIDPRO_1601/1651

RapidPro Control Unit with MPC565 plus RapidPro Power Unit
Stack: RAPIDPRO_1601/1621/1651

RapidPro Control Unit with MPC565 plus RapidPro SC Unit plus RapidPro Power Unit


Real-Time Interface (RTI), (p. 56) RTI

RTI RapidPro Control Unit Blockset (p. 575) RTIRAPIDPRO_BS


Required SC Modules See p. 585
If the DS1664 2-channel direct injection driver module USB_CAB12 (USB PC to LEMO cable with galvanic

is used with RapidPro, electrically safe host PC interface isolation, 4.5 m)
cables (up to 300 V DC/ACRMS and 600 V peak) are Further cables: please inquire.

mandatory for all connected systems such as RapidPro,
MicroAutoBox, and DS1005. You must perform all the
safety precautions described in the documentation.
Optional RapidPro SC Unit (p. 577) RAPIDPRO_1621 (please inquire)

RapidPro Power Unit (p. 579) RAPIDPRO_1651 (please inquire)

Front connector1 for RapidPro Control Unit RPC_F1

Front connector2 for RapidPro Control Unit RPC_F2


RapidPro Break-Out Box for Control Unit (p. 590); DS1689

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

LVDS-Link cable LEMO-1S to ZIF crimp contacts, 5 m, 60 °C LVDS_CAB1
LVDS-Link cable LEMO-1S to LEMO-1S, 5 m, 60 °C LVDS_CAB2



LVDS-Link cable LEMO-1S to ZIF crimp contacts, 1 m, 60 °C LVDS_CAB9
584
2016

RapidPro Hardware / RapidPro SC/PS Modules
RapidPro SC/PS Modules
Introduction
Mountable signal conditioning and power stage modules for RapidPro units
Highlights
Application Fields
Hardware- and software-configurable standard modules
Easy to mount on RapidPro units

Safe locking of modules on RapidPro units

Signal conditioning and power stage functionality

Software
Application Areas Standard Modules and Custom Modules
The RapidPro signal conditioning (SC) and power stage Besides the standard modules described in the following
(PS) modules bring vital signal conditioning and power tables (p. 586 – p. 589), dSPACE also offers you engineer-
stage functionality to the RapidPro units. The SC modules ing services to develop individual signal conditioning and
can be installed in the RapidPro SC Unit and the RapidPro power stage modules for your specific application scenario.
Control Unit. The PS modules are installed in the RapidPro
Power Unit.
Hardware
Key Benefits
A wide choice of hardware- and software-configurable units are automotive-protected and can be locked safely
modules is available that provide standard solutions in many on the carrier boards with coulter clips. This makes them
different applications. Installing and removing the modules suitable for in-vehicle applications. Modules are not limited
is easy, so the RapidPro units can be reused efficiently in in size. If complex electronic circuits require more space or
different projects. Customer-specific modules will also be pins than a single slot module offers, modules with other
Engineering
available on request. All the modules used with the RapidPro form factors can be used.
585
2016

Signal Conditioning (SC) Modules
Signal Conditioning
Description Order Number
Module (SC Module)
SC-SENS 4/1 4-channel sensor supply module
DS1626

Requires 1 slot in a RapidPro unit

Software-adjustable voltage range: 2 V ... 20 V, adjustable in steps of 5.5 mV

Output power: 1.2 W per channel

Fully isolated outputs

Thermal overcurrent protection

Accuracy 1%

SC-AI 4/1 4-channel differential analog input module
DS1631


Software-adjustable input range: ±100 mV ... ±50 V

Output range: 0 ... 5 V, ±5 V, 0 ...10 V, ±10 V, software-adjustable globally for all four channels

Four software-selectable 1st order low-pass filters (per channel). Cutoff frequencies: 10 Hz, 50 Hz, 100 Hz, 1 kHz

Input circuit: up to 4 hardware-configurable devices per channel, for example, pull-up, pull-down

SC-AI 10/1 10-channel analog input module
DS1633

Requires 2 slots in a RapidPro unit

Double size module (requires two slots)

Onboard sensor supply: 5 V, 1 W

External supply input

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 8-channel digital input module
DS1642


Software-adjustable comparator threshold and hysteresis voltage, software-adjustable in a range of ±39.5 V

Input voltage range: up to ±55 V continuous

Input circuit: up to 3 hardware-configurable devices per channel, for example, pull-up, pull-down

SC-DO 8/1 8-channel digital output module

DS1646


Open collector output

Output current: each channel 1 A, total permissible current for all channels: 1 A

Output voltage: 40 V

Fully isolated outputs of one module (one common ground)

Overcurrent protection

SC-CCDI 6/1 Crankshaft/camshaft sensor input module
DS1637


Connection of rotational speed sensors with open load voltage up to ±200 V (±60 V DC)

4 inputs for cam sensors with common ground

SC-EGOS 2/1 2-channel, exhaust gas oxygen sensor module for connecting Bosch LSU4.2, LSU4.9 or LSU ADV broadband
DS1634

lambda probes

Based on Bosch ASIC CJ125

Lambda measurement range: 0.65 ... ∞ and 0.75 ... ∞ (software-configurable)

Pump reference current: 0 ... 150 μA (software-configurable in 10 μA steps)

SC-KNOCK 4/1 4-channel knock sensor module
DS1635


Based on Bosch ASIC CC196 (with on-board DSP)

SC-TC 8/1 8-channel thermocouple sensor input module
DS1638


Suitable for type J and K thermocouples

One 24-bit A/D converter per channel, sampling rate for each converter (software-configurable) 0.1 Hz ... 50 Hz

Splitter cable (available as J or K variant) plus memory identifying the connected thermocable and thermocouples

High-precision cold junction compensation

586
2016

Introduction
Signal Conditioning
Module (SC Module)
SC-UHEGO 2/1 2-channel exhaust gas oxygen sensor module
DS1639

For integrating DENSO broadband lambda probes (PLUS2.1, PLUS3.x, PLUS5.0, PLUS5.1) into a function

prototyping setup
Application Fields

Based on DENSO ASIC technology

Air-fuel ratio measurement range: software-configurable, wide range: AFR 10 … ∞, stoichiometric range:

AFR 12 … 25
SC-DO 8/2 8-channel digital out module with push-pull functionality
DS1647


Configurable output stage: push-pull, low-side driver, high-side driver

Enables fast control of digital circuitry (e.g. dashboard applications, external power stages for electrical drives)

Tri-state capability during shutdown and idle state of the real-time application

Low-side driver mode for driving loads (e.g. relays)

Parallel channel operation for increased current capability

Routing compatible with SC-DO 8/1 (DS1646)

Software
Power Stage (PS) Modules
Power Stage Module

(PS Module)
PS-FBD 2/1 2-channel full-bridge driver module
DS1661


Each driver 5 A continuous, 7 A peak (depends on the Power Unit the module is mounted in)

Maximum supply voltage: 40 V continuous, 45 V peak (0.5 sec)

Hardware
Usable as: full-bridge, half-bridge, low or high side driver

Software adjustable current limitation and switch-off time

High-side rise time: 1.8 μs typ., 3.5 μs max.,

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.
Detailed load failure diagnosis

Current measurement with software adjustable filters (2nd order) on both channels

Overload protection, overtemperature protection, short-circuit protection to ground, UBAT and across the load

Integrated on carrier board: load dump protection up to +100 V, reverse voltage protection up to -100 V

PS-LSD 6/1 6-channel low-side driver module
DS1662

Engineering

4 output channels with up to 5 A (hardware-configurable)

2 output channels with up to 1 A

Max. supply voltage: 37 V continuous

Clamping voltage: 45 V or 70 V (depending on hardware configuration)

Switching time: <10 µs


Current measurement with hardware-adjustable low-pass filter (1st order) on channel 1 and 2

Overload protection, overtemperature protection, short-circuit protection to ground, active output clamping

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
587
2016

Power Stage Module

(PS Module)
PS-HSD 6/1 6-channel high-side driver module
DS1663


4 output channels with up to 5 A, clamping voltage 48 V

2 output channels with up to 1 A, clamping voltage 63 V

Max. supply voltage: 36 V continuous, 40 V peak

Switching time: <30 µs

Load failure diagnosis

Current measurement with hardware-adjustable low-pass filter (1st order) on channel 1 and 2

Overload protection, overtemperature protection, short-circuit protection to ground, VBAT and across the load,

active output clamping
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 1-channel high-current full bridge driver module
DS1667


Up to 60 A DC peak current (1 s), 42 A rms continuous (Tambient= 25 °C, filter frequency 1 kHz, corresponding

duty cycle)
Up to 60 A DC peak current (1 s), 29 A rms continuous (depends on ambient temperature)

Max. supply voltage: <20 V continuous

Current measurement with hardware-adjustable low-pass filter (1st order)

Internal free-wheeling diodes

Protection against: short circuit, overtemperature, and overvoltage

Load failure diagnostics

PS-HCHBD 2/1 2-channel, high-current, half-bridge driver module
DS1668


Each channel up to 30 A peak current (1 s), 25 A rms continuous (depends on ambient temperature)

Parallel mode possible (30 A DC peak per channel, 19 A rms continuous per channel)

Usable as half-bridge or low-side or high-side driver output

Max. supply voltage: <20 V continuous

Current measurement with hardware-adjustable low-pass filter (1st order) for each channel

Internal free-wheeling diodes

Protection against short circuit, overtemperature, and overvoltage

Load failure diagnostics

PS-DINJ 2/11) 2-channel direct-injection driver module
DS1664


Single or double injector operation mode (two injectors of the same bank cannot be driven at the same time)

Booster voltage U max: 100 V1)

I max: 30 A peak, 15 A continuous

Control of start injection

Software-adjustable booster voltage

Software-adjustable injection duration (peak and hold times)

Software-adjustable peak current (upper and lower values), subpulse A and B available for Use Scenario B

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
1)
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.
588
2016

Introduction
Power Stage Module
(PS Module)
PS-HCFBD 1/2 1-channel high-current full-bridge driver module for 12 V and 24 V applications
DS1767


Suitable for Use Scenarios A and B (p. 570, p. 571)
Application Fields

Support of DC motors and stepper motors

Up to 60 A DC peak current (1 s), 42 A rms continuous (depends on ambient temperature)

Max. supply voltage: 30 V

Current measurement with software-configurable low-pass filter (1st order/2nd order)


PS-HCHBD 2/2 2-channel, high-current, half-bridge driver module for 12 V and 24 V applications
DS1768


Suitable for Use Scenarios A and B (p. 570, p. 571)

Each channel up to 60A peak current (1 s), 42 A rms continuous per channel (depends on ambient

temperature, electric drive mode)
Electrical drive mode: Control of
three-phase electrical motors (BLDC motors and synchronous motors).
Requires two PS-HCHBD 2/2 modules in the same Power Unit and includes a brake chopper for conversion
Software
of breaking energy into heat
General purpose mode for controlling high current actuators (e.g. valves, resistive loads) (up to 30 A peak

current. 19 A rms current)
Each channel up to 30 A peak current per channel (1 s), 19 A rms continuous per channel (depends on

ambient temperature)
Output stages in the general purpose mode configurable as half-bridge, low-side or high-side driver

Max. supply voltage: 30 V

Current measurement with software-configurable low-pass filter (1st order/2nd order)


Optional: RP-HC-CAB1 cable for connecting external loads such as three-phase electric motors

For more detailed information, please contact dSPACE. Further signal conditioning modules are under development. Please let us know about
Hardware
your requirements for future modules.
Engineering
589
2016

RapidPro Hardware / RapidPro BreakOut Boxes
RapidPro BreakOut Boxes1)

Desktop connection panels for RapidPro systems
Highlights
Fast and flexible sensor and actuator connection

Checking and reconnecting signals without changing

an existing cable harness
Key Benefits
With the RapidPro Break-Out Boxes, you can connect conditioning, power stages and intelligent I/O subsystems
sensors and actuators to RapidPro units flexibly and see with RapidPro units in combination with dSPACE prototyping
at a glance which signals are connected, including their systems. Each RapidPro Break-Out Box provides a number
statuses. You can also reconnect signals without changing of multicolor LEDs, one LED per signal. The LEDs indicate
an existing cable harness. This makes the RapidPro Break- different voltage ranges and the signals by different colors.
Out Boxes an important accessory in setting up signal
Rotary switch:
Labeled terminals Multicolor LEDs voltage level adaption
Female I/O Male I/O

connectors connectors
to RapidPro to sensors/
units actuators
Terminal points Knife disconnectors Slide switch to

turn LEDs on/off
1)
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!
590
2016

RapidPro Hardware / RapidPro Break-Out Boxes
Introduction
Technical Details
General Three variants for different RapidPro units:

DS1687 for SC Unit, DS1688 for Power Unit, DS1689 for Control Unit
I/O connectors a) for connection to RapidPro units and b) for connection to an existing

cable harness
Each Break-Out Box provides the same number of terminals as the connected unit: up to

6 terminal points for each signal. There are knife disconnectors to interrupt the signal path.
Application Fields
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 +6 ... +60 V DC

MINI® Fuse (blade type automotive fuse):

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)
Load dump protection up to +100 V

Reverse voltage protection up to -100 V

Mechanical characteristics Physical size 356 x 224 x 50 mm (14 x 8.8 x 1.95 in)

Environmental Ambient temperature 0 ... +70 ºC (+32 ... +158 ºF)

characteristics
Software
Order Information

RapidPro Break-Out Box for SC Unit; 2 x connection cable RapidPro SC Unit (F1/F2) and BOB DS1687

(F1/F2), 0.5 m
RapidPro Break-Out Box for Power Unit, 2 x connection cable RapidPro Power Unit (F1/F2) DS1688

and BOB (F1/F2), 0.5 m
Hardware
RapidPro Break-Out Box for Control Unit, 1 x connection cable between RapidPro Control Unit DS1689

(F1) and BOB (F1), 0.5 m; 1 x connection cable between RapidPro Control Unit (F2) and BOB
(F2), 0.5 m


Engineering
Required RapidPro unit with corresponding SC/PS modules See p. 576
591
2016

ECU Interface Hardware / USB to CAN Converter DCI-CAN1
USB to CAN Converter DCI-CAN11)

Robust and compact USB-to-CAN gateway
Highlights
 Robust design for in-vehicle use
 Integrated optoisolation and high-speed transceiver
 API for easy integration in custom applications

 Measurement of ECU internal variables, ECU The Controller Area Network (CAN) is an established stan-
calibration, diagnostics and ECU flash programming via dard in the automotive industry to exchange data between
CCP2), XCP3) on CAN, KWP20004) or UDS5) on CAN, for electronic control units. The DCI-CAN1 provides a robust,
example. compact interface to the CAN bus via a Plug & Play USB
 Measurement of physical quantities like temperature, connection, and features integrated optoisolation and a
pressure and voltages via CAN-based I/O modules high-speed transceiver. The DCI-CAN1 is powered directly
 Monitoring the data stream on the CAN bus in via USB, so no additional components are necessary to con-
ControlDesk® Next Generation nect to the CAN bus.
 Transmitting messages via the CAN bus
Host PC
ECU with CCP
or XCP on CAN
or diagnostic protocols
Connection scenario using a DCI-CAN1.
1)
The end of life of the DCI-CAN1 is planned for 31.12.2020. You can still buy the product until 31.12.2017. New releases of
dSPACE software are guaranteed to continue supporting the DCI-CAN1 until at least the end of 2019. After the end of life, no
services of any kind will be available for this product. For new projects we recommend that you use the successor, the DCI-CAN2
(p. 594, planned availability: March 2016). For general information on the dSPACE product life cycle, please see p. 617.
2)
CAN Calibration Protocol
592 3)
Universal Measurement and Calibration Protocol
2016 4)
Keyword Protocol 2000
5)
Unified Diagnostic Services

ECU Interface Hardware / USB to CAN Converter DCI-CAN1
Introduction
Technical Details
General NXP CAN transceiver SJA1000 (clock rate: 16 MHz)

High-speed CAN transceiver 82C251

Baud rates up to 1 Mbit/s

Supports CAN specification 2.0A and 2.0B (11- and 29-bit identifiers)

Time-stamping – all measured or monitored data is sent to ControlDesk® Next Generation

with time stamps (resolution 50 µs)
Application Fields
Complies with European directives 73/23/ECC (Low Voltage Directive) and 89/336/ECC

(Electromagnetic Compatibility Directive)
Host interface USB

Software configuration Configuration of the DCI-CAN1 from host PC with ControlDesk® Next Generation or with dSPACE CAN API

Physical Enclosure Robust aluminum box

characteristics Connectors 9-pin, male Sub-D connector for connection to CAN (according to CiA-DS 102-1)

A-type USB connector with 1.5 m (5 ft) cable for connection to the host PC

Status LED Off: CAN inactive/not connected

On: CAN active

Flashing: bus traffic


Software
Approx. weight 150 g (0.33 lb.)

Temperature range -40 ... 85 °C (-40 ... 185 °F) ambient temperature

-65 ... 125 °C (-85 ... 257 °F) storage temperature

IP protection class IP 54

Electrical Power supply Power consumption max. 600 mW supplied by USB

characteristics Galvanic isolation up to 50 V (connector maximum) via optoisolation

Power consumption < 600 mW supplied by USB

Galvanic isolation Up to 50 V (connector maximum) via optoisolation

Hardware
Order Information

USB to CAN Converter DCI-CAN1 1) DCI_CAN1

For new projects it is recommend to use the DCI-CAN2 (p. 594), which is the successor of the DCI-CAN1 and has extended capabilities such
1)
as support of CAN FD.
dSPACE CAN API and CAN Driver
Application Areas Key Features Engineering

The API allows custom applications to be built in Python (API Supports multiapplication: several applications can connect to the same CAN channel

available as a Python module) or Microsoft® Visual C++ 6.0 Supports multiclient: the same application can connect to one or more CAN channels

(API available as a functional WIN32 DLL). For supported 2 virtual CAN channels for testing your application without using the hardware

operating systems (API, driver) see Up to 16 CAN channels accessible

www.dspace.com/goto?os_compatibility Provided along with the DCI-CAN1 and dSPACE Release

593
2016

ECU Interface Hardware / USB to CAN/CAN FD Converter DCICAN2
NEW: USB to CAN/CAN FD Converter DCICAN2 1)

Robust and compact USBtoCAN/CAN FD gateway
Highlights
Connects a CAN or CAN FD network to the host PC

Robust design for in-vehicle use

API for easy integration in custom applications


With the DCI-CAN2 you can access the data stream on CAN Compared with the classic CAN protocol, CAN FD (FD =
and CAN FD networks. The interface transfers messages flexible data rate) comes with increased data rates and
between the CAN/CAN FD network and the host PC via the payload data length. With CAN FD, a multiplied data rate
universal serial bus (USB). The DCI-CAN2 is powered di- allows an average data transmission speed of several Mbit/s
rectly via USB, so no additional components are necessary and payload lengths of up to 64 bytes (compared to 8 bytes
to connect to the CAN bus. in a classic CAN).
Host PC
ECU with CCP
or XCP on CAN
or diagnostic protocols
Connection scenario using a DCICAN2.
1)
Planned availability: March 2016
594
2016

ECU Interface Hardware / USB to CAN/CAN FD Converter DCI-CAN2
Introduction
Technical Details
General NXP CAN transceiver TJA 1044GT

CAN FD 1.0 (compatible with CAN 2.0 A/B)

Transmission standards: CAN/CAN FD (ISO 11898-1) & CAN FD (NON-ISO v1.0)

Arbitration bitrate: 25 kbit/s ... 1 Mbit/s; CAN-FD data field: 25 kbit/s ... 12 Mbit/s

Host interface USB 2.0 (high-speed)

Software configuration Configuration of the DCI-CAN2 from host PC with ControlDesk® Next Generation or with dSPACE CAN API
Application Fields


characteristics Connectors 9-pin, male Sub-D connector for connection to CAN (according to CiA-DS 102-1)

A-type USB connector with 1.5 m (59.0 in) cable for connection to the host PC

Status LED Green (lit): connection to operating system driver is established

Green (blinking slowly): software application is connected to the interface

Green (blinking quickly): CAN data is transmitted

Red (blinking): error during CAN data transmission

Orange (blinking quickly): identification of an interface when multiple interfaces are connected


Approx. weight 150 g (0.33 lb.)

Temperature range -40 ... 85 °C (-40 ... 185 °F) ambient temperature

Software
-40 ... 100 °C (-40 ... 212 °F) storage temperature

IP protection class IP 20

Electromagnetic compatibility EN 55024: 2011-09

EN 55022: 2011-12

EC directive 2004/108/EG

Electrical Power supply Power supply via USB

characteristics +5 V DC, max. 170 mA

Galvanic isolation Up to 500 V (connector maximum)

Hardware
Order Information

USB to CAN/CAN FD Converter DCI-CAN2 DCI_CAN2

dSPACE CAN API and CAN Driver
Engineering
Application Areas Key Features
The API allows custom applications to be built in Python (API Supports multiapplication: several applications can connect to the same CAN channel

available as a Python module) or Microsoft® Visual C++ 6.0 Supports multiclient: the same application can connect to one or more CAN channels

(API available as a functional WIN32 DLL). For supported 2 virtual CAN channels for testing your application without using the hardware

operating systems (API, driver) see Up to 16 CAN channels accessible

www.dspace.com/goto?os_compatibility Provided along with the DCI-CAN2 and dSPACE Release

595
2016

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

Integrated optoisolation

Supports 12 V and 24 V power supply networks in

the vehicle

The DCI-KLine1 is used with ControlDesk® Next Generation The DCI-KLine1 comes in the same reliable, robust and
to access electronic control units via KWP2000 on K-Line compact casing as the DCI-CAN1. Plug & play capabilities
(ISO14230). ECUs providing single-wire K-Line communica- via USB provide a quick connection to the host PC. The
tion and a fast initialization wake-up pattern (WuP) are DCI-KLine1 can be used for ECU diagnostics in passenger
supported. ECU diagnostics and ECU flash programming cars and commercial vehicles with 12 V and 24 V power
can both be done via the DCI-KLine1. supply networks. The integrated optoisolation of the DCI-
KLine1 avoids ground loops.
USB K-Line
DCI-KLine1 ECU with

KWP2000 on K-Line
Connection scenario using the DCIKLine1 for ECU diagnostics and ECU flash programming.
596
2016

ECU Interface Hardware / USB to K-Line Interface DCI-KLine1
Introduction
Technical Details
General Support of fast initialization on K‑Line via hardware‑generated wake‑up pattern (WuP)

Baud rate range: 183 Bd … 115,2 kBd1) for communication

Support of standard PC baud rates according to ISO 14230 (9.6 kBd, 19.2 kBd, 38.4 kBd, 57.6 kBd,

115.2 kBd) and other specific baud rates
FT232BM USB-to-serial converter

Complies with European directives 73/23/ECC (Low-Voltage Directive) and 89/336/ECC (Electro

Application Fields
magnetic Compability Directive)
Host Interface USB

Software configuration Configuration of the DCI-KLine1 from host PC with ControlDesk® Next Generation


characteristics Connectors 4 mm female connectors for connection to the ECU and power supply: red (VBAT), black (GND),

green (K-Line)
A-type USB connector with 1.5 m (5 ft) cable for connection to the host PC

Status LED Off: USB not powered/not connected

On (yellow): USB not initialized, VBAT on

On (red): USB initialized, VBAT off

On (green): USB initialized, VBAT on

Flashing (green): K-Line traffic

Software
Physical size 16 x 55 x 84 mm (0.63 x 2.16 x 3.30 in)

Approx. weight 150 g (0.33 lb.)

Temperature range -40 … +85 °C (-40 … +185 °F) ambient temperature

-65 … +125 °C (-85 … +257 °F) storage temperature

Electrical Power supply Voltage range: 4 … 40 V

characteristics Overvoltage protection: ±60 V, including all possible wrong wirings of K-Line, GND, and VBAT

Power consumption < 100 mA (from USB)

40 mA max. (from VBAT)

Approx. 2 mA (from VBAT, in standby mode)

Galvanic isolation Up to 60 V DC (connector maximum) via optoisolation

Hardware
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 Information

DCI-KLine1 DCI_KLINE1

Engineering
Relevant Software

Required ControlDesk Next Generation (p. 120)
®
See p. 122

597
2016

ECU Interface Hardware / Generic Serial Interfaces
Generic Serial Interfaces1)

Function bypassing, measurement, ECU calibration and flash programming
Highlights
Very small communication latencies for bypassing and

high data throughput for measurement
Support of standardized XCP on Ethernet interface

Measurement and bypassing without ECU code

changes
Application Areas Differences Between the DCI-GSIs

The current trend for modern automotive microcontrollers Although both the DCI-GSI11) and the DCI-GSI2 are basi-
is towards higher levels of system integration, faster clock cally tailored for similar use cases, they differ in several
rates, increased on-chip RAM and flash memory, and more details: For example, the DCI-GSI2 provides an open and
comprehensive I/O functionality. In this context, on-chip standardized XCP on Ethernet interface for third-party tools
debug interfaces are becoming much more important for to connect to. In addition, the DCI-GSI2 features bypassing
ECU software development. without requiring any ECU source or HEX code changes,
dSPACE provides the generic serial interfaces DCI-GSI11) and and enables very high measurement data throughputs and
DCI-GSI2, which can be used for function bypassing, mea- extremely fast measurement rasters via GBit Ethernet.
surement, ECU calibration and flash programming. The For a detailed comparison of the DCI-GSI1 and DCI-GSI2,
broad range of available connector adapters lets you adapt see the table on p. 599.
the DCI-GSIs to individual electronic control units.
ECU ControlDesk
Next Generation
DCI-GSI2
XCP on Ethernet Ethernet
Vbat MicroAutoBox II with
integrated Ethernet switch
Example wiring scenario with DCIGSI2 for ECU calibration and measurement in parallel to bypass communication.
1)
The end of life of the DCI-GSI1 is planned for 31.12.2020. You can still buy the product until 31.12.2017. New releases of
dSPACE software are guaranteed to continue supporting the DCI-GSI1 until at least the end of 2019. After the end of life, no
598 services of any kind will be available for this product. For new projects we recommend that you use the successor, the DCI-GSI2.

Introduction
ControlDesk® Next Generation dSPACE AutoBox
for bypassing
Application Fields
Ethernet
USB LVDS
(Low-Voltage
Differential Signaling)
JTAG/Nexus,
ECU AUD or Example wiring scenario with DCIGSI1 for ECU
NBD, ...
DCI-GSI1 calibration and measurement (blue connection)
Installation inside or outside
the ECU enclosure plus function bypassing (green connections)
in parallel.
Software
Comparison of DCI-GSI2 and DCI-GSI1
Parameter DCI-GSI2 DCI-GSI1

Harness complexity Two connections in total (Ethernet, power supply)
Three connections in total (LVDS, USB, power

supply)
Size of enclosure 102.5 x 71 x 26.5 mm (4.04 x 2.80 x 1.04 inch)
102.5 x 71 x 21.4 mm (4.04 x 2.80 x 0.84 inch)

Temperature range 40 … +85 ºC (40 … +185 ºF) operating
40 … +85 ºC (40 … +185 ºF) operating

temperature (extended temperature range on request) temperature)
XCP on Ethernet (UDP/IP, TCP/IP), 1 GBit/s
Host interface for measurement and calibration USB 2.0, proprietary protocol

Hardware
Interface to prototyping system for function XCP on Ethernet (UDP/IP, TCP/IP), 1 GBit/s
LVDS, proprietary protocol

bypassing
Automatic detection of target microcontroller Yes
No

Parallel calibration, measurement and bypassing
Yes Yes

Maximum measurement data throughput > 50 Mbit/s1)
< 6 Mbit/s (via USB interface)

CPU load on ECU for rastersynchronous Very low (no changes to ECU code required)
Low (ECU service typically required)

measurement
Fastest measurement raster ≥ 100 kHz (measurement rasters ≤ 10 μs possible)
≤ 10 kHz (for measurement rasters ≥ 100 μs)

Support of address remapping and memory Unlimited
Limited

management units (MMUs)
Engineering
Data tracing of ECU memory Unlimited (trace mirror size up to 400 kB)
Limited

Bypassing without hooks in ECU software Yes (via data trace interface)
No

ECU calibration including working/reference Yes
Yes

page concept
Flash programming of braindead ECU Yes
Yes

1)
Depending on the debug interface type.
599
2016

Technical Details of DCI-GSI2

Host Interface XCP on Ethernet (100 Mbit/s, 1 GBit/s)

ECU Interface JTAG/OCDS and DAP/DAP2: Infineon´s TriCore families

DAP: Infineon XC2000

JTAG/Nexus: Freescale’s MPC55xx, MPC56xx and MPC57xx families

JTAG/Nexus: ST Microelectronics SPC56xx and SPC57xx families

JTAG/Nexus: Renesas V850E2 and RH850 family

For further interfaces, please contact dSPACE.
Connectors Connector to on-chip debug bus:

Various connector adapters are available from dSPACE. Some adapters also have a tool connector

for connecting an additional tool such as a debugger.
Ethernet connector:

8‑pin connector for connection to the host PC and/or the bypass system

Power connectors (only one power connector can be used at the same time):

2‑pin LEMO power connector on the DCI-GSI2 enclosure for connection to an external power supply

Internal power connector in the DCI-GSI2 for connection to the vehicle power supply in the ECU

via the internal power supply cable
Physical Enclosure Aluminum box (to be ordered separately)

characteristics Size DCI-GSI2 with aluminium box: 102.5 x 71 x 26.5 mm (4.04 x 2.8 x 1.04 in)

DCI-GSI2 without aluminium box: 70.05 x 62.4 x 10.5 mm (2.76 x 2.46 x 0.41 in)

Weight DCI-GSI2 with aluminium box: approx. 220 g (0.49 lb.)

(without connector adapter) DCI-GSI2 without aluminium box: approx. 28 g (0.06 lb.)

Temperature range -40 ... +85 ºC (-40 ... +185 ºF) operating temperature

-40 ... +105 °C (-40 ... +221 °F) operating temperature on request

-65 ... +125 ºC (-85 ... +257 ºF) storage temperature

Electrical Power supply 4.3 ... 30 V (38 V transient), extended range with power supply cable PWR_CAB9
n
characteristics Protection Protected against reverse battery up to -32 V
n
Power consumption 1)
4 W typ. at room temperature, 12 V, and 1 GBit/s Ethernet. Using 100 Mbit/s Ethernet instead of
n
1 GBit/s saves about 0.7 W
30 mW typ. in standby mode
n
If JTAG/Nexus with MPC5xxx microcontroller is used.
1)
600
2016

Introduction
Order Information

Generic Serial Interface DCI-GSI2 DCI_GSI2

Application Fields
Relevant Hardware

Optional Enclosure for in-vehicle use
DCI_GSI2_ENC1

Enclosure for laboratory use
DCI_GSI2_ENC2

Microcontroller-specific connector adapters
Please inquire

Ethernet Connection Cable (e.g., to connect the DCI-GSI2 to the host PC)
ETH_CAB1

Ethernet Connection Cable (e.g., to connect a DCI-GSI2 to a MicroAutoBox II)
ETH_CAB3

Ethernet Connection Cable (e.g., to connect the MicroAutoBox II to the host PC);
ETH_CAB4

length 10 m
Software
Power Supply Cable for DCI-GSI1/GSI2 with galvanic Isolation
PWR_CAB9

Hardware
Engineering
601
2016

Technical Details of DCI-GSI11)

General 64 MB RAM for buffering measurement data

USB host interface for measurement and calibration

Low-voltage differential signaling (LVDS) bypass interface for connection to dSPACE prototyping hardware

Interface for connecting an additional tool to the ECU via its on-chip debug port

Offline check and display of allocation status of overlay RAM in ControlDesk® Next Generation

Quick-start measurement

ECU flash programming via dSPACE ECU Flash Programming Tool (p. 257)

Support of memory address relocation, for example, in connections with microcontrollers featuring

memory management units (MMUs)
ECU interface READI/Nexus: Freescale’s MPC56x family2)

AUD/AUD2: Renesas’ SH2 and SH2A family

NBD: Renesas’ V85x, Renesas’ M32R family and Toshiba TMP1984FDF

JTAG/OCDS: Infineon’s TriCore family

JTAG/H-UDI: Renesas’ SH2A and SH4A family

JTAG/SDI: Renesas’ M32R family

JTAG/Nexus: Freescale’s MPC55xx and MPC56xx family

Target/tool connector SAMTEC FOLC-125-01-S-Q-LC to interface individual connector adapters

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 Enclosure Aluminum box (to be ordered separately)

characteristics Protection classes IP 54 and IP66 on request

Size DCI-GSI1 with aluminum box: 102.5 x 71 x 21.4 mm (4.04 x 2.80 x 0.84 in)

DCI-GSI1 without aluminum box: 62.4 x 56 x 10.5 mm ( 2.46 x 2.21 x 0.41 in)

Weight DCI-GSI1 with aluminum box: approx. 214 g (0.47 lb.)

DCI-GSI1 without aluminum box: approx. 29 g (0.06 lb.)

Temperature range -40 ... +85 °C (-40 ... +185 °F) operating temperature

-65 ... +125 °C (-85 ... +257 °F) storage temperature

Electrical Power supply 6 V ... 48 V
n
characteristics Protection Protected against overvoltage
n
Load dump protection up to 60 V
n
Protected against reverse battery up to -60 V
n
Power consumption3) 2.3 W max., at room temperature and 12 V
n
12 mW typ. in standby mode
n
1)
The end of life of the DCI-GSI1 is planned for 31.12.2020. You can still buy the product until 31.12.2017. New releases of dSPACE software
are guaranteed to continue supporting the DCI-GSI1 until at least the end of 2019. After the end of life, no services of any kind will be available
for this product. For new projects we recommend that you use the successor, the DCI-GSI2. For general information on the dSPACE product
life cycle, please see p. 617.
2)
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.
602
2016

Introduction
Order Information

Generic Serial Interface DCI-GSI1 DCI_GSI1

Application Fields
Relevant Hardware

Optional Enclosure for DCI-GSI1
DCI_GSI1_ENC

Microcontroller-specific connector adapters
Please inquire

Accessory kit for DCI-GSI1
DCI_GSI1_C

Interface cable with optoisolation
USB_CAB4

PC connection cable
USB_CAB5

Power supply cable for DCI-GSI1 with galvanic isolation
PWR_CAB7

LVDS Link Cable (to connect MicroAutoBox and DCI-GSI1 or DPMEM PODs)
LVDS_CAB1

Software
LVDS Link Cable (to connect DS4121 and DCI-GSI1 or DPMEM PODs)
LVDS_CAB2

Hardware
Engineering
603
2016

ECU Interface Hardware / Additional ECU Interface Solutions
Additional ECU Interface Solutions

Customerspecific DPMEM PODs and onchip debugging interfaces
Highlights
Dedicated interfaces tailored for customer-specific

use cases
Solutions for a wide range of microcontrollers

already available
Reliable systems proven in several thousand

installations world-wide

When the external bypass method is used for rapid control From many years of experience with bypass interface
prototyping, there are often several possible ways of divert- development, dSPACE has a long list of well proven solutions
ing the flow of data from the ECU to the prototyping system to offer. You can also order a custom bypass interface,
and back. In cases where a dSPACE standard bypass interface precisely tailored to the microcontroller of your production
is not applicable, a customer-specific plug-on device (POD) ECU and your application.
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 recom-
mend you consult us on bypassing issues at an early project
stage, to gain maximum benefit from one of dSPACE’s
standard solutions and significantly reduce engineering
costs.
Bypass Interfaces Supported by dSPACE Including CustomerSpecific Solutions

Strategy Bypass Interface Solution
Bypassing via DPMEM POD Parallel interface Standard product, e.g., DS541 DPMEM POD for MPC55xx microcontrollers,

DS543 DPMEM POD for Freescale MPC56xx/STM SPC56x with VertiCal connector
Customized DPMEM POD

Bypassing via OnChipDebugging Serial interface Standard products: DCIGSI1 and DCIGSI2 (p. 598) for microcontrollers specified

Interface Customerspecific PODs or specific adaptations of the DCIGSI1 and DCIGSI2

Bypassing via XCP on CAN CAN interface Standard product: One CAN channel on ECU is used

Bypassing via CCP using CAN Standard product: One CAN channel on ECU is used

Bypassing via XCP on Ethernet Ethernet interface Standard product: LVDSEthernet Link Cable (LVDS_CAB13/14), DS1007 (p. 386)

(UDP/IP and TCP/IP) with integrated Ethernet interface, MicroAutoBox® II Ethernet I/O interface (p. 548)
Bypassing via XCP on FlexRay FlexRay interface Standard product: One FlexRay channel on ECU is used

604
2016

ECU Interface Hardware / Additional ECU Interface Solutions
Introduction
Partial List of CPUs and Bypass Interfaces
CPU Bypass Interface
Freescale 68HC11 Customer-specific: DPMEM POD



Freescale MPC563 Customer-specific: DPMEM POD

Freescale MPC555 Customer-specific: DPMEM POD

Application Fields
Freescale MPC56x Standard product: DCI-GSI1 (p. 570)

Freescale MPC55xx and MPC56xx Standard product: DPMEM POD DS541 and DS543 for VertiCal connector

Standard products: DCI-GSI1, DCI-GSI2 (p. 570)

Freescale MPC57xx Standard products: DCI-GSI2 (p. 570)

Standard product: DPMEM POD DS543 for VertiCal connector

Freescale DSP56F807 Customer-specific: DPMEM POD

Infineon Aurix TC27xx Standard product: DCI-GSI2

Infineon C167 Customer-specific: DPMEM POD

Infineon TriCore TC1775 Customer-specific: DPMEM POD

Infineon TriCore TC1766 , TC1796 Standard product: DCI-GSI1

Infineon TriCore TC1736, TC1767, TC1797 Standard products: DCI-GSI1, DCI-GSI2

Infineon TriCore TC1791, TC1793, TC1798 Standard product: DCI-GSI2

Software
Infineon XC2000 Standard product: DCI-GSI2

Renesas M32R Customer-specific: RTD IF POD

Standard product: DCI-GSI1

Renesas RH850 Standard product: DCI-GSI2

Renesas SH2/SH2A Customer-specific: NBD IF POD

Standard products: DCI-GSI1

Renesas V850 Customer-specific: NBD IF POD

Standard product: DCI-GSI1, DCI-GSI2

ST-Microelectronics SPC564A80 Standard products: DPMEM POD DS543 for VertiCal connector

ST-Microelectronics SPC56x Standard products: DPMEM POD DS543 for VertiCal connector

Hardware
ST-Microelectronics ST10-F280 Customer-specific: DPMEM POD

Toshiba R3900 Customer-specific: NBD IF POD

Freescale HCS12 Customer-specific: DPMEM POD

Texas Instruments TMS470 Customer-specific: DPMEM POD

Data, I/O
Interrupts, etc. and/or
standard
Control algorithm DPMEM DPMEM
Engineering
ECU
functions
Processor Board DS4121 Customer- Electronic Control

(DS1005 or DS1006) Specific POD Unit (ECU)
Bypassing via DPMEM POD: a customer-specific POD combined with the DS4121 ECU Interface Board (p. 436) provides a fast and safe
communication between your ECU and your prototyping system.
I/O
Control algorithm DPMEM and/or
or standard
ECU
Processor Board DPMEM functions
(DS1007)
Electronic Control
MicroAutoBox II Customer- Unit (ECU)
Specific POD
605
The DS1007 (p. 386) and the MicroAutoBox II (p. 548) offer standard Ethernet interfaces. 2016

Engineering
n dSPACE Engineering Services _____________ 608

Engineering / dSPACE Engineering Services
dSPACE Engineering Services

Dedicated assistance for all development phases
Highlights
Globally available engineering and consulting services

complementing dSPACE's product range
Custom hardware and software adaptations

Fast response

Experienced team of engineers

Local and global projects, from small projects to

complete turn-key solutions
Key Benefits
dSPACE systems are easy to get up and running – however, tion guarantee smooth and rapid project progress towards
if a project is more complex, if individual solutions are needed successful project completion. dSPACE engineering services
or if there is high time pressure, you can trust dSPACE's are provided worldwide by the dSPACE group companies:
fast, competent and reliable engineering and consulting dSPACE GmbH, represented by offices in Paderborn and
services. Experienced engineers support you with small- three project centers throughout Germany; and the local
scale project aid as well as with complete turn-key solu- dSPACE companies in Japan, the USA, the U.K, France,
tions. And dSPACE engineers can also help you on-site – and China. dSPACE engineering and consulting services are
even as residents. dSPACE's engineering services enable you available for every phase of development, so that you can
to quickly work independently with our tools and to acquire concentrate fully on your actual tasks. Moreover, dSPACE
the necessary product know-how from dSPACE's specialists. specialists provide standard training courses as well as cus-
For global projects, dSPACE's internationally networked tomer-specific courses, also on site if requested.
team of specialists as well as our central project coordina-
Typical Services (Examples) Description

Tool introduction 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 dSPACE supports you in optimizing your development processes and in combining dSPACE tools and

third-party tools efficiently in one single tool chain.
Turn-key solutions dSPACE Engineering Services offer complete ready-to-use solutions even for complex application scenarios.

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 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.
608
2016

Introduction
Overview of Engineering Services
System Architecture
Service (Examples) Details (Examples)

Integrating SystemDesk (p. 40) into
®
Custom integration with basic software configuration tools

Application Fields
customer-specific development processes Custom integration with TargetLink® (p. 202) and other behavior modeling tools

Adapting SystemDesk to customer-specific data management solutions

Migrating customer-specific architectures Importing legacy system and software information from non-AUTOSAR formats

Integrating non-AUTOSAR code

AUTOSAR support Support for introducing the AUTOSAR-compliant development of software architectures

Model analysis and advice Help in analyzing the efficiency, safety, and reusability of your models and modeling style

Assistance in creating and optimizing company-specific guidelines and in applying industry-proven standards

Tool automation Developing custom scripts (e.g., mapping of architecture elements based on naming conventions, connection

of software components based on customer rules)
Rapid Control Prototyping
Software
Custom solutions Custom I/O interfaces (e.g. FPGA-based I/O modules for DS5202/DS5203 FPGA boards or MicroAutoBox II)

Custom RTI blocksets

Modifying and designing signal conditioning and power stage modules for RapidPro hardware (p. 568)

Integrating third-party hardware and software

Turn-key prototyping systems Concept design

(from selective services to complete System configuration

turn-key systems) Signal list / wiring harness specification

Wiring harness assembly

Hardware
I/O model and system tests

On-site commissioning

Hands-on training

Bypassing ECU-specific configuration of dSPACE bypass services and integration into ECU source code

Development of ECU-specific plug-on devices and connector adapters for the dSPACE bypass interfaces DCI-

GSI1 and DCI-GSI2 (p. 598)
Development and customer-specific adaptation of ECU flash programming tools

Support for setting up HEX-code-based external and internal bypassing projects with the ECU Interface

Manager (p. 248)
Engineering
ECU Autocoding

Tool introduction Hands-on support during introduction of TargetLink (p. 202)

Support during evaluations and pilot projects

Custom TargetLink training

Integrating TargetLink into the Defining interfaces to other tools used in the project

customer’s development processes Defining project configurations (project template / TargetLink Data Dictionary)

Connecting to existing data bases, import/export of variable files (e.g., .xls, .m)

Linking the model and TargetLink Data Dictionary

Creating customer-specific utilities and scripts

Adapting documention generation or A2L file generation

Custom block libraries and/or I/O blocksets

Intregrating with SYNECT for central management of TargetLink models, model interfaces, and parameter sets

Integrating with SYNECT Test Management

609
2016

ECU Autocoding

Model analysis and advice Help
in analyzing your models and modeling style with regard to efficiency, safety, and reusability
Assistance
in creating and optimizing company-specific guidelines and in applying industry-proven
standards
AUTOSAR integration Support for developing and integrating AUTOSAR-compliant software components

ECU integration Support for integrating the generated code in the ECU’s software environment

Tool chain development and maintenance Specification and development of complete tool chains around TargetLink

Maintaining tool chains

Migration to new versions

Process consulting 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

Turn-key HIL systems Concept design, hardware planning, project management

(from selective services to complete turn-key Signal list / wiring harness specification

systems) 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)
Developing custom software (e.g., Simulink® and ConfigurationDesk® models)

Open- and closed-loop HIL system tests

HIL systems for applications such as testing complete hybrid powertrains, battery management, etc.

Implementing sensor and actuator models and protocols

Custom tools to manage the HIL system, e.g., for variant handling

Custom FPGA applications (e.g., e-drive models, special I/O functions) based on XSG library

On-site commissioning

Hands-on training

Resident engineers (see also "Test Management and Automation", p. 612)

Simulation models See table "Modeling" (p. 611)

Test management and automation See table "Test Management and Automation" (p. 612)

Process consulting Integrating HIL testing in the ECU development process and tool environment

Optimizing HIL testing activities by means of variant and workflow management

Partitioning between components, subsystems, and full-vehicle HIL simulators

Exchanging models and data between OEM and supplier

Consulting on HIL configuration management

610
2016

Introduction
Modeling

Model parameterization/calibration and Parameterizing and validating Automotive Simulation Models (ASM) (p. 258)

validation Parameterizing third-party models

Adapting models and model parameters for closed-loop HIL tests

Application Fields
Validating models against measurement data

Model integration Integrating ASM models, customer models, and third-party models into a HIL, MIL, or SIL environment

Integrating special maneuvers, roads, vehicles, etc. in the ASM Vehicle Dynamics and ASM Traffic

simulation environment
Combining the above models, for example, to create an entire virtual vehicle

Handling variants of models in a superset model

Model development and adaptation Developing and adapting model components, e.g., for ASM Engine (CNG engine, special injection

systems, truck components, etc.), ASM Vehicle Dynamics (vehicle configurations such as articulated bus
or wheel loader, active front steering, etc.), or drivetrain applications (electric vehicles, hybrid-electric
drivetrains, special differentials, etc.)
Developing custom import and export filters for parameterizations, road descriptions, etc.

Developing and adapting model components for customer models

Further support Closed-loop HIL, MIL, and SIL tests
Software

Integrating ASMs into your development process

On-site support and resident engineers for modeling tasks

Developing custom pre- and postprocessing tools

Special training classes for ASM users

Hardware
Engineering
611
2016

Test Management and Automation

AutomationDesk (p. 172) jump start Creating concepts for test scenarios and test cases

Implementing examples

Hands-on training

AutomationDesk customization and test Integrating AutomationDesk into your development and test process

automation engineering Tool connections, e.g., Microsoft® Excel®, Vector CANoe, Vector CANstress, and other third-party tools

Developing test automation frameworks according to your requirements (e.g., project and library

structure, test development process)
Developing import routines for third-party test formats

Implementing tests and test examples

Extending AutomationDesk with custom test steps and test libraries

Adapting automatic reports to your requirements

On-site services for tool support; resident engineers covering the whole test process

Test management and process support Setting up test processes from test specification to test results

Setting up a SYNECT-based environment for the central management of all test data

Integrating requirements management, test management and test automation

Test system maintenance

Project-specific training for your engineers

Consulting on test modeling in AutomationDesk for efficient use in SYNECT® Test Management (p. 294)

612
2016

Introduction
Virtual Validation

Tool introduction (VEOS , p. 112)
®
Customer-specific training, consulting and support


Integration of virtual validation into customer- Configuring and building virtual electronic control units based on Simulink® models or C-code

Application Fields
specific development processes Connecting several virtual electronic control units to form complex simulation systems

Designing, implementing and maintaining tool chain

Customer-specific tool chains and integration Developing customer-specific scripts (e.g., data exchange between several tools, creating and testing

simulation systems and virtual control units)
Tool connections, e.g., VEOS® (p. 112), TargetLink® (p. 202), SystemDesk® (p. 40), ConfigurationDesk®

(p. 48), ControlDesk® Next Generation (p. 120), or Simulink®, or other third-party tools
V-ECU on HIL systems Integrating V-ECUs into real-time simulations

Process support

Data Management
Software
Tool introduction (SYNECT , p. 292)
®
Customer-specific training, consulting and support


Process consulting and tool chain integration Integrating requirements management, test management and test execution

Optimizing testing activities through efficient variant handling

Integrating signal and parameter management from simulation to calibration

Optimizing signal and parameter management through efficient variant handling

Customizing SYNECT to match customer data

Integrating SYNECT data management with in-house tools

Consulting on test modeling in AutomationDesk for efficient use in SYNECT Test Management (p. 294)

Hardware
Consulting on model life cycle management and the use of SYNECT Model Management (p. 302)

Customizing model import and export

Support: An Integral Part of the Product Custom Training Courses

dSPACE offers high-quality technical support. When you Our specialists will provide a wealth of knowledge and
call us or use the support e-mail address or the form on our experience to get your project moving: in our regular,
website, your request is immediately forwarded to the right standard training courses, in special courses tailor-made
support, application, or development engineer. for you, and if you want, on site. The instructors are expe-
Engineering
rienced dSPACE engineers.
Support and Maintenance (p. 616)

www.dspace.com/go/trainings

613
2016

n Support: An Integral Part of the Product _____ 616
n Software Maintenance Service (SMS) _______ 616
n dSPACE Product Lifecycle Model __________ 617

Support and Maintenance / Support and Software Maintenance Service

Support: An Integral Part of the Product
We regularly receive feedback from customers saying they our support mail address, your request is immediately
are very satisfied with the quality and response time of our forwarded to the right support, application or development
support services. dSPACE offers high-quality technical sup- engineer. We regard support as an integral part of our
port for any technical problem. When you call us or use products.
If You Encounter a Problem

If you encounter a problem using dSPACE products,
please contact your local office:
dSPACE group companies: www.dspace.com/go/locations
Distributors: www.dspace.com/go/distributors
For countries not listed, please contact
dSPACE GmbH in Paderborn, Germany.
www.dspace.com/go/support
Tel.: +49 5251 1638-941
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) maxi- support, online support via WebExTM, and consultation with
mizes the value of your investment in dSPACE systems by senior staff from the dSPACE development departments
giving you access to regular software upgrades and when appropriate.
Premium Support. The service is available for an annual fee. For detailed information on the entire SMS offer and on the
For software products with SMS, you will automatically effective fees, please contact your local dSPACE office or
receive all upgrades and enhancements released during the your local distributor for dSPACE products:
maintenance period. These include the latest feature www.dspace.com/go/locations
innovations as well as compatibility with new MATLAB® www.dspace.com/go/distributors
releases. The dSPACE Software Maintenance Service includes For countries not listed, please contact dSPACE GmbH in
Premium Support, which gives you, for example, telephone Paderborn, Germany.
616
2016

Support and Maintenance / dSPACE Product Lifecycle Model
dSPACE Product Lifecycle Model
Introduction
Staying in Motion
Cutting-edge or even better: ahead of the times – this is
what we all expect from the latest development tools.
But our hearts often beat for well-known tools and processes
we are used to and which we have become comfortable
Application Fields
with over the years – even if we actually know that enabling
further innovation requires leaving some of the past behind.
This why the dSPACE products also run through a life cycle:
to create room for new innovations, to relieve engineers of
design restrictions or maintenance efforts from the past,
and to include the best of established tools in new tools.
The following dSPACE product lifecycle model gives you an
overview of the different product phases, explaining what
they include and offer.
Software
Product Lifecycle Model
Provided Services
Product Lifecycle Phase Description
Hardware Software
Hardware
Available The product is generally available and can be
Product revisions Product versions

(AVL) purchased (subject to patent or export Repairs
Hotfixes, patches, and Service Packs

conditions). Customer support services

Phased Out The end-of-life date for this product is set Product revisions
Product versions

(PHO) and communicated. The product can still be Repairs
Hotfixes, patches, and Service Packs

purchased (subject to patent or export
conditions). Customers are advised against
Customer support services

using the product in new projects.
Maintained Repairs
The product is no longer available and can not Product versions

(MAN) be purchased. Hotfixes, patches, and Service Packs

It is still maintained and supported.
Engineering
Customer support services

Retired The product is not available and cannot be Customer support services

(RET) purchased. It is not maintained anymore.
Individually Supported The product can be supported as part of an optional, fee-based individual agreement.
(ISU)
617
2016

Support and Maintenance / Use of dSPACE Products
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.
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 dSPACE’s production code generator TargetLink®, but not the actual code generated by TargetLink.
Safety measures
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.
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.
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 dSPACE’s 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.
618
2016

Support and Maintenance / Third-Party Brands and Product Names
Introduction
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:
Brand
names and product names are trademarks or registered trademarks of their respective companies or organizations.
Unless explicitly stated otherwise, mentioning third-party products does not imply any endorsement or recommendation of these products. The absence of a company
Application Fields

name or product name does not imply any evaluation.
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.
To purchase or get technical support for third-party products, please contact the third-party product vendor directly.
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.
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 infor-
mation in the Catalog. For information on these, please send your inquiry to info@dspace.de.
“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.
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®), Cohda Wireless (MK5-OBU), Comité Européen de Normalisation (CEN),
Software
Cosmic Software (Cosmic compilers), Delta Elektronika (SM15/100, SM35/45, P183), DENSO (PLUS2.1, PLUS3.x), Eberspächer (FlexCard Cyclone II, FlexCard Cyclone II
SE, FlexCard USB), Elektrobit (EB) (EB 61x0, EB Assist ADTF, tresos®, tresos Studio), Emerge-Engineering (MEDKit), ETAS (INCA), European Telecommunications Standards
Institute (ETSI), 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®), Global Navigation Satellite System (GNSS), Green Hills Software (Green Hills compil-
ers), HERE (HERE), 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), MathWorks® (MathWorks®, MATLAB®, Real-Time Workshop®,
SimPowerSystems™, Simulink®, Simulink® Coder™, Stateflow®, Stateflow Coder®), 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), National Marine Electronics Association (NMEA), NEC (V850FX3 CAN-IT), NXP
(82C251, SJA1000, TJA1054), Oracle® (Orade®), ParallelGraphics (Internet Scene Assembler), PikeTec (TPT), PTC® (Integrity), PushOk Software (SCC API plug-in), QNX®
Hardware
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), Toshiba (R3900, TMP1984FDF), TÜV SÜD (TÜV SÜD), Vector (CANalyzer, CANape, CANcard,
CANcase, CANoe, CANscope, CANstress, VN16xx series, VN5610, VN7600, VN89xx series, vTESTstudio), VIRES Simulationstechnologie (OpenDRIVE®), WebEx™ Com-
munications (WebEx™), Wind River (Wind River compilers), Xilinx® (ISE® Foundation, Kintex®-7, System Generator, Spartan®-3 XC3S4000, Spartan® 6, Virtex®, Vivado®).
Errors and omissions excepted.
Engineering
619
2016

© Copyright 2016 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 regis-
tered 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
Germany United Kingdom France

dSPACE GmbH dSPACE Ltd. dSPACE SARL
Rathenaustraße 26 Unit B7 . Beech House 7 Parc Burospace
33102 Paderborn Melbourn Science Park Route de Gisy
Tel.: +49 5251 1638-0 Melbourn 91573 Bièvres Cedex
Fax: +49 5251 16198-0 Hertfordshire . SG8 6HB Tel.: +33 169 355 060
info@dspace.de Tel.: +44 1763 269 020 Fax: +33 169 355 061
Fax: +44 1763 269 021 info@dspace.fr
info@dspace.co.uk
China Japan USA and Canada

dSPACE Mechatronic Control dSPACE Japan K.K. dSPACE Inc.
Technology (Shanghai) Co., Ltd. 10F Gotenyama Trust Tower 50131 Pontiac Trail
Unit 1101-1105, 11F/L 4-7-35 Kitashinagawa Wixom . MI 48393-2020
Middle Xizang Rd. 18 Shinagawa-ku Tel.: +1 248 295 4700
Harbour Ring Plaza Tokyo 140-0001 Fax: +1 248 295 2950
200001 Shanghai Tel.: +81 3 5798 5460 info@dspaceinc.com
Tel.: +86 21 6391 7666 Fax: +81 3 5798 5464
Fax: +86 21 6391 7445 info@dspace.jp
infochina@dspace.com
01/2016

DSPACE Catalog2016 E Web

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

DSPACE Catalog2016 E Web

Încărcat de

Drepturi de autor:

Formate disponibile

www.dspace.

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

dSPACE Locations Distributors

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

dSPACE Systems ___________________________________________________ 10

Automotive Industry ________________________________________________ 22

Experiment and Visualization Software _______________________________ 120

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

Platform API Package _______________________________________ 196

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

SCALEXIO® Hardware ______________________________________________ 318

DS4201 Prototyping Board ___________________________________ 440

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

DS5001 Digital Waveform Capture Board ______________________ 452

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

dSPACE Engineering Services _______________________________________ 608

Support and Maintenance 614

Safe Use of dSPACE Products 618

Important Information on Third-Party Brand Names

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

Embedded Control Development

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

SystemDesk® simplifies and speeds up the planning, implementation,

Rapid Control Prototyping

dSPACE prototyping systems are flexible development platforms that

Relevant products and product groups:

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

Automatic code generation for the production ECU is a key development

Relevant products and product groups:

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

The amount of data produced in electronics and software development

dSPACE systems are easy to get up and running. However, if a project

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

System Architecture Implementation Software Simulation Software

SystemDesk® ConfigurationDesk® RTI AUTOSAR Blockset VEOS®

RTI for Multiprocessor Systems dSPACE Ethernet Configuration

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

Automotive Simulation Data Management SCALEXIO® Hardware

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

DS4505, page 448

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

Modular Hardware I/O Boards (2) Accessories Simulator Hardware

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

RapidPro SC/PS Modules Generic Serial Interfaces

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

Well-Proven, Integrated Development Systems

A Diversity of Application Fields

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

Hybrid Drive (I) HIL

Drivetrain ECUs/ AUTOSAR-compliant

Electric Vehicle Developing

Active Seat Belts Pre-pretensioner

Steering Systems/ ISO-26262-compliant functional Validating electrically powered steering systems

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

Application Examples1) (2)

Video-based Driver Developing

Smart Adaptive Developing

AUTOSAR Software Developing AUTOSAR

Window Control Developing

dSPACE GmbH • Rathenaustraße 26 • 33102 Paderborn • Germany • info@dspace.de • www.dspace.com

ETSI ITS www.etsi.org

Simulating Satellite Simulating

Commercial & OffHighway Vehicles

Virtual Vehicle Test

Electric Wedge Validating

Permanent Magnet Real-time

dSPACE Systems (p. 10)

Safe Surgical Semiautomatic

Prosthetic Wrist Prosthetic

Miniature Robot Miniature

Intelligent Flying Unmanned

SystemDesk VECU Generation Module