Académique Documents
Professionnel Documents
Culture Documents
Platform Management
Important Notice
This document contains proprietary information that is protected by copyright. All rights
are reserved. The document may be printed for personal or internal use provided all the
proprietary markings are retained on all printed copies. In all other cases, the document
must not be copied, photocopied, reproduced, translated, or reduced to any electronic
medium or machine-readable form, in whole or in part, without the prior written consent
of dSPACE GmbH.
2010 - 2016 by:
dSPACE GmbH
Rathenaustrae 26
33102 Paderborn
Germany
This publication and the contents hereof are subject to change without notice.
CalDesk, ConfigurationDesk, ControlDesk, MicroAutoBox, SCALEXIO, SYNECT,
SystemDesk, TargetLink and VEOS are registered trademarks of dSPACE GmbH in the
United States or other countries, or both. Other brand names or product names are
trademarks or registered trademarks of their respective companies or organizations.
Contents
New Features 19
New Features of Platform Management and
Platforms/Devices (ControlDesk 5.6).................................. .... 19
DCIGSI1............................................................................. 234
DCI-GSI2............................................................................. 236
DS1005 PPC Board.............................................................. 238
DS1006 Processor Board................................................... .. 240
DS1007 PPC Processor Board............................................... 242
DS1103 PPC Controller Board.............................................. 245
DS1104 R&D Controller Board............................................. 246
DS1202 MicroLabBox.......................................................... 248
ECU Diagnostics.................................................................. 251
FlexRay Bus Monitoring....................................................... 252
LIN Bus Monitoring.............................................................. 254
MicroAutoBox..................................................................... 255
Multiprocessor System......................................................... 258
SCALEXIO............................................................................ 260
VEOS................................................................................... 262
Video Capturing.................................................................. 265
XCP on CAN........................................................................ 266
XCP on Ethernet.................................................................. 268
XCP on FlexRay.................................................................... 271
XIL API MAPort.................................................................... 273
Platform/Device-Related Properties............................................... 275
Active ODX Database / ODX Database Properties................. 279
Advanced Settings Properties............................................ .. 280
Assignment Properties......................................................... 281
Audio Settings Properties.................................................. .. 284
Backplane Properties........................................................... 284
Board Details Properties....................................................... 285
Board Hardware Properties.................................................. 286
Camera Characteristics Properties........................................ 287
Camera Control Settings Properties................................... .. 287
Camera Properties............................................................... 288
Camera Settings Properties.................................................. 289
CAN Interface Properties................................................... .. 290
CAN Settings Properties....................................................... 291
Capture Mode Settings Properties..................................... .. 292
CCP Settings Advanced Properties....................................... 293
CCP Settings Checksum Calculation Properties..................... 297
CCP Settings Properties..................................................... .. 298
Automation 539
Programming ControlDesk Automation........................................ 540
Automating Platform Management and Variable
Management.................................................................... .. 540
Platform Management Automation API Versions................. 545
Platform Handling........................................................................ 551
Platform-Related Interfaces.................................................. 551
Troubleshooting 553
Hardware Access Problems........................................................... 554
Problem with Accessing, e.g., SCALEXIO Hardware........... .. 554
Real-Time Application Handling Problems..................................... 555
Problem with Starting DS2201 Slave DSP Applications......... 555
Problems with Handcoded Applications............................... 555
Limitations 557
General Limitations for Platform Management.................. .. 557
Limitations for Platforms...................................................... 558
Limitations for Devices......................................................... 563
Index 611
Required knowledge Knowledge in handling the PC and the Microsoft Windows operating
system is assumed.
Admonition Description
Indicates a hazardous situation that, if
V DANGER
not avoided, will result in death or
serious injury.
Indicates a hazardous situation that, if
V WARNING
not avoided, could result in death or
serious injury.
Indicates a hazardous situation that, if
V CAUTION
not avoided, could result in minor or
moderate injury.
NOTICE Indicates a hazard that may cause
property damage if you do not avoid
it by following the instructions given.
Note Indicates important information that
should be kept in mind, for example,
to avoid malfunctions.
Tip Indicates tips containing useful
information to make your work
easier.
Naming conventions The following abbreviations and formats are used in this document:
%name% Names enclosed in percent signs refer to environment
variables for file and path names.
< > Angle brackets contain wildcard characters or placeholders for
variable file and path names, etc.
Special folders Some software products, for example, ControlDesk Next Generation
and AutomationDesk, use the following special folders:
Common Program Data folder A standard folder for application-
specific configuration data that is used by all users.
%PROGRAMDATA%\dSPACE\<InstallationGUID>\<ProductName>
Objective After you install your dSPACE software, the documentation for the
installed products is available as online help and Adobe PDF files.
Online help You can access the online help, dSPACE HelpDesk, as follows:
Windows Start menu Select Start (All) Programs
<ProductName> dSPACE HelpDesk (<ProductName>) to open
dSPACE HelpDesk with the start page of the selected product
displayed. You can also navigate and search in the user
documentation of any other installed software product and its
supported hardware.
Context-sensitive Press the F1 key or click the Help button in the
dSPACE software to get help on the currently active context.
Note
In some software products, context-sensitive help is not
available.
Related Documents
Objective Below is a list of documents that you are recommended to read when
working with ControlDesk:
Information in other documents
dSPACE Release documentation
New Features and Migration
Provides information on the new features of all the dSPACE software
products in the current dSPACE Release. It also gives you an
overview of software products with no or minor changes. There are
instructions on migrating from older dSPACE releases, especially
from older product versions, if required.
Software Installation and Management Guide
Provides detailed instructions on installing and handling the dSPACE
software. It also shows you how to manage dSPACE licenses.
Information in this topic CAN/LIN channels of SCALEXIO and VEOS as bus interfaces on page 19
LIN Bus Monitoring device: Support for FIBEX and AUTOSAR system
description files on page 20
LIN Bus Monitoring device: Variable observer functionality on page 20
SCALEXIO and DS1007 platforms: Naming processing unit/processor
board during registration on page 21
CAN/LIN channels of CAN/LIN channels of SCALEXIO and VEOS can now be selected as bus
SCALEXIO and VEOS as bus interfaces for the following devices:
interfaces n Bus monitoring devices
n CAN Bus Montoring device
Refer to How to Configure a CAN Bus Monitoring Device
on page 159.
n LIN Bus Montoring device
Refer to How to Configure a LIN Bus Monitoring Device
on page 164.
LIN Bus Monitoring device: The LIN Bus Monitoring device now also supports the following
Support for FIBEX and variable description file formats in addition to LDF:
AUTOSAR system n FIBEX:
description files
n Version 4.1.0, 4.1.1
n Version 3.1.0, 3.1.1
n Version 3.0.0
n AUTOSAR system description files according to the
AUTOSAR system template:
n Version 4.2.2
n Version 4.2.1
n Version 4.1.1 ... 4.1.3
n Version 4.0.3
n Version 3.2.1 ... 3.2.3
n Version 3.1.4
Note
n Keep the migration aspects in mind when you reuse an
experiment that was originally created with ControlDesk 5.5
or earlier and contains a LIN Bus Monitoring device. Refer to
Migrating from ControlDesk 5.5 to 5.6 ( ControlDesk
Next Generation Migration).
n LDF files (format version 1.2 and earlier) were supported by
the LIN Bus Monitoring device for the last time with
ControlDesk 5.5 (dSPACE Release 2015B).
LIN Bus Monitoring device: ControlDesk's variable observer functionality is now also supported
Variable observer for the LIN Bus Monitoring device.
functionality Refer to Observing Variables ( ControlDesk Next Generation
Measurement and Recording).
SCALEXIO and DS1007 You can specify a name for each processing unit of a
platforms: Naming SCALEXIO system and processor board of a DS1007 system during
processing unit/processor system registration.
board during registration Refer to Register Platforms on page 513.
Basics of Platforms/Devices
Basics of Platforms/Devices
Objective Platforms and devices are software modules in ControlDesk used for
carrying out calibration, measurement, ECU flash programming, or
ECU diagnostics tasks. They provide access to dSPACE real-time
hardware, ECUs, etc., and also to VEOS.
Global device
References to
global device
Experiment-specific
device
Visualization Description
Platform/ Status Bar
Device Icon
Disabled
(Any status n No logical connection is established between ControlDesk
indicated in the and the platform/device hardware or VPU.
status bar) n When a platform/device is disabled, ControlDesk does not
try to establish the logical connection for that
platform/device. Any communication between the
platform/device hardware or VPU and ControlDesk is
rejected.
n Online calibration is impossible. Offline calibration is
possible.
n Platform/device configuration is possible.
Connected
(Any status n A continuous logical connection is established between
indicated in the ControlDesk and the platform/device hardware or VPU.
status bar) n A platform/device must be in the 'connected' state before it
can change to the 'measuring/recording' or 'online
calibration started' state.
n Online calibration is impossible. ControlDesk did not yet
adjust the memory segments containing calibration data in
the platform/device and on the corresponding hardware or
VPU. Offline calibration is possible.
n Platform/device configuration is not possible. However, you
can invoke platform/device configuration for a
platform/device that is in the connected state. ControlDesk
temporarily sets the platform/device to the disconnected
state.
Disconnected
(Any status n No logical connection is established between ControlDesk
indicated in the and the platform/device hardware or VPU.
status bar) n When a platform/device is in the disconnected state,
ControlDesk does not try to reestablish the logical
connection for that platform/device.
n Online calibration is impossible. Offline calibration is
possible.
n Platform/device configuration is possible.
Visualization Description
Platform/ Status Bar
Device Icon
Measuring / Recording
or n A continuous logical connection is established between
ControlDesk and the platform/device hardware or VPU.
or
n Online calibration is possible. Parameter values can be
changed directly on the platform/device hardware or VPU.
n A measurement (or recording) is currently running.
n Platform/device configuration is not possible.
Online Calibration Started
n A continuous logical connection is established between
ControlDesk and the platform/device hardware or VPU.
n Online calibration is possible. Parameter values can be
changed directly on the platform/device hardware or VPU.
n Platform/device configuration is not possible.
Visualization Description
Platform/ Status Bar
Device Icon
Unplugged1)
(Any status n The logical connection between ControlDesk and the
indicated in the hardware was interrupted, for example, because the
status bar) ignition was turned off or the ControlDesk PC and the
hardware were disconnected.
Tip
A device whose connection between ControlDesk and
the device hardware is currently interrupted is also set
to the 'unplugged' state when you start online
calibration if both the following conditions are fulfilled:
n The device's Start unplugged property is enabled.
Platform/Device state The following illustration shows the platform/device states and their
transitions relationships. You can see the predecessor and successor states for
each platform/device state together with information on what caused
the state transition.
Disconnect
4) 5)
Connect
5)
5)
4)
4)
Disconnected Unplugged
Disable
Enable
Disabled
Tip
A device for which the connection between ControlDesk and
the device hardware currently is interrupted is also set to the
"unplugged" state when you start online calibration if both
the following conditions are fulfilled:
n The device's Start unplugged property is enabled.
n The Start online calibration behavior property is set to
"Ignore differences".
This is possible for CCP and XCP devices. For details on the
two properties listed above, refer to General Settings
Properties on page 313.
Note
After the ECU reboots, the default page is activated on the
ECU. For this reason, the currently active page on the
hardware can differ from the page that was last active in
ControlDesk before the ECU shutdown.
Note
For DS1007 PPC Processor Board, DS1202 MicroLabBox,
MicroAutoBox, and SCALEXIO platforms, the automatic
reconnect functionality is always enabled. You cannot change
this setting, but you can specify the Resume online calibration
behavior for the platforms.
Tip
A platform management instance provides information on
platforms and the applications loaded to them only for those
platforms that are supported by the respective dSPACE product.
Performing platform The following table shows the platform management activities that
management activities are synchronized between the platform management instances. You
can see which platform management activities are possible even if
another platform management activity in another dSPACE product is
currently running. Depending on the activity you perform,
Note
Not every platform management activity is available in every
dSPACE product.
Activity You Want to Perform in Activity That is Currently Running in Platform Management
Platform Management Instance A Instance B
Update Firmware
Clear System
Stop RTP(s)
Clear Flash
Register Platforms
Refresh Interface Connections
Refresh Platform Configuration
Clear System
Manage Recent Platform Configuration
Load Real-Time Application 1) 1) 1) 1) 1) 1) 1)
Stop RTP(s) 1) 1) 1) 1) 1) 1) 1)
Unload Real-Time Application 1) 1) 1) 1) 1) 1) 1)
Update Firmware 1) 1) 1) 1) 1) 1) 1)
Clear Flash 1) 1) 1) 1) 1) 1) 1)
Explore USB Flight Recorder 1) 1) 1) 1) 1) 1) 1)
Go Online / Start Online Calibration 1) 1) 1) 1) 1) 1) 1)
1) Only possible for different platforms since the activity you want to perform requires exclusive platform access.
Experiment parts that can When you switch from offline to real-time simulation, you can reuse
be reused the following parts of a ControlDesk experiment:
n Layouts for variable visualization
n Data sets for parameter calibration
Preconditions for reusing Reusing experiment parts is possible if ControlDesk can restore
experiment parts variable connections. A variable connection is the connection of a
variable to an instrument or a signal of a signal generator, for
example.
When you switch from offline to real-time simulation, ControlDesk
restores variable connections successfully if the following conditions
are fulfilled:
n The Platform name in experiment property is the same for the
platforms/devices in the offline and the real-time simulation.
Tip
n ControlDesk lets you rename platforms, which lets you
equalize the Platform name in experiment property of the
simulation platforms. Refer to Rename Platform/Device
on page 524.
n If you do not want to equalize the Platform name in
experiment property of the simulation platforms, you can
assign a platform manually. Refer to Assign Platforms
( ControlDesk Next Generation Layouting).
n The paths and names of variables are the same in the variable
descriptions for the platforms/devices in the offline and the
realtime simulation.
Separate experiments for You should create separate ControlDesk experiments when you
the simulation platforms switch the simulation platform.
As an example, the following illustration shows the platforms and
devices to be created in the two separate experiments when you
switch from offline simulation on VEOS to real-time simulation on
SCALEXIO:
VEOS SCALEXIO
platform platform Environment model
Environment VPU
application process
Reusing experiment parts To reuse experiment parts, export the parts to be reused from the first
experiment and import them to the second experiment.
The following table lists the related commands:
Note
For bus devices, ControlDesk checks only if the corresponding
CAN, LIN or FlexRay interface is connected to the host PC.
Supported CAN interfaces PC-based CAN interfaces The following PCbased CAN interfaces
are supported:
Supplier Interface
dSPACE n DCI-CAN1 (USB-toCAN converter)
n DCI-CAN2 (USB-toCAN/CAN FD converter)
n Calibration Hub (USB hub with two USB-toCAN interfaces)
Vector Informatik n CANcardXL
n CANcardXLe
n CANcaseXL
n VN16xx1)
n VN56101)
n VN76001)
n VN89001)
Note
To use ControlDesk's timer resynchronization in connection with
bus interfaces from Vector Informatik, perform the following steps:
1. Enable the Software time synchronization option in
Vector Informatik's hardware configuration tool. The tool is
accessible via the Control Panel.
2. Restart the interface driver.
For details, refer to Vector Informatik's user documentation.
Supplier Interface
Eberspcher Electronics n FlexCard Cyclone II
(formerly TZM) n FlexCard Cyclone II SE
n FlexCard USB
Note
n CAN channels on VEOS do not support CAN FD.
n The ECU Diagnostics device does not support CAN channels
of dSPACE platforms.
Configuring virtual devices To test your ControlDesk experiment with a virtual device that is
simulated on the host PC, such as the CalDemo ECU, you must select
the Virtual CAN interface. Virtual devices do not require external
hardware. You do not need to specify CAN settings, such as the baud
rate or CAN channel. However, you must specify message identifiers
for a virtual XCP on CAN ECU.
Note
n Do not mix up the Virtual CAN interface with
CAN channels on VEOS.
n The Calibration Hub cannot be configured for virtual devices.
Limitations There are some limitations when you use PCbased CAN interfaces.
Refer to Limitations for Devices on page 563.
Supported LIN interfaces PC-based LIN interfaces The following PCbased LIN interfaces are
supported:
Supplier Interface
Vector n CANcardXL
Informatik n CANcaseXL
n VN8900
Note
To use ControlDesk's timer resynchronization in connection with bus
interfaces from Vector Informatik, perform the following steps:
1. Enable the Software time synchronization option in Vector Informatik's
hardware configuration tool. The tool is accessible via the Control Panel.
2. Restart the interface driver.
For details, refer to Vector Informatik's user documentation.
Supported FlexRay The following PC-based FlexRay interface modules are supported:
interfaces
Supplier Interface
Eberspcher n FlexCard Cyclone II
Electronics (formerly n FlexCard Cyclone II SE
TZM) n FlexCard USB
Vector Informatik n VN7600
n VN8900
Note
To use ControlDesk's timer resynchronization in connection with bus
interfaces from Vector Informatik, perform the following steps:
1. Enable the Software time synchronization option in
Vector Informatik's hardware configuration tool. The tool is accessible
via the Control Panel.
2. Restart the interface driver.
For details, refer to Vector Informatik's user documentation.
Objective ControlDesk supports KLine interfaces to access ECUs via KLine for
diagnostics or flash programming purposes.
Supported KLine interfaces The following KLine interface modules are supported:
Supplier Interface
dSPACE DCI-KLine1 (USBtoKLine interface)1)
KPIT Technologies GmbH eCOM1)
1) Supported by the ECU Diagnostics device only.
Adding Platforms/Devices
Note
When an XCP on FlexRay device is used, the
configuration parameters are specified in the A2L file
and in an additional FIBEX file. Usually the FIBEX file is
referenced by the A2L file. If necessary, you can
specify an external FIBEX file during device
configuration. If you want to use the FIBEX file
referenced in the A2L file, ControlDesk expects the
FIBEX file to be located in the same folder as the A2L
file.
11 Enter or select the ECU Image file which contains the initial
parameter values for the application.
V WARNING
If the ECU Image file of a device does not provide initial
parameter values for the entire memory region described by
the memory segments of the device, ControlDesk sets the
remaining parameter values to "0" in the mirrored memory
and in the initially created data sets.
Do not download such data sets to the connected device
hardware when you start online calibration, since this may
cause property damage or even personal injury in connection
with the connected system. Upload the parameter values
from the connected device hardware instead.
Result You have added a new hosting SCALEXIO or VEOS platform and the
selected XCP on Ethernet devices representing the simulated virtual
ECUs to the experiment. The application and variable descriptions are
added to the experiment and assigned to the platform and newly
created devices.
Handling Platforms
Basics on Platforms
ControlDesks platform For platforms, ControlDesk provides functions that allow you to:
support n Register the platforms
n Configure the connection type: bus or network connection
n Load, start and stop applications
n Change parameter values and measure measurement values of the
application
n Manage the firmware of dSPACE realtime hardware
Simultaneous bypassing Many dSPACE systems provide one or more ECU interfaces, for
and calibration example:
n Several variants of MicroAutoBox
n Modular systems including at least one DS4121 ECU Interface
Board
n Modular systems with dSPACE CAN board (e.g., DS4302)
You can access an ECU for bypassing purposes via one of the above
systems, and simultaneously access the same ECU via one of the
available ECU interfaces. This allows you to perform function
bypassing and parameter calibration on one ECU at the same time.
Features of platforms for For the features of the platforms supported by ControlDesk, refer to:
accessing dSPACE real-time n DS1005 Features
hardware
n DS1006 Features
n DS1007 Features
n DS1103 Features
n DS1104 Features
n MicroAutoBox Features
n MicroLabBox Features
n SCALEXIO System Overview
Note
Unlike for other platforms, the registration of the XIL API MAPort
platform is not described in this topic. It is described in How to
Register and Configure an XIL API MAPort Platform
on page 113.
Tip
You do not need to register boards that support the plug & play
feature. The Platform/Device Manager automatically registers
them. This applies to:
n DS1104
Tip
You can add the DS1401ConfigGUI.exe tool as a user function.
Refer to How to Add External Programs or Scripts as User
Functions to ControlDesk ( ControlDesk Next Generation
Customization).
Tip
As an alternative, you can select the Register Platforms
command via the context menu of the Platform/Device
Manager.
2 From the Platforms list, select the type of the platform you want
to register.
Note
You cannot subsequently add processor boards to a DS1007
system that is already registered.
Note
You cannot subsequently add processing units to a SCALEXIO
system that is already registered.
Each processing unit has an edit field to specify its connection parameter
value and an edit field to specify a unique name for it. After registration,
the name is displayed in ControlDesk Next Generation's Platform/Device
Manager.
The valid characters are 'a ... z', 'A ... Z', '0 ... 9', '_', '-' and ' '. The
name must not start or end with an underline, hyphen or blank. If you
do not specify a custom name for a processing unit, ControlDesk
displays a default name for it in the Platform/Device Manager.
Scan for available Lets you scan the local network for connected platform hardware.
processor boards/ Depending on the platform type to be registered, ControlDesk opens
processing units/ the Scan Local Network for Processor Boards, the Scan Local Network for
platforms Processing Units or the Scan Local Network for Platforms dialog and
displays all the platform hardware found in the network. Refer to Scan
Local Network for Processor Boards/ Processing Units /Platforms dialog
on page 518.
Model Access Port Properties
Implementation Lets you select the MAPort implementation for the XIL API MAPort
platform.
The list displays all the supported XIL API MAPort implementations. The
XIL API MAPort platform analyzes the IMF files in the standard XIL API
folder (ProgramData\ASAM\XIL\Implementation) to determine the installed
XIL API MAPort implementations.
Product name Model Access Port Properties on page 337
Product version Model Access Port Properties on page 337
Vendor name Model Access Port Properties on page 337
XIL API version Model Access Port Properties on page 337
Multiprocessor Configuration Properties
Network client Assignment Properties on page 281
Processors Lets you specify the number of processors belonging to the
Note
You cannot subsequently add members to a multiprocessor system
that is already registered.
Tip
ControlDesk helps you to avoid erroneous entries. Affected
registration property settings are marked with the symbol.
Move the mouse pointer over the symbol to open a tool tip
with information on the reason for the error.
Tip
If you register a platform with corrupted boot firmware or
with hardware components containing different firmware
versions, a message box containing warning messages about
the detected firmware problem is displayed. The warning
messages are also displayed in the Log Viewer. In the
Platform/Device Manager, the affected hardware
components are marked with the symbol. Its tool tip also
provides information on the detected firmware problem. You
should check the entries and perform firmware updates, if
necessary. Refer to Update Firmware on page 533.
5 Repeat steps 2 ... 4 for all the platforms you want to register.
6 Click Close to close the Register Platforms dialog.
Possible methods n You can assign dSPACE real-time hardware or VEOS by adding the
registered platform to an experiment. Refer to Method 1
on page 66.
n You can assign dSPACE realtime hardware or VEOS to an existing
platform. Refer to Method 2 on page 67.
Tip
As an alternative, you can add a platform to the experiment
using the Add Platform/Device command, and assign the
hardware or VEOS to the platform by selecting the registered
platform from the Available platforms/devices list in the Add
Platform/Device dialog.
Assignment Description
Mode
Assign to any ControlDesk assigns the platform to a registered and unassigned platform of the relevant platform type,
equal platform according to the following assignment settings:
n Alias name
n Board name
n Connection type
n Net client
n Port address
n XIL API MAPort implementation
The above assignment settings are platform-type-specific. The list below shows the settings available for the
platform types:
n DS1005, DS1006, DS1103: Port address and/or Board name, Connection type, Net Client (only for the
Net connection type)
n DS1104: Board name
n MicroAutoBox: Board name (optional), Connection type, Net Client
n Multiprocessor System: Connection type
Multiprocessor System members: Port address
n DS1007, DS1202 MicroLabBox, SCALEXIO: IP address or Board name
n VEOS: none
n XIL API MAPort platform: XIL API MAPort implementation
Assign to identical (Not available for the VEOS and XIL API MAPort platforms) ControlDesk assigns the platform to registered
platform and unassigned dSPACE hardware of the relevant platform type, according to the following assignment
settings:
n Connection type
n Serial number
n MAC address
The above assignment settings are platform-type-specific. The list below shows the settings available for the
platform types:
n DS1005, DS1006, DS1103, DS1104, MicroAutoBox, Multiprocessor System members: Serial number
n Multiprocessor System: Connection type
Multiprocessor System members: Serial number
n DS1007, DS1202 MicroLabBox, SCALEXIO: MAC address
Note
If several platforms are assigned to dSPACE hardware in one
step (for example, if you call the Refresh Platform
Configuration command), the assignment modes are applied
to the platforms in a certain order:
1. Assign to identical platform
2. Assign to any equal platform
3. Assign to first available platform
Note
n Since a DS1104 R&D Controller Board is installed in a PCI
slot in the host PC, no connection type (BUS or NET) has
to be configured for the DS1104 platform.
Next steps n Add a variable description to the platform. For instructions, refer
to How to Add a Variable Description to a Platform/Device
( ControlDesk Next Generation Variable Management).
n If necessary, you can modify general settings for the platform. In
the Project Manager, select Configure Platform/Device from the
platform's context menu.
Objective Before you start a firmware update, you have to decide whether to
update the firmware to a later version or to repair the currently
installed firmware version.
Basics on Firmware
Firmware features The firmware for a hardware component provides basic functionality
that is stored in a nonvolatile memory. For example, it includes
functions for the communication between the host PC and the
hardware, and can also provide I/O functions such as CAN or LIN
protocol support, or complex I/O functions for an FPGA component.
Firmware components The following firmware components are
used with dSPACE realtime hardware.
Firmware Meaning
Firmware for the main hardware components
Boot firmware Provides essential functions to access the hardware system
connected to the host PC.
It also contains functions to provide a hardware inventory and to
load and start a realtime application.
Relevant for any hardware.
CN boot firmware Provides essential functions for the computation node (CN) to
configure the initial hardware settings and to load the CN
firmware.
Relevant for DS1007 and MicroLabBox.
CN firmware Provides the functionality for a realtime processor (computation
node).
Relevant for DS1007 and MicroLabBox.
CN CPU configuration Provides the hardware configuration of a realtime processor.
Relevant for DS1007 and MicroLabBox.
System FPGA firmware Provides the system functions for the programmable logic device
of the processor board.
Relevant for DS1007 and MicroLabBox.
Firmware Meaning
HCN boot firmware Provides essential functions for the host communication
coprocessor (host communication node) to configure the initial
hardware settings for communication and to load the HCN
firmware.
Relevant for DS1007 and MicroLabBox.
HCN firmware Provides the host communication functionality for the host
communication node and other services such as USB flight
recording.
Relevant for DS1007 and MicroLabBox.
Host IF firmware Provides functions that allow the communication between the
host PC and dSPACE realtime hardware that has an
Ethernetbased host interface.
Relevant for MicroAutoBox.
Host IF PLD firmware Provides functions for the programmable logic device that
controls the host interface communication.
Relevant for MicroAutoBox.
System PLD firmware Provides functions for the programmable logic device that offers
system functions, for example, watchdog handling or accessing
onboard sensors.
Relevant for MicroAutoBox.
DSx86_32 UserFirmware Provides essential functions to access the hardware system
connected to the host PC.
It also contains functions to provide a hardware inventory and to
load and start a realtime application.
Relevant for SCALEXIO.
Firmware for additional hardware components
AIO TYPE 1 PLD firmware Provides functions for accessing analog input and output signals
via the programmable logic device of the AIO Type 1 module.
Relevant for the DS1513 I/O board of MicroAutoBox.
ADC TYPE 4 PLD firmware Provides functions for accessing analog input signals via the
programmable logic device of the ADC Type 4 module.
Relevant for the DS1511 and DS1513 I/O boards of
MicroAutoBox.
CAN slave firmware Provides functions for CAN communication via a slave processor
or a connected I/O board.
Relevant for DS1103, DS2202, DS2210, DS2211, and DS4302
boards.
CAN TYPE 1 firmware Provides functions for CAN communication via the CAN Type 1
module.
Relevant for MicroAutoBox and MicroLabBox.
Firmware Meaning
DIO TYPE 3 PLD firmware Provides functions for accessing digital input and output signals
via the programmable logic device of the DIO Type 3 module.
Relevant for the DS1511 I/O board of MicroAutoBox.
DIO TYPE 4 PLD firmware Provides functions for accessing digital input and output signals
via the programmable logic device of the DIO Type 4 module.
Relevant for the DS1513 I/O board of MicroAutoBox.
DS4342 firmware Provides functions for CAN communication via the DS4342 CAN
FD Interface Module mounted on a DS4505 Interface Board or
MicroAutoBox.
DS<xxxx> UserFirmware Provides the basic functions for the related SCALEXIO board, for
example, for accessing digital input and output signals or the bus
interface.
Relevant for SCALEXIO boards.
DS<xxxx> UserIplFirmware Provides the bootloader for the related SCALEXIO board.
Relevant for the SCALEXIO DS6101 MultiI/O Board.
DS<xxxx> UserFpga Provides the functions realized on an FPGA module.
Relevant for SCALEXIO boards.
DS<xxxx> IoFpga Provides the I/O functions realized on an FPGA module.
Relevant for the SCALEXIO DS2680 I/O Unit.
FPGA Code Provides the system and I/O functions realized on an FPGA
module.
Relevant for DS1006.
FPGA TYPE 1 PLD firmware Provides basic functions for initializing and accessing the FPGA
Type 1 module.
Relevant for the DS1512 and DS1514 I/O boards of
MicroAutoBox.
I/O Clock Buffer Configuration Provides functions for processing the clock signal on the local
bus.
Relevant for MicroLabBox.
I/O CPLD firmware Provides functions for controlling and accessing the I/O modules.
Relevant for MicroLabBox.
I/O FPGA firmware Provides the I/O functions realized on an FPGA module.
Relevant for MicroLabBox.
LIN slave firmware Provides functions for LIN communication via a connected I/O
board.
Relevant for DS4330.
Slave DSP firmware Provides system and I/O functions for the slave DSP units.
Relevant for DS1103 and DS1104.
Note
Using DS802 PHS Link Board
You can update the firmware of I/O boards only if they are
supported by the DS802 PHS Link Board. For example, you
cannot update the above mentioned CAN slave firmware
components, if the boards are connected via DS802 PHS Link
Board. For an overview of the supported I/O boards, refer to
DS802 Data Sheet ( PHS Bus System Hardware Reference).
Note
To program the firmware that supports the RTI DS1552 I/O
Extension blockset for the DS1552 MultiI/O module, you have to
use the DS1401UpdateExtIO command, which is described in the
MicroAutoBox RTLib Reference.
Note
n The archive format for DS1007 and MicroLabBox changed
with Firmware Archives 2.0 contained in dSPACE
Release 2015B. To open an archive in the new format, you
must use Firmware Manager 2.0 or later.
n The archive format for SCALEXIO changed with Firmware
Archives 2.1 contained in dSPACE Release 2016A. To open
an archive in the new format, you must use Firmware
Manager 2.1.
Special firmware The firmware archives installed with your dSPACE software provide
the standard firmware type. There might be other firmware types to
be managed with the Firmware Manager.
Custom firmware The Firmware Manager allows you to install
custom firmware that dSPACE provides for solutions or engineering
projects.
User firmware
Note
When you use a SCALEXIO system, this term is used for the
standard firmware. The following restrictions refer only to
customized firmware.
NOTICE
dSPACE accepts no liability for incorrect operation or property
damage when using user firmware with dSPACE hardware.
Note
Note the following restriction if you use DS1007, MicroAutoBox,
or MicroLabBox.
In secured mode, for example, caused by an interrupted
firmware repair or update process, you cannot repair or update
the firmware components of the I/O components of the board
(connected I/O boards, internal I/O modules, or the I/O FPGA).
You firstly have to repair or update the firmware components of
the base board and then reboot the board to leave the secured
mode. Error messages regarding to the repair or update process
of the I/O components can be ignored. After reboot, you can
continue the repair or update process for the firmware of the I/O
components.
If your realtime hardware does not provide a secured mode for using
the default factory firmware, you have to repair the board's boot
firmware. You can do this via the command line interface of the
firmware management or via the Platform Manager. To repair the
corrupted boot firmware via the command line interface, refer to
Examples of ScriptBased Firmware Management ( Firmware
Manager Document).
Note
n The archive format for DS1007 and MicroLabBox changed
with Firmware Archives 2.0 contained in dSPACE
Release 2015B. To open an archive in the new format, you
must use Firmware Manager 2.0 or later.
n The archive format for SCALEXIO changed with Firmware
Archives 2.1 contained in dSPACE Release 2016A. To open
an archive in the new format, you must use Firmware
Manager 2.1.
Result You have configured the settings which are required for a firmware
update process in update or repair mode.
If you use a multiprocessor or a multicore system, note the following
points:
n If you have registered a multiprocessor system, you can update
only one processor at a time.
n If you have registered a multicore system with additional I/O
boards, you have to select the core to which the I/O boards are
connected for the update of the entire system. The other cores will
be updated too.
Objective Gives you the instructions for the firmware update mode.
Preconditions The firmware update process has to be prepared with the Update
Mode specified as described in How to Prepare the Firmware Update
on page 81.
Note
You must not switch off the hardware during the firmware
update process. This will cause a corrupted firmware.
Objective Gives you the instructions for the firmware repair mode.
Preconditions The firmware update process has to be prepared with the Repair
Mode specified as described in How to Prepare the Firmware Update
on page 81.
Result If there are updatable firmware components, the repair process starts.
You can see the progress in the Status column. The initial '--' entry is
replaced by a percentage. If the progress information cannot be
detected continuously, only the states 50% and 100% are displayed.
If the process successfully finished, an OK is shown, otherwise an
error message is displayed.
If the firmware repair process will require more than 40 minutes, an
estimate of the time is displayed. Then you can decide whether to
start the process. Interrupting a running firmware repair process is not
possible.
Note
You must not switch off the hardware during the firmware
repair process. This will cause a corrupted firmware.
DS1007 PPC
Processor Board
Cores
DS1007 PPC
Processor Boards
Loading applications to a To load a realtime application to a DS1007 system, you must load it
DS1007 system to the DS1007 PPC Processor Board platform (not to the individual
DS1007 PPC Processor Boards).
The illustration below shows a DS1007 multiprocessor system with
two DS1007 PPC Processor Boards. In the example, the datatypes_id
application is loaded to the DS1007 PPC Processor Board platform.
Real-time application
DS1007 PPC
Processor Boards
Application processes and Each real-time application contains one or more application
cores processes. Each application process runs on a separate processor core
of a DS1007 PPC Processor Board. Because the DS1007 PPC Processor
Board has a dualcore processor, up to two application processes can
run on a DS1007 PPC Processor Board.
The following illustration shows a DS1007 multiprocessor system with
two DS1007 PPC Processor Boards. In the example, the datatypes_id
application is loaded to the platform. The application contains the
four application processes master.ppc, slave.ppc, slave_b.ppc and
slave_c.ppc.
Real-time application
DS1007 PPC
Processor Boards
Application processes
Application process 4
slave_c.ppc
There are some differences in the working concepts for the DS1005
and the DS1007.
Migrating models For information on how to migrate a model for a DS1005 for use
with a DS1007, refer to Migrating from DS1005 to DS1007
( DS1007 Features).
Reusing experiments Experiments that were originally created for the DS1005 platform can
originally created for the be reused for the DS1007 platform.
DS1005 For details, refer to Switching the Simulation Platform and Reusing
Experiment Parts on page 38.
DS1005 platform
DS1007 platform
Application
DS1007 board
Application processes
Differences in tool Two platform automation API versions Handling the DS1005 via
automation tool automation is possible via Platform Management's platform API
version 1.0 and 2.0.
Unlike for the DS1005, handling the DS1007 via tool automation is
possible only via platform automation API version 2.0.
The version can be selected on the Platform Management Page in the
ControlDesk NG Options dialog.
Note
The two platform automation API versions are incompatible.
Reusing automation scripts originally created for handling the
DS1005 via platform automation API version 1.0 therefore
involves some migration steps.
For migration details, refer to Platform Management Automation
API Versions on page 545.
Adding and changing the The variable description (SDF file) of a Multiprocessor System platform
platform's variable contains information on:
description n The type of the multiprocessor system (DS1005 or DS1006)
n The number of processors/boards belonging to the multiprocessor
system
Note
The number of processors/boards specified in the SDF file
must not exceed the number of members that are specified
for the multiprocessor system during platform registration.
Otherwise, the multiprocessor system cannot be assigned to
the Multiprocessor System platform using the SDF file.
Checking the topology of During platform registration or in the platform properties, you can
the multiprocessor system enable the topology check. If enabled, ControlDesk checks if all the
DS1005/DS1006 processor boards of the multiprocessor system are
interconnected via Gigalinks.
Note
ControlDesk does not check whether the topology of the
connected boards is compatible with the topology required by
the realtime application to be loaded to the system, i.e., it does
not check whether the correct Gigalink ports of the processor
boards are used for interconnection.
Tip
When you perform a Gigalink topology check on demand,
ControlDesk also does the following:
ControlDesk generates topology information that you can use in
connection with RTI-MP to specify the multiprocessor system's
topology. Refer to Multiprocessor Topology Setup Dialog ( RTI
and RTI-MP Implementation Reference).
Note
Working with optional processors is supported for multiprocessor
systems based on DS1005 or DS1006 processor boards only. It is
not supported for multiprocessor systems based on DS1007 or
SCALEXIO.
Note
If you already added a variable description to the platform, it
is not sufficient to save the changed SDF file under its original
name and reload the variable description. Instead, you must
specify a new file name and add the file as a new variable
description.
Tip
It is recommended to add the variable description with all the
processor states set to enabled in the first step. This lets you
visualize variables from all processors in instruments. When you
disable processors later on, variables of the disabled processors
are displayed in the novalue view in instruments, but their
variable connections remain valid.
Example for a The following example applies to a multiprocessor system with three
multiprocessor application processors, where all the optional processors are enabled.
subset in which each In the SDF file, the state is enabled for each processor.
optional processor is
enabled
Example for a The following example applies to a multiprocessor system with three
multiprocessor application processors where the second processor is disabled.
subset in which one In the SDF file, the state of the second processor is disabled. The
optional processor is state of the other processors is enabled.
disabled
Tip
When you reactivate the variable description in which the state
of each member is enabled, values for signals originating from
Platform_2 are displayed again.
SCALEXIO system A SCALEXIO system can consist of one or more processing units, each
of which contains a number of processor cores.
Representation of a SCALEXIO system in ControlDesk In
ControlDesk, a SCALEXIO system is represented by a
SCALEXIO platform. You must specify the processing units belonging
to the system during platform registration. After registration, the
Platform/Device Manager displays the system (without the individual
processor cores).
Loading applications to a To load an application to a SCALEXIO system, you must load it to the
SCALEXIO system SCALEXIO platform (not to the individual processing units). Several
realtime applications (RTAs) can be loaded to a SCALEXIO platform,
but each RTA must be loaded from a different host PC. Each
processing unit can be used by one RTA at a time only.
Real-time applications
Application processes and Each real-time application contains one or more application
cores processes.
Assigning processing units to application processes To
download a SCALEXIO application, the target processing units to run
Application process 4
Accessing the You can access a SCALEXIO system by using the following
SCALEXIO system from dSPACE products at the same time, if they run on the same PC:
one PC n ConfigurationDesk
n ControlDesk Next Generation
n AutomationDesk
n ModelDesk
n rtplib2 Test Automation Python module
Note
The products to access the SCALEXIO system must be installed
from the same dSPACE Release.
Accessing the Another person can also access the SCALEXIO system by using
SCALEXIO system from a ControlDesk Next Generation running on a second PC.
second PC
Note
Consider the following restrictions when accessing the system
from a second PC:
n Do not execute platform management functions from a
second PC.
These are functions such as:
n Downloading a real-time application to the
SCALEXIO system
n Starting/stopping the real-time application on the
SCALEXIO system
n Access to the SCALEXIO system from a second PC is restricted
to measurement and recording tasks:
n Do not use ControlDesk's Signal Editor from a second PC
to stimulate variables of the real-time application running
on the SCALEXIO system.
n Do not use RealTime Testing from a second PC to
perform tests synchronously to the real-time application
running on the SCALEXIO system
n Do not use ControlDesk's Failure Simulation Module from
a second PC to control the failure simulation hardware of
the SCALEXIO system
n The products to access the SCALEXIO system (incl.
ControlDesk Next Generation running on a second PC) must
be installed from the same dSPACE Release.
V DANGER
When you use AutomationDesk to carry out automated tests on
a SCALEXIO system, do not use ControlDesk Next Generation to
change the values of model parameters that influence the
currently running test, because this will falsify the results.
The person carrying out automated tests will not even be able to
detect whether the SCALEXIO system is currently being accessed
by ControlDesk Next Generation.
Access levels Access levels are provided by the system for accessing the:
n SCALEXIO system
n Real-time application (executable on the SCALEXIO system)
Depending on the action you perform, other users' access to the
hardware and real-time application can be restricted. There are two
access levels:
n Exclusive access
Other users have no access.
n Shared access
Other users have shared but not an exclusive access. Actions
which need shared access can be carried out by several users at
the same time.
Access required for specific The following table shows actions in ConfigurationDesk, ControlDesk
actions Next Generation, AutomationDesk and ModelDesk for which each
user needs exclusive or shared access to the hardware and/or to the
real-time application.
Tip
The required access levels are independent of the status of the
ConfigurationDesk application (Connected to hardware or Not
connected to hardware).
XIL API MAPort platform The XIL API MAPort platform provides access to a simulation platform
via an ASAM XIL API implementation that is installed on your host PC.
Platform access is done via the model access port (MAPort). The
standardized hardware access is possible for any simulation platform
that supports an XIL API MAPort implementation supported by the XIL
API MAPort platform.
If access to the simulation platform via the XIL API MAPort platform is
configured, the XIL API MAPort platform can be used in ControlDesk
experiments. Basically, you can use it to perform measurements and
recordings, calibrate parameters, and manage data sets (manually or
via tool automation).
Supported XIL API versions The following XIL API versions for the MAPort implementation are
supported:
n XIL API version 2.0.1
Supported XIL API MAPort The standard XIL API folder (ProgramData\ASAM\XIL\Implementation)
implementations contains information on the XIL API implementations that are installed
on the host PC. The XIL API MAPort platform analyzes the IMF files
located in this folder to determine the installed and supported XIL API
MAPort implementations.
Registering an XIL API An XIL API MAPort platform is registered with an MAPort
MAPort platform implementation. During registration, ControlDesk displays all the
supported XIL API MAPort implementations for selection.
ControlDesk 5.6 supports the dSPACE XIL API implementation
delivered with dSPACE Release 2016A.
Configuring an MAPort After the XIL API MAPort platform is registered with an MAPort
implementation, the MAPort must be configured accordingly. You
have to load an appropriate MAPort configuration file. Depending on
the selected MAPort implementation, the MAPort configuration file
must have a specific file format and specific contents. Contact the
vendor of the XIL API MAPort implementation for details.
Using the dSPACE XIL API implementation If you want to access
simulator hardware via the dSPACE XIL API MAPort implementation,
the MAPort configuration file must be an XML file. The MAPort
configuration file mainly references the SDF file of the real-time
application and the simulator hardware.
Note
The file path to the SDF file can be absolute or relative. However,
relative paths must not contain subfolders.
Adapting the XIL API The dSPACEspecific XIL API implementation offers features that
implementation to exceed the standard XIL API functionality. For example, it is possible
ControlDesk to measure subelements of value blocks and measurement arrays,
which the standard functionality does not support. Another example
is that all the files which are in the same folder as the selected
MAPort configuration file are attached as related files to the variable
description. This ensures that the corresponding realtime application
can be automatically loaded to the simulation platform when online
calibration is started, regardless of whether you entered the file path
of the SDF file as a relative or an absolute path in the MAPort
configuration file. To make the enhancements and modifications of
the dSPACE XIL API implementation available for your work in
ControlDesk, some configurations have to be made.
ControlDesk supports further XIL API implementations. You probably
need dSPACE engineering support for putting them into operation
and adapting ControlDesk to them. Contact dSPACE Support.
Objective ControlDesk can access a simulation platform via an XIL API MAPort
platform only if the platform is configured correctly.
Preconditions n The XIL API MAPort implementation to be used with the platform
must be installed on the host PC.
n The XIL API MAPort implementation to be used with the platform
must be threadsafe to let ControlDesk perform tasks such as
measuring and observing variables in parallel.
n A suitable MAPort configuration file must be available.
Tip
You can register several XIL API MAPort platforms with the
same MAPort implementation. In contrast to other dSPACE
platforms, hardware assignment does not take place during
the platform registration, only after the MAPort has been
configured.
Note
Make sure that the selected MAPort configuration file is
suitable for the MAPort implementation selected for the XIL
API MAPort platform.
For example, if you work with a dSPACE XIL API MAPort
implementation, the MAPort configuration file must have the
XML format. The name of the simulation platform in the
XML file must match the platform name that is used for the
registration in ControlDesk. Refer to Basics on the MAPort
( dSPACE XIL API Implementation Guide).
Result You have registered the XIL API MAPort platform and configured the
MAPort. The platform is displayed in the Platform/Device Manager.
Next steps You can add the registered XIL API MAPort platform to a ControlDesk
experiment, and then add a variable description referenced by an
MAPort configuration file to the platform.
Unlike other platforms, the following conditions must be fulfilled
when calling the Add Variable Description command for an XIL API
MAPort platform:
n The registered XIL API MAPort platform must be assigned to the
platform in the experiment.
n ControlDesk must be physically connected to the simulation
platform referenced in the MAPort configuration file.
Information in this topic Simulation application and variable description on page 117
Loading an application on page 117
DS1007, DS1202 MicroLabBox, SCALEXIO, and VEOS platforms on page 117
XIL API MAPort platform on page 118
All other platforms on page 118
Starting an application on page 118
DS1007, DS1202 MicroLabBox, SCALEXIO, and VEOS platforms on page 118
XIL API MAPort platform on page 119
All other platforms on page 119
Reloading an application on page 119
DS1007, DS1202 MicroLabBox, SCALEXIO, and VEOS platforms on page 119
XIL API MAPort platform on page 119
All other platforms on page 119
Pausing the simulation application on page 119
VEOS on page 119
All platforms except for VEOS on page 119
Running a pausing simulation application stepwise on page 119
VEOS on page 119
All platforms except for VEOS on page 119
Stopping an application on page 119
DS1007, DS1202 MicroLabBox, SCALEXIO, and VEOS platforms on page 119
XIL API MAPort platform on page 120
DS1005, DS1006, DS1103, DS1104, and MicroAutBox platforms on page 120
Multiprocessor System platform on page 120
Unloading an application on page 120
DS1007, DS1202 MicroLabBox, SCALEXIO, and VEOS platforms on page 120
XIL API MAPort platform on page 120
All other platforms on page 120
Detecting terminated applications on page 120
Handling applications on a slave DSP on page 121
No offline calibration if variable description has no initial data set
on page 121
Adding additional initial parameter values on page 121
Access to mask and workspace parameters on page 122
Flash memory for standalone operation on page 122
Flight recorder on page 122
Loading an application There are different ways to load an application to realtime hardware
and VEOS. The status of an application after loading is closely related
to the way the application is loaded to the hardware or VEOS.
DS1007, DS1202 MicroLabBox, SCALEXIO, and VEOS platforms
To load an application to the dSPACE realtime hardware or VEOS,
you have the following possibilities:
n Via the Platform/Device Manager: You can decide whether to load
the application with or without subsequent start of the
application:
n Select the Real-Time Application / Offline Simulation
Application - Load and Start command from the platform's
context menu, or drag an application file from Windows
Explorer to the platform node.
The application is always started automatically after it is loaded.
n Select the Real-Time Application / Offline Simulation
Application - Load command from the platform's context
menu, or use the right mouse button to drag an application file
from Windows Explorer to the platform node.
The application is not started after it is loaded. After
downloading, the application state is STOPPED.
n When starting online calibration (Go Online) and starting
measuring (Start Measuring): When you start online calibration,
the realtime application is loaded to the hardware (if it is not
loaded yet). If an application is already loaded when online
calibration is started, it is not loaded again.
If the application is not yet loaded when online calibration is
started, it is started automatically after it is loaded if the platform's
Start application automatically after loading property is enabled.
If the application is already loaded when online calibration is
started, it is started automatically if the platform's Enforce starting
real-time application property is enabled.
Pausing the simulation VEOS To pause the offline simulation application loaded to VEOS,
application use the Pause command.
All platforms except for VEOS Pausing the real-time application
loaded to the platform is not possible.
Detecting terminated When you start online calibration, ControlDesk automatically detects
applications whether an application has been terminated. If ControlDesk detects a
terminated application, it cannot start measurement.
When ControlDesk detects a terminated application, you have the
following options:
n You can start online calibration without reloading the application.
The application remains terminated. Selecting this option can be
useful, for example, to investigate why the application has been
terminated.
n You can reload the application and then start online calibration.
Note
Termination can be detected only if the application was built
with dSPACE Release 7.3 or later.
Handling applications on a The DS1103 and DS1104 boards contain a slave DSP.
slave DSP ControlDesk Next Generation supports slave DSP applications of the
DS1103 and DS1104. When you download a main application
containing a slave DSP application to a DS1103 or DS1104, the slave
DSP application is loaded, too. An application for a slave DSP is
started and stopped together with the realtime application loaded on
the corresponding main processor.
If an application is loaded on the slave DSP, the current status of the
slave DSP is displayed in the Properties controlbar. Refer to Board
Details Properties on page 285.
Tip
RTI coming with dSPACE Release 4.1 and later provides the
Include initial parameter values option, which allows you to
make initial parameter values available in the variable description
to be generated. This lets you calibrate parameters of the
application even if ControlDesk is offline. For details, refer to the
RTI variable description file options category on the Code
Generation Dialog (Model Configuration Parameters Dialogs)
( RTI and RTI-MP Implementation Reference).
Adding additional initial Depending on the settings in the Simulink CoderTM, ControlDesk
parameter values allows you to add an additional set of initial parameter values on the
basis of a data set (or sub data set). This allows you to change initial
parameter values in the real-time application without rebuilding the
application via the Simulink CoderTM. For details, refer to How to
Create an Application Image ( ControlDesk Next Generation
Calibration and Data Set Management).
Access to mask and To access mask parameters and workspace parameters, you can use
workspace parameters MATLAB/Simulink's Inline parameters option and specify the
parameters as non-inline. As a result, the parameters are available in
the Tunable Parameters group of the real-time application's SDF file,
and can be changed during real-time simulation.
Tip
The access is the same for all dSPACE tools and requires no
MATLAB installation during real-time simulation since it is
calculated directly in the real-time application.
Flash memory for MicroAutoBox, MicroLabBox, the DS1005 PPC Board, the DS1006
standalone operation Processor Board, the DS1007 PPC Processor Board and the DS1104
R&D Controller Board contain a flash memory. Loading an application
to the flash memory allows you to use dSPACE real-time hardware as
a stand-alone system without a connection to the host PC. When you
reboot dSPACE real-time hardware, the application loaded to the
flash memory is first copied to the RAM of the hardware. Then the
application is started.
Refer to Autobooting Real-Time Applications on dSPACE Hardware
on page 126.
Note
To prevent the dSPACE real-time hardware from booting a flash
application, you have to clear the application from the flash
memory. If there is no application in the flash memory, the
hardware enters the idle state after powerup.
Flight recorder For some platforms, the flash memory can also be
used for flight recording. You can upload the flight recorder data to
the ControlDesk PC and store it in a measurement data file. Refer to
How to Upload Flight Recorder Data Written to the Internal Flash
Memory ( ControlDesk Next Generation Measurement and
Recording).
Tip
For some platforms, flight recorder data can also be written to a
USB mass storage device connected to the platform hardware.
ControlDesk lets you upload flight recorder data from a USB
mass storage device. Refer to How to Upload Flight Recorder
Data Written to a USB Mass Storage Device ( ControlDesk
Next Generation Measurement and Recording).
Using VEOS for offline VEOS is dSPACE software for the C-code-based simulation of virtual
simulation ECUs (V-ECUs) and environment VPUs on a PC.
To perform offline simulation with ControlDesk in conjunction with
VEOS:
n You need VEOS to be installed on your host PC. For further details
on VEOS, refer to VEOS Guide.
n You have to register a VEOS platform in the Platform/Device
Manager. For further details, refer to How to Register a Platform
on page 60 and VEOS on page 262.
XCP on
Ethernet V-ECU 1
device 1
.. ..
. .
XCP on
Ethernet V-ECU n
device n
Environment
VEOS Environment
VPU 1
platform VPU 1 - m
Opening demo projects For instructions on opening demo projects, refer to Opening a demo
project ( ControlDesk Next Generation Introduction and Overview).
Description of the demo The RT application demo projects allow you to work with ControlDesk
projects and use all of its features in connection with dSPACE real-time
hardware connected to the host PC, and in connection with VEOS.
Required licenses Working with this demo requires:
n A license for the ControlDesk Basic Version
n A license for the ControlDesk Standard Platforms Module
n (If you work with a SCALEXIO system) A license for the SCALEXIO
Platform Module
Demo projects The RT application demos consist of the following
demo projects:
n DS1005 project (including the DS1005 Demo experiment). To
access a DS1005 PPC Board connected to the host PC, the
experiment contains a DS1005 PPC Board platform.
n DS1006 project (including the DS1006 Demo experiment). To
access a DS1006 Processor Board connected to the host PC, the
experiment contains a DS1006 Processor Board platform.
n DS1007 project (including the DS1007 Demo experiment). To
access a DS1007 PPC Processor Board connected to the host PC,
the experiment contains a DS1007 PPC Processor Board platform.
n DS1103 project (including the DS1103 Demo experiment). To
access a DS1103 PPC Controller Board connected to the host PC,
the experiment contains a DS1103 PPC Controller Board platform.
n DS1104 project (including the DS1104 Demo experiment). To
access a DS1104 R&D Controller Board connected to the host PC,
the experiment contains a DS1104 R&D Controller Board platform.
n DS1202 project (including the DS1202 Demo experiment). To
access a MicroLabBox (DS1202) connected to the host PC, the
experiment contains a DS1202 MicroLabBox platform.
n DS1401 project (including the DS1401 Demo experiment). To
access a MicroAutoBox (DS1401) connected to the host PC, the
experiment contains a MicroAutoBox platform.
n Scalexio project (including the Scalexio Demo experiment). To
access a SCALEXIO system connected to the host PC, the
experiment contains a SCALEXIO platform.
n Scalexio MC project (including the Scalexio MC Demo experiment).
To access a SCALEXIO MC system connected to the host PC, the
experiment contains a SCALEXIO platform.
n VEOS project (including the VEOS Demo experiment). To access
VEOS, the experiment contains a VEOS platform.
Throttle control implemented on the dSPACE real-time
hardware The application running on the dSPACE real-time
hardware implements a throttle control.
SDF and executable file When you open a real-time application
demo project, ControlDesk automatically loads an SDF file to the
corresponding platform. The SDF file describes measurement variables
and parameters of the throttle control application running on the
Running a demo project After you have opened a demo project, you have to configure the
experiment's platform according to the dSPACE real-time hardware
connected to the host PC. For instructions, refer to How to Assign
dSPACE Real-Time Hardware or VEOS to a Platform on page 66.
Then you can start a measurement to run the demo project. When
you start a measurement, the executable file with the throttle control
real-time application is downloaded to the dSPACE real-time
hardware and then started. For instructions, refer to How to Start
Measuring ( ControlDesk Next Generation Measurement and
Recording).
Basics on autobooting You can enable dSPACE hardware to start an application from flash
dSPACE hardware memory or from a USB mass storage device, for example. On power-
up or restart of the hardware, this application is automatically
downloaded to the hardware and started on it.
After a real-time application autoboots on dSPACE hardware, you can
connect ControlDesk to the hardware. ControlDesk then detects the
running real-time application. ControlDesk therefore does not unload
the application when online calibration is started.
Autobooting support for The following table shows which dSPACE hardware supports
hardware autobooting.
No support of the AutoBoot Unlike ControlDesk 3.x, ControlDesk Next Generation does not
Option support the AutoBoot Option, which enables a DS1005 or DS1103
installed in an expansion box to start a realtime application without
any user interaction.
ControlDesk Next Generation cannot detect a running real-time
application on a DS1005 or DS1103 if the application was started via
AutoBoot Option. As a consequence, ControlDesk Next Generation
unloads the application when online calibration is started.
Basics When you load an application to the flash memory, the application is
copied to the RAM and then started. This also happens whenever you
reboot the dSPACE real-time hardware.
If you work with a DS1007 system or MicroLabBox, ControlDesk lets
you load an application to the hardware with or without a
subsequent start of the application. In the latter case the application
remains in the STOPPED state after it is loaded. This can be useful if
you have to specify parameters on the hardware before the
application is started, for example.
Note
Loading an application to the flash memory is not supported for
DS1007 multiprocessor systems.
Note
An application that was already in RAM is overwritten when you
load an application to the flash memory.
Tip
You can store calibrated parameter values to the flash memory
of the DS1005 and MicroAutoBox. Using the Store Calibration
Parameter to Flash solution, you can let a flash application store
calibrated parameter values during the regular shutdown process
or when you switch the SimState from RUN to STOP in
ControlDesk.
When the application restarts from the DS1005/MicroAutoBoxs
flash memory, the application starts with the parameter values
recently calibrated. Without the solution, the application would
start with the original parameter values as defined in the
Simulink model.
For detailed information on the solution, install it from the
dSPACE Solutions DVD and read the user guide. For information
on installing it, refer to the ReadMe.txt file.
Result You have loaded an application to the flash memory of the selected
dSPACE real-time hardware. The application is copied from the flash
to the RAM, and then started (the latter is optional for DS1007 and
MicroLabBox).
The state icon next to the platform icon (for DS1007 and
MicroLabBox platforms: next to the application icon) indicates that
the running application is loaded to the flash memory.
Objective You can clear an application that is currently in the flash memory.
This prevents the dSPACE real-time hardware from booting a flash
application.
The state icon next to the platform icon (for DS1007 and
MicroLabBox platforms: the state icon next to the application
icon) indicates that the realtime processor of the dSPACE real-
time hardware is stopped.
3 From the context menu of the platform, select Clear Flash.
The Clear Flash dialog opens.
4 In the dialog, select Clear flash application memory, then click the
Clear memory button.
Result You have cleared the application that was in the flash memory of the
selected dSPACE real-time hardware.
Basics You can download and start applications on dSPACE platforms via
the cmdloader command line tool. The tool runs in the command shell
of the operating system, so you can use it in batch files or makefiles.
Supported platforms You can use the cmdloader tool to download
and start applications on the following platforms:
n DS1005 PPC Board
n DS1006 Processor Board
n DS1007 PPC Processor Board
n DS1103 PPC Controller Board
n DS1104 R&D Controller Board
n MicroAutoBox
n DS1202 MicroLabBox
n Multiprocessor System (DS1005-based and DS1006-based)
n SCALEXIO
n VEOS
Message output Status messages of the cmdloader tool and
messages from the error check mechanism of the dSPACE platform
are displayed in a DOS window, which acts as the standard output.
Messages are also recorded in the log file.
Precondition for using the You must have registered the dSPACE system(s) since the cmdloader
cmdloader tool tool requires registration information.
Tip
Some platform types can be registered via the rnc parameter of
the cmdloader tool.
Using the cmdloader tool The cmdloader tool is located in the .\Main\bin folder of your
ControlDesk installation. When you use the tool, you have to specify
the entire path to it. If the path contains blanks, you have to enclose
the path in quotation marks.
Example For example, to display the cmdloader help, enter
"C:\Program Files (x86)\dSPACE ControlDesk 5.6\Main\bin\cmdloader" -?
in a DOS window.
Tip
To use the cmdloader tool in a DOS window without having to
specify the path to the tool, select All Programs -
dSPACE ControlDesk 5.6 - Utilities - Platform Management
Loader from the Windows Start menu.
This opens a DOS window. You do not have to specify the path
as long as this DOS window is open.
Syntax and command line Syntax The cmdloader tool has the following syntax:
parameters cmdloader <{application [-suppress_start]} | -start | -stop>
<-p platform_name | {-rnc net_client -t platform_type}>
[-go seconds] [-fl] [-ol output_level] [-q] [-ra] [-?]
Command line parameters You can use the cmdloader tool with
the following parameters:
Parameter Description
application1) The application to download to the selected platform. You must specify the
file extension (SDF, PPC, RTA or x86).
You also have to specify the relative or absolute path to the application. If
the path contains blanks, you have to enclose the path in quotation marks,
e.g.,:
"C:\Program Files\dSPACE ControlDesk 5.6\Demos\RTApplications\DS1005\ds1005_demo.sdf"
-suppress_start4) To suppress the start of the application (specified via the
application parameter) after it is downloaded to the target.
Note
This parameter is relevant only for DS1007, DS1202 MicroLabBox,
SCALEXIO and VEOS platforms.
Note
This parameter is relevant only for DS1007, DS1202 MicroLabBox,
SCALEXIO and VEOS platforms.
Note
This parameter is relevant only for DS1007, DS1202 MicroLabBox,
SCALEXIO and VEOS platforms.
-p platform_name2), 3) To scan the recent hardware configuration for the platform (specified via
platform_name), to try to register the platform, and to load the application
(specified via the application parameter) to the platform.
-rnc net_client2) To register a platform that is connected via net connection and that is not
yet registered, and add the platform to the recent hardware configuration.
Valid net_client values (depending on the platform type to be registered):
n IP address
n Alias name
Note
If you use the -rnc parameter, you also have to specify the -t
parameter.
Parameter Description
-t platform_type2) To specify the platform type for the -rnc parameter.
Valid platform_type values:
n DS1007
n DS1202
n DS1401
n SCALEXIO
Note
SCALEXIO systems with multiple processing units cannot be
registered in this way.
n VEOS
Note
Other platform types such as DS1006 cannot be registered using the -
rnc and the -t parameter combination.
-go seconds4) To specify the time during which the standard output can display error
messages returned by the error check mechanism of the platform. You have
to specify the time value in seconds. The maximum time value is 120 s.
Messages are also recorded in the log file.
-fl4) To load the application (specified via the application parameter) to the
flash memory of the platform (specified via the -p platform_name
parameter).
-ol output_level4) To specify the output level of cmdloader messages.
Valid output_level values range from 0 to 5. As an example, specifying -ol
0 selects the quiet mode.
-q4) To select the quiet mode, in which cmdloader messages are not displayed in
the standard output but are recorded in the log file.
-ra4) To scan the recent hardware configuration for platforms that are not yet
registered and to try to register them.
-?4) To display the cmdloader help.
1) One of the following parameters is mandatory: application, -start, -stop.
2)
Mandatory parameter
3) The platform name as displayed in the Properties controlbar:
Value Meaning
0 No error
1 Error loading the application
2 Error returned by the error check mechanism of the
platform
Examples The following examples show how to use the cmdloader tool for
batch operations.
n cmdloader -p ds1104 ds1104_demo.sdf
The cmdloader tool loads the ds1104_demo.sdf application to a
platform named ds1104 and starts the application.
n cmdloader -p ds1401 -fl ds1401_demo.sdf
The cmdloader tool loads the ds1401_demo.sdf application to the
flash memory of a platform named ds1401 and starts the
application.
n cmdloader -ra
The cmdloader tool scans the recent hardware configuration for
platforms that are not yet registered and tries to register them.
n cmdloader -ra -p ds1005 ds1005_demo.sdf
This example combines the use of the following parameters:
n -ra
n -p platform_name
n application
Handling Devices
Specifics of Devices
Objective To ensure the reliability of the data used for calibrating parameters,
ECU software consistency checks are supported for measurement and
calibration devices.
Principle of EPK checks ControlDesk performs consistency checks for measurement and
calibration devices, if the EEPROM (EPK) identifier is specified. Without
these checks, ECU behavior could be unpredictable.
Check on A2L and ECU Image file (EPK check) To check whether
the A2L file and the ECU Image file of the platform/device are
consistent, the ADDR_EPK and EPK attributes of the MOD_PAR element are
evaluated. These are optional attributes of A2L files and also
contained in ECU Image files.
The ADDR_EPK and EPK attribute values in the A2L file are compared to
the values in the ECU Image file. If they differ, the files are
inconsistent and you get a warning. Specify a consistent set of A2L
file and ECU Image file.
Note
The consistency check is not possible if no ADDR_EPK and EPK
attributes are defined in the A2L file and the ECU Image file.
Tip
The EPK attribute value is displayed in the Properties controlbar
of the platform/device. Refer to Common Properties
on page 301.
Objective You can specify the memory segments that contain the adjustable
parameters and that are mirrored on the host PC. The ECU Image file
can contain the data according to these memory segments.
ControlDesk can calculate checksums on the hardware and the
mirrored memory according to the segment definitions. The memory
segments will be up- or downloaded if the checksums differ. If no
ECU Image file is available, the memory segments are uploaded when
online calibration is started for the first time.
Basics on memory segments The memory of an ECU consists of different segments, such as code
segments, data segments, internal RAM, and segments for adaptive
parameters. A consistent A2L file contains information on the
different segments, their memory addresses and sizes. Different
segments of the same type may exist, because of noncontinuous
memory segments or a subdivision of larger units.
ECU Image file with code In some cases the ECU Image file contains code and data. Such an
and data ECU Image file is much larger than the file that holds only the
calibration parameters. Usually such a file is used to initially flash the
ECU with a new program version.
ECU Image file and memory segment definition
V WARNING
If the ECU Image file of a device does not provide initial
parameter values for the entire memory region described by the
memory segments of the device, ControlDesk sets the remaining
parameter values to "0" in the mirrored memory and in the
initially created data sets.
Do not download such data sets to the connected device
hardware when you start online calibration, since this may cause
property damage or even personal injury in connection with the
connected system. Upload the parameter values from the
connected device hardware instead.
Note
This setting is evaluated only if the ECU Image Creation
column is displayed. If the column is hidden (because the
Memory-segment-based ECU Image creation checkbox is
cleared), this setting is not evaluated but the whole ECU
memory image is exported.
Information on CAN signals DBC files provide information on the CAN signals contained in a CAN
in DBC files message. Among other things, the following information is provided:
n The DBC file defines the start bit and length in bits for each signal.
n The DBC file defines the byte order format (Motorola or Intel) for
each signal.
n The DBC file defines whether CAN signal values are interpreted as
signed or unsigned.
Signal formats in a CAN The signals within a CAN message can be arranged according to the
message Motorola or Intel format. In both formats the bit significance within a
byte is equal.
1 1 0 0 1 1 1 1
msb lsb
MSB and LSB The most significant byte (MSB) of a signal is the byte
that contains the most significant bit (msb) of the signal.
The least significant byte (LSB) of a signal is the byte that contains the
signal's least significant bit (lsb) of the signal.
Motorola format (also referred to as MSB first or big endian
format) In this format, the byte transmitted first of a signal in a CAN
message is the signals most significant byte.
Subformats for CAN signals Several CAN signal subformats are possible for the signals defined in
a DBC file. The positions of a signals start bit and all the other signal
bits within a message depend on the subformat. Since the DBC file
contains no information on byte order subformats, you have to
specify the subformat for CANbased measurement devices such as
the CAN Bus Monitoring device. This lets ControlDesk index the start
bits of the CAN signals defined in the DBC file correctly.
ControlDesk supports the following CAN signal subformats:
Indexing start
7 Bit 0
0 Byte transmitted
first
Start bit
msb
Byte
lsb
7 Byte transmitted
last
Start bit: 28
Length: 14
Indexing start
7 Bit 0
0 Byte transmitted
first
msb
Byte
Start bit
lsb
7 Byte transmitted
last
Start bit: 47
Length: 14
n Motorola Backward
The table below lists the characteristics of this format:
Indexing start At bit 0 of the last data
byte
Indexing of bits in a byte From right to left
of bytes in a message From right to left
Start bit of a CAN signal Signals lsb
The illustration below shows the layout of a CAN message with 8
bytes of data. As an example, the illustration also shows the
position of a CAN signal starting at bit 23 and 14 bits long.
7 Bit 0
0 Byte transmitted
first
msb
Byte
Start bit
lsb
7 Byte transmitted
last
Start bit: 23
Length: 14 Indexing start
Note
In this format, the number of data bytes in a CAN message
affects the position of the signal in the message since
indexing starts with the data byte transmitted last.
n Motorola Sequential
The table below lists the characteristics of this format:
Indexing start At bit 7 of byte 0
Indexing of bits in a byte From left to right
of bytes in a message From left to right
Start bit of a CAN signal Signals msb
The illustration below shows the layout of a CAN message with 8
bytes of data. As an example, the illustration also shows the
position of a CAN signal starting at bit 27 and 14 bits long.
Indexing start
7 Bit 0
0 Byte transmitted
first
Start bit
msb
Byte
lsb
7 Byte transmitted
last
Start bit: 27
Length: 14
Indexing start
7 Bit 0
0 Byte transmitted
first
Start bit
lsb
Byte
msb
7 Byte transmitted
last
Start bit: 28
Length: 14
n Intel Sequential
The table below lists the characteristics of this format:
Indexing start At bit 7 of byte 0
Indexing of bits in a byte From left to right
of bytes in a message From left to right
Start bit of a CAN signal Signals lsb
The illustration below shows the layout of a CAN message with 8
bytes of data. As an example, the illustration also shows the
position of a CAN signal starting at bit 27 and 14 bits long.
Indexing start
7 Bit 0
0 Byte transmitted
first
Start bit
lsb
Byte
msb
7 Byte transmitted
last
Start bit: 27
Length: 14
CalDemo
Opening demo projects For instructions on opening demo projects, refer to Opening a demo
project ( ControlDesk Next Generation Introduction and Overview).
Description of the demo The CalDemo project lets you work with ControlDesk and use its
project measurement and calibration features even without a real ECU
connected to your host PC.
Tip
No license for ControlDesk's ECU Interface Module is required.
n DCI-GSI2 device
The device is part of the DCI-GSI2 experiment in the CalDemo
project. The DCI-GSI2 device is used to access the CalDemo ECU.
If you have no DCI-GSI2 connected to the host PC, the Interface
Selection page of the device's Interface Selection dialog is empty.
However, starting online calibration is possible since the device
uses the localhost loopback address to communicate with the
CalDemo ECU.
The illustration below shows the demo setup in ControlDesk's Project
Manager:
You can observe the effect of the changed parameter value in the
Time Plotter.
Accessing ECUs
1 DCI-GSI1
or
DCI-GSI2
2
ControlDesk Calibration
ECU flash programming
ECU
with dSPACE Calibration
and Bypassing Service
3
Bus connection
or Ethernet dSPACE LVDS Bypass
prototyping interface
or
system
Ethernet
4
Bypassing
USB Interface
module
Ethernet 1
ControlDesk Calibration
2
ECU flash programming 3
FlexRay
Bus connection
or Ethernet dSPACE
prototyping
system
Bypassing 4
USB Interface
(directly or via module
Calibration Hub) 1
ControlDesk CAN
Calibration
ECU
with CCP Service
Bus connection
or Ethernet dSPACE
prototyping
system
Bypassing
USB Interface
(directly or via module
Calibration Hub) 1
ECU
with implemented
diagnostic protocol
Objective ControlDesk can use a CAN Bus Monitoring device for accessing a
CAN bus only if the device is configured correctly.
Tip
You can use dSPACE's simulation program CANGenerator to
experiment the CAN Bus Monitoring device without a
connection to real hardware devices. For information on the
CANGenerator, refer to CANGenerator on page 572.
Preconditions n Add the device to the experiment first. Refer to How to Add a
Platform/Device to an Experiment on page 49.
n To monitor the CAN communication of a SCALEXIO system or on
VEOS, the following conditions must be met:
n The SCALEXIO or VEOS platform must be registered in
ControlDesk. Refer to How to Register a Platform on page 60.
n A suitable application must be loaded to the SCALEXIO or
VEOS platform. Refer to Basics on Handling Simulation
Applications on page 116.
n To use ControlDesk's timer resynchronization in connection with
bus interfaces from Vector Informatik, perform the following
steps:
1. Enable the Software time synchronization option in
Vector Informatik's hardware configuration tool. The tool is
accessible via the Control Panel.
2. Restart the interface driver.
For details, refer to Vector Informatik's user documentation.
If the current experiment does not contain a suitable SCALEXIO or VEOS platform or if you want to
assign another bus channel to the device, you have to specify the IP address of the corresponding
SCALEXIO system or VEOS platform manually:
n Expand the Interface search attributes property to show the IP addresses property.
n Click or select Add from the context menu to add an edit field for an IP address.
n Enter the IP address of the SCALEXIO system or VEOS platform whose bus channel you want to
assign to the device.
If the bus channel of SCALEXIO that you want to use is also used in the model underlying the
application currently loaded to the SCALEXIO platform, you must enter the IP address that is
specified in the model.
To use a bus channel of VEOS, always enter 127.0.0.1 as the IP address.
4. Specify the connection option for the specified bus channel. Click the Browse button of the
Interface selection property to open the Interface Selection dialog.
Note
Do not mix up the Virtual CAN interface with CAN channels on VEOS.
Preconditions n Add the device to the experiment first. Refer to How to Add a
Platform/Device to an Experiment on page 49.
Objective ControlDesk can use a LIN Bus Monitoring device for accessing a LIN
bus only if the device is configured correctly.
Preconditions n Add the device to the experiment first. Refer to How to Add a
Platform/Device to an Experiment on page 49.
n To monitor the LIN communication of a SCALEXIO system or on
VEOS, the following conditions must be met:
n The SCALEXIO or VEOS platform must be registered in
ControlDesk. Refer to How to Register a Platform on page 60.
n A suitable application must be loaded to the SCALEXIO or
VEOS platform. Refer to Basics on Handling Simulation
Applications on page 116.
n To use ControlDesk's timer resynchronization in connection with
bus interfaces from Vector Informatik, perform the following
steps:
1. Enable the Software time synchronization option in
Vector Informatik's hardware configuration tool. The tool is
accessible via the Control Panel.
2. Restart the interface driver.
For details, refer to Vector Informatik's user documentation.
If the current experiment does not contain a suitable SCALEXIO or VEOS platform or if you want to
assign another bus channel to the device, you have to specify the IP address of the corresponding
SCALEXIO system or VEOS platform manually:
n Expand the Interface search attributes property to show the IP addresses property.
n Click or select Add from the context menu to add an edit field for an IP address.
n Enter the IP address of the SCALEXIO system or VEOS platform whose bus channel you want to
assign to the device.
If the bus channel of SCALEXIO that you want to use is also used in the model underlying the
application currently loaded to the SCALEXIO platform, you must enter the IP address that is
specified in the model.
To use a bus channel of VEOS, always enter 127.0.0.1 as the IP address.
4. Specify the connection option for the specified bus channel. Click the Browse button of the
Interface selection property to open the Interface Selection dialog.
Note
Do not mix up the Virtual CAN interface with CAN channels on VEOS.
Objective ControlDesk can access an ECU with CCP only if the CCP device is
configured correctly.
Configuring a CCP device Configuring a CCP device means selecting the CAN interface and
configuring CCP features. CCP service parameters such as CAN
identifiers are taken from the variable description. You can change
them if necessary.
For details on working with an ECU with CCP service in connection
with ControlDesk's CCP device, refer to the CCP Feature
Reference. For details on CANrelated settings, refer to Supported
CAN Interfaces on page 44.
Preconditions n Add the device to the experiment first. Refer to How to Add a
Platform/Device to an Experiment on page 49.
n To use a CAN channel of a SCALEXIO system or on VEOS as the
CAN interface, the following conditions must be met:
n The SCALEXIO or VEOS platform must be registered in
ControlDesk. Refer to How to Register a Platform on page 60.
n A suitable application must be loaded to the SCALEXIO or
VEOS platform. Refer to Basics on Handling Simulation
Applications on page 116.
n To use ControlDesk's timer resynchronization in connection with
bus interfaces from Vector Informatik, perform the following
steps:
1. Enable the Software time synchronization option in
Vector Informatik's hardware configuration tool. The tool is
accessible via the Control Panel.
2. Restart the interface driver.
For details, refer to Vector Informatik's user documentation.
If the current experiment does not contain a suitable SCALEXIO or VEOS platform or if you want to
assign another bus channel to the device, you have to specify the IP address of the corresponding
SCALEXIO system or VEOS platform manually:
n Expand the Interface search attributes property to show the IP addresses property.
n Click or select Add from the context menu to add an edit field for an IP address.
n Enter the IP address of the SCALEXIO system or VEOS platform whose bus channel you want to
assign to the device.
If the bus channel of SCALEXIO that you want to use is also used in the model underlying the
application currently loaded to the SCALEXIO platform, you must enter the IP address that is
specified in the model.
To use a bus channel of VEOS, always enter 127.0.0.1 as the IP address.
4. Specify the connection option for the specified bus channel. Click the Browse button of the
Interface selection property to open the Interface Selection dialog.
Note
Do not mix up the Virtual CAN interface with CAN channels on VEOS.
Tip
If you have only one DCIGSI1 connected to the host PC, you do
not have to assign it to a DCIGSI1 device in ControlDesk. It is
assigned automatically.
Features of the DCI-GSI1 For the features of the DCIGSI1, refer to DCI-GSI1 Feature
Reference.
Preconditions n Add the device to the experiment first. Refer to How to Add a
Platform/Device to an Experiment on page 49.
n To assign a DCIGSI1, the DCIGSI1 hardware must be connected
to the host PC via USB. Refer to Connecting an ECU with DCIGSI1
( ECU Interfaces Hardware Installation and Configuration).
Next steps n To configure an ECU interface, use the DCI Configuration Tool.
You can start it via Start Programs dSPACE DCI Configuration
Tool dSPACE DCI Configuration Tool. The tool lets you configure
the DCI-GSI1.
However, you should modify the configuration only if you are
familiar with ECU interface hardware.
n Name of the device
ControlDesk Next Generation identifies the device via its name.
The following cases are common:
You want to reuse the same configuration with several
identical ECUs, so the devices must have identical names.
You have specific configurations for different ECUs, so the
devices must have different names.
n Address and memory settings (experts only)
Preconfigure these settings according to the specifications
provided by the software vendor of your ECU.
For details on the DCI Configuration Tool and how to carry out the
configuration, refer to the DCI Configuration document.
Objective ControlDesk can access an ECU equipped with a DCIGSI2 only if the
DCIGSI2 is assigned to a DCIGSI2 device in ControlDesk. Otherwise,
ControlDesk cannot access the connected DCIGSI2 correctly.
Since the DCIGSI2 is connected to the host PC via XCP on Ethernet,
you can alternatively use the XCP on Ethernet device. However, it is
recommended to use the DCIGSI2 device because it provides some
DCIGSI2specific features.
Features of the DCI-GSI2 For the features of the DCIGSI2, refer to DCI-GSI2 Feature
Reference.
Assigning a DCIGSI2 The DCI-GSI2 supports three separate XCP service instances. Each
instance behaves as an XCP slave, providing independent access to
the ECU resources, i.e., the DCIGSI2 provides three ports to connect
the ECU with DCIGSI2 with up to three tools. Two of the ports can
be used to assign the DCIGSI2 to a DCIGSI2 device in ControlDesk.
Assigning a DCIGSI2 to a DCIGSI2 device means selecting the
DCIGSI2 and its Ethernet port to be used for communication, and
configuring XCP features.
Preconditions n Add the device to the experiment first. Refer to How to Add a
Platform/Device to an Experiment on page 49.
n To assign a DCIGSI2, the DCIGSI2 hardware must be connected
to the host PC via Ethernet. Refer to Connecting an ECU with
DCIGSI2 ( ECU Interfaces Hardware Installation and
Configuration).
Next steps To set and modify the configuration settings of your DCIGSI2, use
the dSPACE DCI Configuration Tool. Refer to the DCI
Configuration document.
For information on connecting a DCIGSI2 to the host PC, refer to
Setting up the Ethernet Connection Between a DCI-GSI2 and the Host
PC ( ECU Interfaces Hardware Installation and Configuration).
Objective dSPACE ECU interfaces provide system variables to give you status
information on the ECU and the connected ECU interface. You can
measure these variables in ControlDesk.
System variable A type of variable that represents internal variables
of the device or platform hardware and that can be used as
measurement signals in ControlDesk to give feedback on the status of
the related device or platform hardware. For example, an ECUs
power supply status or the simulation state of a dSPACE board can be
visualized via system variables.
Note
System variables are provided by the DCIGSI1 and DCIGSI2.
Data acquisition rasters for In most cases, system variables of ECU interfaces are automatically
system variables assigned to a particular internal data acquisition raster, which is used
exclusively for measuring system variables. It triggers sampling at a
fixed interval of 10 ms. Since this raster is executed on the device
without ECU service, it is possible to measure system variables even
when the ECU is not running.
For the DCIGSI1, the gsi_daq_time_raster_<raster_name> system
variables are an exception to this rule. For each measurement raster
that is defined in the IF_DATA DCIGSI1 element in the ECUs A2L file,
ControlDesk automatically creates an appropriate system variable,
named gsi_daq_time_raster_<raster_name>. It is automatically
assigned to the data acquisition raster that is specified in the ECUs
A2L file for the <raster_name> measurement raster.
Tip
n For the DCIGSI1, the automatically assigned data acquisition
raster for system variables is named DCI_Timer. The DCI_Timer
raster is available only for the system variables.
n For the DCIGSI2, you can use any available data acquisition
raster for measuring system variables as long as the assigned
data acquisition raster is based on a DCIGSI2s internal clock
event and is used exclusively for measuring system variables.
System variables in the tree System variables are contained in the Variable Browser. If the tree
view view is enabled, the structure of the variable description file is
displayed. The tree view contains the SystemVariables node as a
subnode of the variable description file. If you select the
SystemVariables node in the tree view, only system variables are
shown in the variable list.
System variables can be visualized in instruments like other
measurement variables. You can select a system variable from the
tree node and place it on a layout in the usual way.
For further information on system variables, refer to
n Status Information on the ECU and DCI-GSI1 ( DCI-GSI1 Feature
Reference)
n Status Information on the ECU and DCI-GSI2 ( DCI-GSI2 Feature
Reference)
ECU Diagnostics device ControlDesk provides the ECU Diagnostics v2.0.2 device, which
supports the ASAM MCD-3 D V2.0.2 standard.
ControlDesk supports the following ODX database standards:
n ASAM MCD-2 D V2.0.1
n ASAM MCD-2 D V2.2.0 (ISO 229011)
ECU diagnostics based on ECU diagnostics with ControlDesk are completely based on Open
ODX Diagnostic Data Exchange (ODX), the ASAM MCD-2 D (ISO 22901)
diagnostics standard. The ODX database contains the description of
the diagnostic services implemented on the ECU, and the settings for
communication between ControlDesk and the ECU.
ODX database Abbreviation of Open Diagnostic Data Exchange, a
diagnostics database ( Diagnostics database on page 577) that is
the central ECU description for working with an ECU Diagnostics
device ( ECU Diagnostics device on page 251) in ControlDesk. The
ODX database contains all the information required to perform
diagnostic communication between ControlDesk and a specific ECU
or set of ECUs in a vehicle network. ControlDesk expects the
database to be compliant with ASAM MCD-2 D (ODX).
Working with several ODX If you work with an ECU Diagnostics device, you can specify several
databases ODX diagnostics databases for it and switch between them. This
means you can manage multiple diagnostics databases for one device
in ControlDesk, but only one of them is active at a time. In the Project
Manager, all the diagnostics databases used in an experiment are
displayed below the ECU Diagnostics device. The currently active
database is displayed in bold letters with a or symbol
(depending on whether it has the ODX data or the binary format)
next to it. You can activate a diagnostics database via the Project
Manager or the Properties controlbar.
Working with several ODX databases enables you to check a further
ODX diagnostics database within an existing experiment without
having to modify or copy the experiment. After a successful test, you
can easily make the new diagnostics database the only diagnostics
database for the device by removing the other databases.
Hierarchical layers of an An ODX database contains several layers that are defined in the
ODX database ASAM MCD-2 D standard:
n The Protocol layer describes the information that is usually defined
in a vehicle manufacturer's protocol specification or international
standard (for example, KWP2000). This layer typically contains all
the information that is used by all a vehicle manufacturer's ECUs.
n The Functional group layer describes the information that is
relevant for a group of ECUs with similar functionality. This layer
typically contains all the information that is used by a group of a
vehicle manufacturer's ECUs.
n An ECU base variant contains data for all the variants of a specific
ECU.
n An ECU variant contains data for one specific variant of an ECU.
Protocol
Functional group
Inheritance
ECU base variant
ECU variant
More specific
Objective You can measure and calibrate diagnostics variables via the ECU
Diagnostics device. This requires that a variable description is
generated from the ODX database specified for the device.
Variable description You can enable or disable the generation of a variable description
generated from the ODX from the ODX database during device configuration via the Create
database variable description for selected logical links checkbox in the Select
Logical Links dialog, or via the Properties controlbar (refer to Logical
Link Selection Properties on page 333).
The variable description is saved in the Variable Descriptions folder in
the Project Manager. The generated variable description is named
after the ODX database, followed by "Variables".
The ODX database must meet some requirements so that
ControlDesk can create a variable description from it. For details, refer
to Conventions in Connection with ODX Databases ( ControlDesk
Next Generation ECU Diagnostics).
Objective ControlDesk can use the ECU Diagnostics device for accessing an ECU
via CAN or KLine for ECU diagnostics purposes only if the device is
configured correctly.
Renaming or modifying the If you modify (add, replace or remove) the files of an ODX database,
ODX database the ODX database is automatically reloaded, its proprietary binary
format (if specified) is regenerated, and the variable description (if
enabled) is regenerated.
When reloading a database, ControlDesk checks whether the
following configuration settings are still valid for the reloaded
database:
n Selected vehicle
n Selected logical link(s)
n Configuration of the diagnostic protocol, physical connection and
hardware settings for each selected logical link
Validity is checked hierarchically: A logical link can be valid only if the
corresponding vehicle information is still valid. The diagnostic protocol
and physical connection settings can be valid only if the
corresponding logical link is still valid. The hardware interface settings
can be valid only if the corresponding logical link, diagnostic protocol
and physical connection are still valid. Settings from the previous
configuration that cannot be applied are reset, and you must
reconfigure them via the configuration dialogs.
Variable description You can measure and calibrate diagnostics variables via the ECU
generated from the ODX Diagnostics device. A variable description must be generated from the
database ODX database specified for the device for this purpose. For further
information, refer to Requirements for Measurement and Calibration
via the ECU Diagnostics Device on page 182.
Preconditions n Add the device to the experiment first. Refer to How to Add a
Platform/Device to an Experiment on page 49.
n You must have a database compliant with ASAM MCD-2 D V2.0.1
or V2.2.0 (ISO 22901). For further information, refer to
Conventions in Connection with ODX Databases ( ControlDesk
Next Generation ECU Diagnostics).
Tip
You can specify several diagnostics databases for an ECU
Diagnostics device. You should then change their default
names for clarity and better handling.
Tip
As an alternative, you can add an ODX database template.
An ODX database template is a valid ODX database with
fixed contents that cannot be modified. ControlDesk provides
built-in ODX database templates for different diagnostic
protocols and also supports custom ODX database templates.
Built-in templates let you access your ECU via the ECU
Diagnostics device without having to provide an ODX
database yourself. Custom templates let you use an ODX
database that is available on your file system.
For further information on adding ODX database templates,
refer to Add ODX Database on page 372.
Tip
ControlDesk can detect the ODX version automatically using
the files you imported for the diagnostics database for your
ECU Diagnostics device. Alternatively, you can specify the
ODX version to be used with your ECU Diagnostics device
manually. Refer to Add ODX Database on page 372.
You can add further files to the database via the Add Files button.
To remove one or more files from the diagnostics database, select
them from the files list and click Remove or press the Delete key.
To remove all the files from the diagnostics database in one step,
click Remove All.
If you want ControlDesk to reload files in the diagnostics
database, select them from the files list and press the Reload
button. ControlDesk reloads the files from their original file source
paths, if possible.
Modifying (adding, replacing, or removing) the files belonging to
an ODX database that was already configured for the device
causes a reload of the ODX database.
5 You can specify to use a proprietary binary format (generated
from the ODX data) instead of ODX data for the diagnostics
database. Using the binary files allows faster experiment loading
and lets you work with large ODX databases since memory usage
is reduced. However, transforming the ODX data into the binary
format takes some time, so you should think carefully whether to
use ODX data or the binary format with your experiment.
Tip
Using the binary format is useful in the following cases:
n Experiments that are frequently loaded, and whose
diagnostics database is modified only rarely
n Experiments that require large ODX databases
Note
For ODX 2.2.0 diagnostics databases, database optimization
is always performed. You cannot change this setting. So if
you work with an ODX 2.2.0 database, ControlDesk always
uses the binary format instead of ODX data for the
diagnostics database.
n EcuVariantDiagLayerShortName_GeneratedLogicalLink_
BaseVariantShortName_FunctionalGroupShortName
Note
The pattern depends on the structure of the underlying
database.
Tip
ControlDesk supports logical link selection via ODX variant
identification. If the ODX database contains one or more ECU
Note
Your logical link selection must not contain more than one
simulated logical link. If you select two or more logical links
for which "Simulation" is specified as the physical
connection, the selection is invalid and ControlDesk opens a
dialog for you to define a valid logical link selection.
Note
ControlDesk can use only one (physical) K-Line interface at a
time.
For each logical link selected to be used with the ECU Diagnostics
device, the relevant communication parameters are displayed with
the original values specified for them in the ODX database and
their manually configured values. By default, the configured values
are equal to the ODX values. You can switch between the active
logical links via the dropdown list at the top of the dialog.
21 If necessary, specify userdefined values for single communication
parameters by overwriting the appropriate entries in the
Configured Value column. To make the Configured Value fields
editable, the Use configured ComParam values checkbox must be
selected. To reset the configured value of a communication
parameter to its original ODX value, you can click the appropriate
Reset button.
Via the Use configured ComParam values checkbox, you can
specify to use the configured values for the communication
parameters. If the checkbox is cleared, the original ODX values are
used.
You can modify the userdefined values or switch between the
ODX values and userdefined values later on via the Properties
controlbar. Refer to Logical Link Selection Properties on page 333.
22 Open the Connection Check page in the Active Logical Links
dialog to specify, for each individual active logical link, whether
and how to perform the (re)connection check and the cyclic ECU
communication check after the device is connected.
Note
For KLinebased diagnostic protocols, the
StartCommunication control primitive must be executed to
initialize the bus. So if you want to access an ECU via
KLine, you should not disable this option, because
otherwise communication with an ECU via KLine might
be impossible.
Note
For CANbased diagnostic protocols, the connection check
that is performed during the state transition from
"disconnected" to "connected" is done by executing a
TesterPresent service for the logical links. So if you want to
check the access to an ECU via CAN, you should enable
this option and specify the TesterPresent configuration
settings.
Tip
n ControlDesk comes with default configuration settings for
the connection check according to the diagnostic protocol
used. Via the Reset to default button you can reset the
logicallink-specific configuration settings for the
connection check behavior to their default values.
n In some cases, ControlDesk displays symbols that mark
specific configurations. The tool tips of the symbols
provide corresponding information.
23 Specify whether and when the diagnostic job for preparing the
ECU for security access is to be executed (with every online
calibration start, or only if a variable description was generated
from the ODX database for the ECU Diagnostics device). To do so,
select the appropriate value from the Security access execution
behavior list.
Result You have now configured the ECU Diagnostics device. The logical
links which are selected for use with this device are displayed in the
Project Manager.
Tip
ControlDesk displays the settings you specified during device
configuration hierarchically in the device's Properties controlbar.
You can also (re)configure an ECU Diagnostics device via the
Properties controlbar. Refer to Platform/Device-Related
Properties on page 275.
Next steps You can now place instruments on a layout and perform ECU
diagnostics tasks, or, if a variable description was generated from the
ODX database for the device, measure and calibrate scalar diagnostics
variables via the ECU Diagnostics device. Refer to
n ControlDesk Next Generation ECU Diagnostics
n ControlDesk Next Generation Measurement and Recording
n Calibrating Parameters ( ControlDesk Next Generation
Calibration and Data Set Management)
n How to Program the ECU Flash Memory via a Diagnostic Protocol
on page 223
You can specify multiple diagnostics databases for the device. Only
one database can be active at a time. Refer to
n Add ODX Database on page 372
n Activate ODX Database on page 369
n Configure ODX Database on page 406
Camera view
Windscreen
Sensor and
control unit
LIN, CAN, FlexRay
Ethernet, USB
Camera
ControlDesk Next Generation
Supported cameras ControlDesks Video Capturing device supports all the cameras using
DirectShow. DirectShow is a multimedia framework and API for
Integrated and separate You can choose between two methods to save video data in
capture modes ControlDesk:
n Integrated means that the video data is saved in the measurement
data file (MF4 or IDF file) together with other measurement data.
Note
To record large videos with high resolution and high quality,
it is recommended to use the Separate capture mode to
reduce the size of the measurement data files. However, to
work with large MF4 or IDF files in ControlDesk, you can split
them using the DSSIGCONV tool. Refer to How to Extract
Data from a Measurement Data File ( ControlDesk
Next Generation Measurement and Recording).
Note
Video data saved separately with the Separate capture mode
is not saved with the Save Buffer command.
Supported video codecs The Video Capturing device lets you specify a video codec to
compress/decompress video data. In Separate capture mode, you can
use any of the video codecs that are installed on the host PC for the
Video Capturing device. For example, you can use the Xvid codec
(www.xvid.org). By default, the Microsoft Video 1 codec is the used. It
is available on all Microsoft Windows operating systems. For more
Recording and replaying If your recording also contains measurement data from other
measurement data devices/platforms, the video data is automatically synchronized to the
synchronously measurement data. As shown in the illustration below, the time
cursors of the Plotter and the Video Monitoring instrument are
synchronized:
Virtual cameras to play The Video Capturing device lets you specify a virtual camera to replay
streamed video data or recorded videos or play data from video streams. This is particularly
replay a recorded video useful if you want to simulate a real video recording and synchronize
synchronously to signal it to signal measurements.
measurements
File size and quality of your The Video Capturing device provides several properties that influence
video the file size and the quality of a video in both, the integrated and the
separate capture mode. Some of those properties are listed below.
Property Description
Image width and Lets you specify the video resolution in
Image height pixels [px]. Higher resolutions provide
better quality but they also increase the file
size of the video.
Frame rate Lets you specify the frames per seconds
[fps]. Higher frame rates provide better
quality because motion is smoother, but
they also increase the file size of the video.
Color mode Lets you specify the color mode.
RGB 24 bit color provides better quality
because of the color spectrum, but also
increases the file size of the video.
Grayscale 8 bit provides lower quality
because of the missing colors, but it
reduces the file size of the video.
Capturing audio data The Video Capturing device can also record audio data in addition to
the video stream. If you use the Separate capture mode, you can
activate audio capturing, select an audio device, and specify further
audio capturing settings, for example, the audio format. For further
information, refer to Audio Settings Properties on page 284.
Objective ControlDesk can access a Video Capturing device only if the device is
configured correctly.
Preconditions n Add the device to the experiment first. Refer to How to Add a
Platform/Device to an Experiment on page 49.
n Some cameras need special drivers that you must install and
activate manually. For example, cameras from IDS (http://www.ids-
imaging.com/) need special drivers to work with ControlDesks
DirectShow interface. For more information, refer to Required
Third-Party Software ( Software Installation and Management
Guide).
3 Click Next.
The All Properties dialog opens.
You can use the default properties or set them according to your
needs. For example, you can select the Integrated or Separate
capture mode.
Virtual Camera Settings The Video Capturing device lets you specify a virtual camera to replay
already recorded videos or use data from video streams as input.
Setting Description
Auto-repeat Once finished, the video is automatically repeated.
Online Calibration The video starts after you have started online calibration.
Restart Video on Measurement Start The video automatically restarts with every new measurement.
Measurement The video starts upon initializing a measurement.
Tip
If a camera is already connected to another Video Capturing
device in the current experiment, it is displayed under Cameras in
Use:
Objective ControlDesk can access an ECU with XCP on CAN only if the XCP on
CAN device is configured correctly.
Configuring an XCP on CAN Configuring an XCP on CAN device means selecting the CAN
device interface and configuring XCP features. XCP service parameters such
as CAN identifiers are taken from the variable description. You can
change them if necessary.
For details on working with an ECU with XCP on CAN in connection
with ControlDesk's XCP on CAN device, refer to the XCP Feature
Reference. For details on CANrelated settings, refer to Supported
CAN Interfaces on page 44.
Preconditions n Add the device to the experiment first. Refer to How to Add a
Platform/Device to an Experiment on page 49.
n To use a CAN channel of a SCALEXIO system or on VEOS as the
CAN interface, the following conditions must be met:
n The SCALEXIO or VEOS platform must be registered in
ControlDesk. Refer to How to Register a Platform on page 60.
n A suitable application must be loaded to the SCALEXIO or
VEOS platform. Refer to Basics on Handling Simulation
Applications on page 116.
n To use ControlDesk's timer resynchronization in connection with
bus interfaces from Vector Informatik, perform the following
steps:
1. Enable the Software time synchronization option in
Vector Informatik's hardware configuration tool. The tool is
accessible via the Control Panel.
2. Restart the interface driver.
For details, refer to Vector Informatik's user documentation.
If the current experiment does not contain a suitable SCALEXIO or VEOS platform or if you want to
assign another bus channel to the device, you have to specify the IP address of the corresponding
SCALEXIO system or VEOS platform manually:
n Expand the Interface search attributes property to show the IP addresses property.
n Click or select Add from the context menu to add an edit field for an IP address.
n Enter the IP address of the SCALEXIO system or VEOS platform whose bus channel you want to
assign to the device.
If the bus channel of SCALEXIO that you want to use is also used in the model underlying the
application currently loaded to the SCALEXIO platform, you must enter the IP address that is
specified in the model.
To use a bus channel of VEOS, always enter 127.0.0.1 as the IP address.
4. Specify the connection option for the specified bus channel. Click the Browse button of the
Interface selection property to open the Interface Selection dialog.
Note
Do not mix up the Virtual CAN interface with CAN channels on VEOS.
Objective ControlDesk can access an ECU with XCP on Ethernet only if the XCP
on Ethernet device is configured correctly.
Tip
ControlDesk also lets you access XCP on Ethernet-based
measurement modules via the XCP on Ethernet device.
Configuring an XCP on Configuring an XCP on Ethernet device means selecting the Ethernet
Ethernet device device and configuring XCP features. XCP service parameters are
taken from the variable description. You can change them if
necessary.
For details on working with an ECU with XCP on Ethernet in
connection with ControlDesk's XCP on Ethernet device, refer to the
XCP Feature Reference.
Preconditions Add the device to the experiment first. Refer to How to Add a
Platform/Device to an Experiment on page 49.
Purpose Refer to
To prepare ControlDesk and the ECU for quick start measurement. XCP/GSI2 Settings Prepare Quick Start Property
on page 360
To specify quick start settings for the selected XCP or DCIGSI2 device. XCP/GSI2 Settings Quick Start Property
on page 361
To specify seed and key settings for the selected XCP device. XCP Settings Seed and Key Settings Properties
on page 353
Objective ControlDesk can access an ECU with XCP on FlexRay only if the XCP
on FlexRay device is configured correctly.
Configuring an XCP on Configuring an XCP on FlexRay device means selecting the FlexRay
FlexRay device interface and configuring XCP and FlexRay features. The
configuration parameters are taken from the variable description (A2L
file which includes an appropriate IF_DATA section for XCP on FlexRay)
and the FIBEX file which is referenced in the variable description file.
You can change the settings if necessary.
Preconditions n Add the device to the experiment first. Refer to How to Add a
Platform/Device to an Experiment on page 49.
n To use ControlDesk's timer resynchronization in connection with
bus interfaces from Vector Informatik, perform the following
steps:
1. Enable the Software time synchronization option in
Vector Informatik's hardware configuration tool. The tool is
accessible via the Control Panel.
2. Restart the interface driver.
For details, refer to Vector Informatik's user documentation.
Objective You can program the flash memory of ECUs. This allows you to store
a modified data set or a new ECU software revision on an ECU
permanently. The modified data set also remains active after you stop
using a calibration tool.
Objective Using the dSPACE ECU Flash Programming Tool, the flash memory of
ECUs can be programmed via ECU interfaces. You can access the tool
from within ControlDesk.
Restrictions Programming the flash memory of ECUs using the dSPACE ECU Flash
Programming Tool is possible only for various ECU types. Refer to
Supported ECU Interface Types ( ECU Flash Programming).
Preconditions To program the flash memory of an ECU, you must have an ECU
Image file which contains the calibration data, ECU application code
and/or ECU boot code to be flashed to the ECU. For example, you can
create an ECU Image file out of the data set to be programmed to the
flash memory. Refer to How to Create an ECU Image File
( ControlDesk Next Generation Calibration and Data Set
Management).
Possible methods n You can start the dSPACE ECU Flash Programming Tool via the
Windows Start menu. Refer to Method 1 on page 222.
n You can start the dSPACE ECU Flash Programming Tool from
within ControlDesk. Refer to Method 2 on page 222.
Method 1 To start the dSPACE ECU Flash Programming Tool via the
Windows Start menu
1 From the Windows Start menu, select Programs dSPACE ECU
Flash Programming Tool dSPACE ECU Flash Programming Tool.
Method 2 To start the dSPACE ECU Flash Programming Tool from within
ControlDesk
1 From the context menu of the device, select Flash ECU.
Result The dSPACE ECU Flash Programming Tool is started, displaying the
last selected flash project.
Tip
If you want to use the dSPACE ECU Flash Programming Tool
with a specific ECU Image file as the flash data source, you can
use one of the following alternative methods to start the tool:
n You can start the dSPACE ECU Flash Programming Tool from
ControlDesk Next Generation. Doubleclick the ECU Image
file to be used as the flash data source in ControlDesks
Project Manager, or select Open from its context menu.
n You can start the dSPACE ECU Flash Programming Tool from
Windows Explorer. Navigate to the ECU Image file to be used
as the flash data source in Windows Explorer and doubleclick
it.
Note
The HEX, MOT, S19, and SREC file name extensions are
automatically associated with the dSPACE ECU Flash
Programming Tool, if you confirmed this when installing the
dSPACE ECU Flash Programming Tool. If the dSPACE ECU Flash
Programming Tool does not start when you use one of the
methods of opening the tool from an ECU Image file described
above, check whether the file name extension of the selected
ECU Image file is associated with the dSPACE ECU Flash
Programming Tool, that is, whether the dSPACE ECU Flash
Programming Tool has been selected for opening files of this
type. If it is, a small icon indicating the dSPACE ECU Flash
Programming Tool is displayed beside the ECU Image file in
Windows Explorer.
Next steps You can now select an existing or define a new flash project for ECU
flash programming or testing purposes. For details on the dSPACE
ECU Flash Programming Tool and how to carry out the ECU flash
programming, refer to the ECU Flash Programming document.
Objective With the ControlDesk ECU Diagnostics Module, the flash memory of
ECUs can be programmed via diagnostic protocols. ControlDesk uses
the flash programming information contained in the ODX database
for this.
6 The Input Parameter tab displays the input parameters of the flash
job belonging to the selected flash session. You can change the
settings of writable input parameters before the flash operation is
started.
7 On the Options tab, you can specify whether the flash job
contains the StartCommunication control primitive or ControlDesk
must execute the control primitive before the flash job is started.
n With the checkbox selected, ControlDesk starts the flash job
(which is expected to execute the StartCommunication control
primitive) without having to execute any control primitives
beforehand.
n With the checkbox cleared, ControlDesk executes the
StartCommunication control primitive before it starts the flash
job.
Note
For KLinebased diagnostic protocols, the
StartCommunication control primitive must be executed first
to initialize the bus. Otherwise, communication with an ECU
via KLine is impossible.
Result You have supplied the ECUs flash memory with the latest software
revision and/or new calibration data.
Platform/Device Descriptions
Configuring the device For instructions on configuring the device, refer to Bus Device
Configuration on page 158.
Device properties The device provides the following properties and settings:
Purpose Refer to
To select the CAN interface for the selected device. CAN Interface Properties on page 290
To specify CAN settings for the selected CANbased device. CAN Settings Properties on page 291
To specify common properties of the platform/device. Common Properties on page 301
To specify the byte order format for the DAQ data. DAQ Settings Properties on page 305
To specify general settings of the selected platform/device. General Settings Properties on page 313
To specify inheritance settings for the selected device. Inheritance Settings Properties on page 329
Related commands The CAN Bus Monitoring device provides the following commands:
Purpose Refer to
To insert a platform/device into the active project or experiment. Insert Platform / Add Platform/Device on page 479
To add a new variable description, and (if applicable) a new ECU Image Add Variable Description ( ControlDesk
file, to a platform/device. Next Generation Variable Management)
To configure the platform/device selected in ControlDesk and assign it to Configure Platform/Device on page 431
the available hardware or VEOS.
To establish a logical connection between ControlDesk and the selected Connect Platform/Device on page 467
platform/device hardware or VPU.
To add columns to the platform/device list or to remove them from it. Customize Columns (Platform/Device Manager)
on page 469
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To filter the platform/device list. Filter on page 475
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
CCP
Introduction to CCP and the For an introduction, refer to Introduction to the Features of CCP and
CCP device the CCP Device ( CCP Feature Reference).
Configuring the device For instructions on configuring the device, refer to How to Configure
a CCP Device on page 168.
Device properties The device provides the following properties and settings:
Purpose Refer to
To select the CAN interface for the selected device. CAN Interface Properties on page 290
To specify CAN settings for the selected CANbased device. CAN Settings Properties on page 291
To specify CCP-specific settings for the selected device. CCP Settings Properties on page 298
To specify advanced settings for the selected CCP device. CCP Settings Advanced Properties on page 293
To specify checksum calculation settings for the selected CCP device. CCP Settings Checksum Calculation Properties
on page 297
To specify seed and key settings for the selected CCP device. CCP Settings Seed and Key Settings Properties
on page 300
To specify common properties of the platform/device. Common Properties on page 301
To specify ECU-specific settings for the selected device. ECU Information Properties on page 306
To specify general settings of the selected platform/device. General Settings Properties on page 313
To specify inheritance settings for the selected device. Inheritance Settings Properties on page 329
Purpose Refer to
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To filter the platform/device list. Filter on page 475
To import the entire contents of a data set container (variable Import Data Set Container ( ControlDesk
description, data sets, ECU Image files). Next Generation Calibration and Data Set
Management)
To view, customize, add, and delete memory segments of the memory Memory Segments on page 489
of the selected device.
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
DCIGSI1
Feature overview For a feature overview of the DCIGSI1, refer to Features of the
DCIGSI1 ( DCI-GSI1 Feature Reference).
Configuring the device For instructions on configuring the device, refer to How to Assign a
DCIGSI1 to a DCIGSI1 Device on page 172.
Device properties The device provides the following properties and settings:
Purpose Refer to
To specify common properties of the platform/device. Common Properties on page 301
To specify general settings of the selected platform/device. General Settings Properties on page 313
To select a connected DCI-GSI1 interface and assign it to the device. GSI Interface Properties on page 324
To specify checksum calculation settings for the selected DCI-GSI1 GSI Settings Checksum Calculation Properties
device. on page 325
To specify the settings of the overlay elements. Overlay Management Properties on page 339
Purpose Refer to
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
DCI-GSI2
Feature overview For a feature overview of the DCI-GSI2, refer to Features of the DCI-
GSI2 ( DCI-GSI2 Feature Reference).
Configuring the device For instructions on configuring the device, refer to How to Assign a
DCIGSI2 to a DCIGSI2 Device on page 174.
Device properties The device provides the following properties and settings:
Purpose Refer to
To specify common properties of the platform/device. Common Properties on page 301
To specify ECU-specific settings for the selected device. ECU Information Properties on page 306
To specify Ethernet settings for the selected platform/device. Ethernet Settings Properties on page 307
To specify general settings of the selected platform/device. General Settings Properties on page 313
To specify network adapter settings for the selected platform/device. Network Adapter Properties on page 338
Purpose Refer to
To specify the settings of the transport layer on the ECU with XCP/DCI- Transport Layer Settings Properties on page 343
GSI2.
To specify the communication settings of the selected platform/device. XCP on Ethernet/GSI2 Ethernet Settings Properties
on page 350
To specify advanced settings for the selected XCP or DCIGSI2 device. XCP/GSI2 Settings Advanced Properties
on page 353
To specify checksum calculation settings for the selected XCP or XCP/GSI2 Settings Checksum Calculation Properties
DCIGSI2 device. on page 358
To prepare ControlDesk and the ECU for quick start measurement. XCP/GSI2 Settings Prepare Quick Start Property
on page 360
To specify quick start settings for the selected XCP or DCIGSI2 device. XCP/GSI2 Settings Quick Start Property
on page 361
Purpose Refer to
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
Feature overview For a feature overview of the DS1005 PPC Board, refer to Feature
Overview ( DS1005 Features).
Configuring the platform For instructions on configuring the platform, refer to Basics of
Handling Platforms on page 58.
Platform properties The platform provides the following properties and settings:
Purpose Refer to
To specify the assignment of the selected platform in the experiment to Assignment Properties on page 281
a registered platform.
To display details of the selected board. Board Details Properties on page 285
To specify common properties of the platform/device. Common Properties on page 301
To display the connection settings of the selected platform. Connection Settings Properties on page 304
Purpose Refer to
To specify general settings of the selected platform/device. General Settings Properties on page 313
To display the memory settings of the selected platform. Memory Properties on page 337
To display the properties of the selected real-time application currently Real-Time Application Properties on page 340
loaded to the platform.
To display module version information for the selected platform. Version Properties on page 347
Related commands The DS1005 PPC Board platform provides the following commands:
Purpose Refer to
To add a registered platform to the currently active project. Add to Active Experiment on page 397
To insert a platform/device into the active project or experiment. Insert Platform / Add Platform/Device on page 479
To add a new variable description, and (if applicable) a new ECU Image Add Variable Description ( ControlDesk
file, to a platform/device. Next Generation Variable Management)
To clear the flash memory of the selected platform, in whole or in part. Clear Flash on page 403
To configure the platform/device selected in ControlDesk and assign it to Configure Platform/Device on page 431
the available hardware or VEOS.
To establish a logical connection between ControlDesk and the selected Connect Platform/Device on page 467
platform/device hardware or VPU.
To add columns to the platform/device list or to remove them from it. Customize Columns (Platform/Device Manager)
on page 469
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To filter the platform/device list. Filter on page 475
To import the entire contents of a data set container (variable Import Data Set Container ( ControlDesk
description, data sets, ECU Image files). Next Generation Calibration and Data Set
Management)
To load a real-time application to the RAM of the selected hardware, Real-Time Application - Load on page 502
and start it automatically.
To load an application to the flash memory of the selected hardware, Real-Time Application - Load to Flash
and start it automatically. (DS1005/DS1006/DS1104/MicroAutoBox)
on page 503
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To reload the currently loaded application. Real-Time Application - Reload on page 506
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
Purpose Refer to
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop the application running on the selected platform. Stop RTP on page 531
To update the firmware of the selected platform. Update Firmware on page 533
To upload flight recorder data and save it to a measurement file. Upload Flash Flightrecorder Contents on page 537
Feature overview For a feature overview of the DS1006 Processor Board, refer to
Feature Overview ( DS1006 Features).
Configuring the platform For instructions on configuring the platform, refer to Basics of
Handling Platforms on page 58.
Platform properties The DS1006 Processor Board platform provides the following
properties and settings:
Purpose Refer to
To specify the assignment of the selected platform in the experiment to Assignment Properties on page 281
a registered platform.
To display details of the selected board. Board Details Properties on page 285
To specify common properties of the platform/device. Common Properties on page 301
To display the connection settings of the selected platform. Connection Settings Properties on page 304
To specify general settings of the selected platform/device. General Settings Properties on page 313
Purpose Refer to
To display the memory settings of the selected platform. Memory Properties on page 337
To display the properties of the selected real-time application currently Real-Time Application Properties on page 340
loaded to the platform.
To display module version information for the selected platform. Version Properties on page 347
Related commands The DS1006 Processor Board platform provides the following
commands:
Purpose Refer to
To add a registered platform to the currently active project. Add to Active Experiment on page 397
To insert a platform/device into the active project or experiment. Insert Platform / Add Platform/Device on page 479
To add a new variable description, and (if applicable) a new ECU Image Add Variable Description ( ControlDesk
file, to a platform/device. Next Generation Variable Management)
To configure the platform/device selected in ControlDesk and assign it to Configure Platform/Device on page 431
the available hardware or VEOS.
To establish a logical connection between ControlDesk and the selected Connect Platform/Device on page 467
platform/device hardware or VPU.
To add columns to the platform/device list or to remove them from it. Customize Columns (Platform/Device Manager)
on page 469
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To filter the platform/device list. Filter on page 475
To clear the flash memory of the selected platform, in whole or in part. Clear Flash on page 403
To load a real-time application to the RAM of the selected hardware, Real-Time Application - Load on page 502
and start it automatically.
To load an application to the flash memory of the selected hardware, Real-Time Application - Load to Flash
and start it automatically. (DS1005/DS1006/DS1104/MicroAutoBox)
on page 503
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To reload the currently loaded application. Real-Time Application - Reload on page 506
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
Purpose Refer to
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop the application running on the selected platform. Stop RTP on page 531
To update the firmware of the selected platform. Update Firmware on page 533
Tip
The DS1007 PPC Processor Board is the successor to the DS1005
PPC Board. For the differences in ControlDesk's working
concepts for the DS1005 and the DS1007, refer to Working
Concept Differences Between DS1005 and DS1007 on page 89.
Feature overview For a feature overview of the DS1007 PPC Processor Board, refer to
Feature Overview ( DS1007 Features).
Configuring the platform For instructions on configuring the platform, refer to Basics of
Handling Platforms on page 58.
For further general information on working with a DS1007 platform,
refer to DS1007 Platform Configuration on page 85.
Platform properties The DS1007 Processor Board platform provides the following
properties and settings:
Purpose Refer to
To specify the assignment of the selected platform in the experiment to Assignment Properties on page 281
a registered platform.
To display details of the selected board. Board Details Properties on page 285
To display hardware information on the selected component of the Board Hardware Properties on page 286
DS1007, MicroLabBox, or SCALEXIO system.
To specify common properties of the platform/device. Common Properties on page 301
To display the connection settings of the selected platform. Connection Settings Properties on page 304
To display information identifying the hardware-related software. Firmware Version Property on page 308
To specify general settings of the selected platform/device. General Settings Properties on page 313
To display information on the Gigalink connections of the selected Gigalink Information Properties on page 323
DS1007 multiprocessor system.
To display information on the host interface settings. Host Interface Properties on page 325
To display details on the selected component of the DS1007, Identification Properties on page 327
MicroLabBox or SCALEXIO system or VEOS simulator for identification
purposes.
To display the DS1005/DS1006 processor boards that form the selected Member Overview Properties on page 335
Multiprocessor System platform, or the DS1007 PPC Processor Boards
that constitute the selected DS1007 platform, with their configuration
settings.
To display the memory settings of the selected platform. Memory Properties on page 337
To display information on the hardware that is assigned to the selected Online Details Properties on page 339
active member of the multiprocessor/multicore system, and state
information on the application process that is currently loaded to the
hardware.
To display the properties of the selected real-time application currently Real-Time Application Properties on page 340
loaded to the platform.
Related commands The DS1007 Processor Board platform provides the following
commands:
Purpose Refer to
To add a registered platform to the currently active project. Add to Active Experiment on page 397
To insert a platform/device into the active project or experiment. Insert Platform / Add Platform/Device on page 479
To add a new variable description, and (if applicable) a new ECU Image Add Variable Description ( ControlDesk
file, to a platform/device. Next Generation Variable Management)
To clear the flash memory of the selected platform, in whole or in part. Clear Flash on page 403
To configure the platform/device selected in ControlDesk and assign it to Configure Platform/Device on page 431
the available hardware or VEOS.
To establish a logical connection between ControlDesk and the selected Connect Platform/Device on page 467
platform/device hardware or VPU.
To add columns to the platform/device list or to remove them from it. Customize Columns (Platform/Device Manager)
on page 469
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
Purpose Refer to
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
To specify processor names for the boards of a DS1005based, Edit Processor Names on page 471
DS1006based, or DS1007based multiprocessor system.
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To save the flight recorder data currently available in a USB mass storage Explore to USB Flight Recorder on page 474
device connected to the platform hardware.
To filter the platform/device list. Filter on page 475
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To load an application to the RAM of the selected hardware or to VEOS. Real-Time Application / Offline Simulation
After downloading, the application is not started. Application - Load on page 508
To load an application to the selected hardware or VEOS, and start it Real-Time Application / Offline Simulation
automatically. Application - Load and Start on page 509
To load an application to the flash memory of the selected hardware. Real-Time Application - Load to Flash
After loading, the application is not started. (DS1007/MicroLabBox) on page 504
To load an application to the flash memory of the selected hardware, Real-Time Application - Load to Flash and Start
and start it automatically. (DS1007/MicroLabBox) on page 505
To reload the currently loaded application. After reloading, the Reload on page 520
application is not started.
To reload the currently loaded application. After reloading, the Reload and Start on page 520
application is started.
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start the selected application. Start on page 528
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop the selected application. Stop on page 530
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To unload the selected application. Unload on page 532
To update the firmware of the selected platform. Update Firmware on page 533
Feature overview For a feature overview of the DS1103 PPC Controller Board, refer to
Introduction to the Features of the DS1103 ( DS1103 Features).
Configuring the platform For instructions on configuring the platform, refer to Basics of
Handling Platforms on page 58.
Platform properties The DS1103 PPC Controller Board platform provides the following
properties and settings:
Purpose Refer to
To specify the assignment of the selected platform in the experiment to Assignment Properties on page 281
a registered platform.
To display details of the selected board. Board Details Properties on page 285
To specify common properties of the platform/device. Common Properties on page 301
To display the connection settings of the selected platform. Connection Settings Properties on page 304
To specify general settings of the selected platform/device. General Settings Properties on page 313
To display the memory settings of the selected platform. Memory Properties on page 337
To display the properties of the selected real-time application currently Real-Time Application Properties on page 340
loaded to the platform.
To display module version information for the selected platform. Version Properties on page 347
Related commands The DS1103 PPC Controller Board platform provides the following
commands:
Purpose Refer to
To add a registered platform to the currently active project. Add to Active Experiment on page 397
To insert a platform/device into the active project or experiment. Insert Platform / Add Platform/Device on page 479
To add a new variable description, and (if applicable) a new ECU Image Add Variable Description ( ControlDesk
file, to a platform/device. Next Generation Variable Management)
To configure the platform/device selected in ControlDesk and assign it to Configure Platform/Device on page 431
the available hardware or VEOS.
To establish a logical connection between ControlDesk and the selected Connect Platform/Device on page 467
platform/device hardware or VPU.
To add columns to the platform/device list or to remove them from it. Customize Columns (Platform/Device Manager)
on page 469
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
Purpose Refer to
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To filter the platform/device list. Filter on page 475
To load a real-time application to the RAM of the selected hardware, Real-Time Application - Load on page 502
and start it automatically.
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To reload the currently loaded application. Real-Time Application - Reload on page 506
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop the application running on the selected platform. Stop RTP on page 531
To update the firmware of the selected platform. Update Firmware on page 533
Feature overview For a feature overview of the DS1104 R&D Controller Board, refer to
Introduction to the Features of the DS1104 ( DS1104 Features).
Configuring the platform For instructions on configuring the platform, refer to Basics of
Handling Platforms on page 58.
Platform properties The DS1104 R&D Controller Board platform provides the following
properties and settings:
Purpose Refer to
To specify the assignment of the selected platform in the experiment to Assignment Properties on page 281
a registered platform.
To display details of the selected board. Board Details Properties on page 285
To specify common properties of the platform/device. Common Properties on page 301
To display the connection settings of the selected platform. Connection Settings Properties on page 304
To specify general settings of the selected platform/device. General Settings Properties on page 313
To display the memory settings of the selected platform. Memory Properties on page 337
To display the properties of the selected real-time application currently Real-Time Application Properties on page 340
loaded to the platform.
To display module version information for the selected platform. Version Properties on page 347
Related commands The DS1104 R&D Controller Board platform provides the following
commands:
Purpose Refer to
To insert a platform/device into the active project or experiment. Insert Platform / Add Platform/Device on page 479
To add a new variable description, and (if applicable) a new ECU Image Add Variable Description ( ControlDesk
file, to a platform/device. Next Generation Variable Management)
To clear the flash memory of the selected platform, in whole or in part. Clear Flash on page 403
To configure the platform/device selected in ControlDesk and assign it to Configure Platform/Device on page 431
the available hardware or VEOS.
To establish a logical connection between ControlDesk and the selected Connect Platform/Device on page 467
platform/device hardware or VPU.
To add columns to the platform/device list or to remove them from it. Customize Columns (Platform/Device Manager)
on page 469
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To filter the platform/device list. Filter on page 475
To load a real-time application to the RAM of the selected hardware, Real-Time Application - Load on page 502
and start it automatically.
To load an application to the flash memory of the selected hardware, Real-Time Application - Load to Flash
and start it automatically. (DS1005/DS1006/DS1104/MicroAutoBox)
on page 503
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To reload the currently loaded application. Real-Time Application - Reload on page 506
Purpose Refer to
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop the application running on the selected platform. Stop RTP on page 531
To update the firmware of the selected platform. Update Firmware on page 533
DS1202 MicroLabBox
Configuring the platform For instructions on configuring the platform, refer to Basics of
Handling Platforms on page 58.
Platform properties The DS1202 MicroLabBox platform provides the following properties
and settings:
Purpose Refer to
To specify the assignment of the selected platform in the experiment to Assignment Properties on page 281
a registered platform.
To display details of the selected board. Board Details Properties on page 285
To display hardware information on the selected component of the Board Hardware Properties on page 286
DS1007, MicroLabBox, or SCALEXIO system.
To display channel details of the selected FPGA I/O module of Channels Properties on page 301
MicroLabBox.
To specify common properties of the platform/device. Common Properties on page 301
To display the connection settings of the selected platform. Connection Settings Properties on page 304
To display information identifying the hardware-related software. Firmware Version Property on page 308
To display information on the selected FPGA module of MicroAutoBox FPGA Properties on page 312
or MicroLabBox or the userprogrammable FPGA base board.
To specify general settings of the selected platform/device. General Settings Properties on page 313
To display information on the host interface settings. Host Interface Properties on page 325
To display details on the selected component of the DS1007, Identification Properties on page 327
MicroLabBox or SCALEXIO system or VEOS simulator for identification
purposes.
To display information on the hardware that is assigned to the selected Online Details Properties on page 339
active member of the multiprocessor/multicore system, and state
information on the application process that is currently loaded to the
hardware.
To display the properties of the selected real-time application currently Real-Time Application Properties on page 340
loaded to the platform.
Purpose Refer to
To save the flight recorder data currently available in a USB mass storage Explore to USB Flight Recorder on page 474
device connected to the platform hardware.
To filter the platform/device list. Filter on page 475
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To load an application to the RAM of the selected hardware or to VEOS. Real-Time Application / Offline Simulation
After downloading, the application is not started. Application - Load on page 508
To load an application to the selected hardware or VEOS, and start it Real-Time Application / Offline Simulation
automatically. Application - Load and Start on page 509
To load an application to the flash memory of the selected hardware. Real-Time Application - Load to Flash
After loading, the application is not started. (DS1007/MicroLabBox) on page 504
To load an application to the flash memory of the selected hardware, Real-Time Application - Load to Flash and Start
and start it automatically. (DS1007/MicroLabBox) on page 505
To reload the currently loaded application. After reloading, the Reload on page 520
application is not started.
To reload the currently loaded application. After reloading, the Reload and Start on page 520
application is started.
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To unload the selected application. Unload on page 532
To update the firmware of the selected platform. Update Firmware on page 533
ECU Diagnostics
Managing tasks with the For information on managing tasks with the ECU Diagnostics device,
ECU Diagnostics device refer to Basics and Instructions on page 23.
Configuring the device For instructions on configuring the device, refer to ECU Diagnostics
Device Configuration on page 178.
Device properties The device provides the following properties and settings:
Purpose Refer to
To specify common properties of the platform/device. Common Properties on page 301
To specify diagnostics settings for the selected device. Diagnostics Settings Properties on page 306
To specify general settings of the selected platform/device. General Settings Properties on page 313
To select logical links for ECU diagnostics, to display the active logical Logical Link Selection Properties on page 333
links of the ECU Diagnostics device with their configurations, and to
specify connection check settings and configure communication
parameters individually for each active logical link.
To display and configure the ODX database specified for the selected Active ODX Database / ODX Database Properties
ECU Diagnostics device. on page 279
To display the vehicle that is selected to be used with the selected ECU Vehicle Selection Properties on page 345
Diagnostics device and to select another vehicle.
Related commands The ECU Diagnostics device provides the following commands:
Purpose Refer to
To add a new diagnostics database to the selected ECU Diagnostics Add ODX Database on page 372
device.
To insert a platform/device into the active project or experiment. Insert Platform / Add Platform/Device on page 479
To configure the platform/device selected in ControlDesk and assign it to Configure Platform/Device on page 431
the available hardware or VEOS.
To establish a logical connection between ControlDesk and the selected Connect Platform/Device on page 467
platform/device hardware or VPU.
Purpose Refer to
To add columns to the platform/device list or to remove them from it. Customize Columns (Platform/Device Manager)
on page 469
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To filter the platform/device list. Filter on page 475
To execute an ECU flash programming operation based on an ODX Flash ECU (ECU Diagnostics) on page 477
database and diagnostic protocol.
To import the entire contents of a data set container (variable Import Data Set Container ( ControlDesk
description, data sets, ECU Image files). Next Generation Calibration and Data Set
Management)
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
n FIBEX
n AUTOSAR system description
Configuring the device For instructions on configuring the device, refer to How to Configure
a FlexRay Bus Monitoring Device on page 162.
Device properties The device provides the following properties and settings:
Purpose Refer to
To specify common properties of the platform/device. Common Properties on page 301
To select the FlexRay interface type for the selected device. FlexRay Interface Properties on page 308
To specify FlexRay-specific settings for the selected device. FlexRay Settings Properties on page 309
To specify general settings of the selected platform/device. General Settings Properties on page 313
Related commands The FlexRay Bus Monitoring device provides the following commands:
Purpose Refer to
To insert a platform/device into the active project or experiment. Insert Platform / Add Platform/Device on page 479
To add a new variable description, and (if applicable) a new ECU Image Add Variable Description ( ControlDesk
file, to a platform/device. Next Generation Variable Management)
To configure the platform/device selected in ControlDesk and assign it to Configure Platform/Device on page 431
the available hardware or VEOS.
To establish a logical connection between ControlDesk and the selected Connect Platform/Device on page 467
platform/device hardware or VPU.
To add columns to the platform/device list or to remove them from it. Customize Columns (Platform/Device Manager)
on page 469
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To filter the platform/device list. Filter on page 475
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
Purpose Refer to
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
LIN Bus Monitoring device A device that monitors the data stream
on a LIN bus connected to the ControlDesk PC.
The LIN Bus Monitoring device works, for example, with PC-based LIN
interfaces.
The device supports the following variable description file types:
n LDF
n FIBEX
n AUTOSAR system description
Configuring the device For instructions on configuring the device, refer to Bus Device
Configuration on page 158.
Device properties The device provides the following properties and settings:
Purpose Refer to
To specify common properties of the platform/device. Common Properties on page 301
To specify general settings of the selected platform/device. General Settings Properties on page 313
To specify inheritance settings for the selected device. Inheritance Settings Properties on page 329
To select the LIN interface type for the selected device. LIN Interface Properties on page 331
To specify LIN settings for the selected device. LIN Settings Properties on page 332
Related commands The LIN Bus Monitoring device provides the following commands:
Purpose Refer to
To insert a platform/device into the active project or experiment. Insert Platform / Add Platform/Device on page 479
To add a new variable description, and (if applicable) a new ECU Image Add Variable Description ( ControlDesk
file, to a platform/device. Next Generation Variable Management)
Purpose Refer to
To configure the platform/device selected in ControlDesk and assign it to Configure Platform/Device on page 431
the available hardware or VEOS.
To establish a logical connection between ControlDesk and the selected Connect Platform/Device on page 467
platform/device hardware or VPU.
To add columns to the platform/device list or to remove them from it. Customize Columns (Platform/Device Manager)
on page 469
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To filter the platform/device list. Filter on page 475
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
MicroAutoBox
Configuring the platform For instructions on configuring the platform, refer to Basics of
Handling Platforms on page 58.
Platform properties The platform provides the following properties and settings:
Purpose Refer to
To specify the assignment of the selected platform in the experiment to Assignment Properties on page 281
a registered platform.
To display details of the selected board. Board Details Properties on page 285
To specify common properties of the platform/device. Common Properties on page 301
To display the connection settings of the selected platform. Connection Settings Properties on page 304
To display information on the selected FPGA module of MicroAutoBox FPGA Properties on page 312
or MicroLabBox or the userprogrammable FPGA base board.
To specify general settings of the selected platform/device. General Settings Properties on page 313
To display details of the selected I/O board of MicroAutoBox. I/O Board Properties on page 326
To display details of the selected I/O module. I/O Module Details Properties on page 326
To display the memory settings of the selected platform. Memory Properties on page 337
To display the properties of the selected real-time application currently Real-Time Application Properties on page 340
loaded to the platform.
To display module version information for the selected platform. Version Properties on page 347
Purpose Refer to
To load a real-time application to the RAM of the selected hardware, Real-Time Application - Load on page 502
and start it automatically.
To load an application to the flash memory of the selected hardware, Real-Time Application - Load to Flash
and start it automatically. (DS1005/DS1006/DS1104/MicroAutoBox)
on page 503
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To reload the currently loaded application. Real-Time Application - Reload on page 506
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To display the system times of MicroAutoBox and the host PC, and to Set MicroAutoBox System Time on page 526
set the system time on MicroAutoBox to the system time of the host PC.
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop the application running on the selected platform. Stop RTP on page 531
To update the firmware of the selected platform. Update Firmware on page 533
To upload flight recorder data and save it to a measurement file. Upload Flash Flightrecorder Contents on page 537
Multiprocessor System
Configuring the platform For instructions on configuring the platform, refer to Basics of
Handling Platforms on page 58.
For further general information on working with multiprocessor
systems based on DS1005 or DS1006 processor boards, refer to
Multiprocessor System Platform Configuration on page 96.
Platform properties The Multiprocessor System platform provides the following properties
and settings:
Purpose Refer to
To specify the assignment of the selected platform in the experiment to Assignment Properties on page 281
a registered platform.
To specify common properties of the platform/device. Common Properties on page 301
To specify general settings of the selected platform/device. General Settings Properties on page 313
To display the DS1005/DS1006 processor boards that form the selected Member Overview Properties on page 335
Multiprocessor System platform, or the DS1007 PPC Processor Boards
that constitute the selected DS1007 platform, with their configuration
settings.
To display the processor boards of the multiprocessor system and their Topology Information Properties on page 342
interconnections via Gigalinks.
Purpose Refer to
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop the applications running on the selected Multiprocessor System Stop RTPs on page 531
platform.
To update the firmware of the selected platform. Update Firmware on page 533
SCALEXIO
Configuring the platform For instructions on configuring the platform, refer to Basics of
Handling Platforms on page 58.
For further general information on working with a SCALEXIO
platform, refer to SCALEXIO Platform Configuration on page 104.
Platform properties The platform provides the following properties and settings:
Purpose Refer to
To specify the assignment of the selected platform in the experiment to Assignment Properties on page 281
a registered platform.
To display the properties of the backplane. Backplane Properties on page 284
To display hardware information on the selected component of the Board Hardware Properties on page 286
DS1007, MicroLabBox, or SCALEXIO system.
To specify common properties of the platform/device. Common Properties on page 301
To display information on the failrail segment switch. Failrail Segment Switch Properties on page 308
To display information identifying the hardware-related software. Firmware Version Property on page 308
To display information on the selected FPGA module of MicroAutoBox FPGA Properties on page 312
or MicroLabBox or the userprogrammable FPGA base board.
To specify general settings of the selected platform/device. General Settings Properties on page 313
To display information on the host interface settings. Host Interface Properties on page 325
To display details on the selected component of the DS1007, Identification Properties on page 327
MicroLabBox or SCALEXIO system or VEOS simulator for identification
purposes.
To display the properties of the unit's IOCNET router. IOCNET Router Properties on page 331
Purpose Refer to
To display information on the hardware that is assigned to the selected Online Details Properties on page 339
active member of the multiprocessor/multicore system, and state
information on the application process that is currently loaded to the
hardware.
To display the properties of the selected real-time application currently Real-Time Application Properties on page 340
loaded to the platform.
To display information on the speed for an angle operating range of Speed Properties on page 342
360 / 720 for the selected SCALEXIO angle unit.
To display information on the uplink and downlink connections. Uplink and Downlink Connections Properties
on page 344
Purpose Refer to
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To replace the application of the platform. Replace Application on page 525
To start the selected application. Start on page 528
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop the selected application. Stop on page 530
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To unload the selected application. Unload on page 532
To update the firmware of the selected platform. Update Firmware on page 533
VEOS
Configuring the platform For instructions on configuring the platform, refer to Basics of
Handling Platforms on page 58.
Platform properties The VEOS platform provides the following properties and settings:
Purpose Refer to
To specify the assignment of the selected platform in the experiment to Assignment Properties on page 281
a registered platform.
To specify common properties of the platform/device. Common Properties on page 301
To specify general settings of the selected platform/device. General Settings Properties on page 313
To display details on the selected component of the DS1007, Identification Properties on page 327
MicroLabBox or SCALEXIO system or VEOS simulator for identification
purposes.
To display information on the hardware that is assigned to the selected Online Details Properties on page 339
active member of the multiprocessor/multicore system, and state
information on the application process that is currently loaded to the
hardware.
To display the properties of the offline simulation application that is VEOS Simulation Properties on page 345
currently loaded to the platform.
To specify timing settings for the VEOS simulation for the selected VEOS Simulation Time Options Properties
platform. on page 346
To display the properties of the selected VPU. VPU Properties on page 348
Purpose Refer to
To load an application to the selected hardware or VEOS, and start it Real-Time Application / Offline Simulation
automatically. Application - Load and Start on page 509
To reload the currently loaded application. Reload Application on page 521
To reload the currently loaded application. After reloading, the Reload on page 520
application is not started.
To reload the currently loaded application. After reloading, the Reload and Start on page 520
application is started.
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To remove an application from the platform. Remove Application on page 523
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To replace the application of the platform. Replace Application on page 525
To run a pausing or stopped offline simulation stepwise. Single Step on page 528
To start the selected application. Start on page 528
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop the selected application. Stop on page 530
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To unload the selected application. Unload on page 532
Video Capturing
Configuring the device For instructions on configuring the device, refer to How to Configure
Video Capturing Devices on page 206.
Introduction to the Video For an introduction, refer to Basics on Video Capturing Devices
Capturing device on page 203.
Device properties The device provides the following properties and settings:
Purpose Refer to
To specify the advanced settings of the device. Advanced Settings Properties on page 280
To specify the audio settings of the device. Audio Settings Properties on page 284
To specify the camera properties of the device. Camera Properties on page 288
To display the camera characteristics of the device. Camera Characteristics Properties on page 287
To specify the camera control settings. Camera Control Settings Properties on page 287
To specify the camera settings of the device. Camera Settings Properties on page 289
To specify the capture mode settings of the device. Capture Mode Settings Properties on page 292
To specify common properties of the platform/device. Common Properties on page 301
To specify the compression settings of the device. Compression Settings Properties on page 304
To specify the image quality settings of the device. Image Quality Settings Properties on page 328
Related commands The Video Capturing device provides the following commands:
Purpose Refer to
To insert a platform/device into the active project or experiment. Insert Platform / Add Platform/Device on page 479
To configure the platform/device selected in ControlDesk and assign it to Configure Platform/Device on page 431
the available hardware or VEOS.
To establish a logical connection between ControlDesk and the selected Connect Platform/Device on page 467
platform/device hardware or VPU.
To add columns to the platform/device list or to remove them from it. Customize Columns (Platform/Device Manager)
on page 469
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To filter the platform/device list. Filter on page 475
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
Purpose Refer to
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
XCP on CAN
Introduction to XCP and the For an introduction, refer to Introduction to the Features of XCP
XCP devices ( XCP Feature Reference).
Configuring the device For instructions on configuring the device, refer to How to Configure
an XCP on CAN Device on page 211.
Device properties The device provides the following properties and settings:
Purpose Refer to
To select the CAN interface for the selected device. CAN Interface Properties on page 290
To specify CAN settings for the selected CANbased device. CAN Settings Properties on page 291
To specify common properties of the platform/device. Common Properties on page 301
Purpose Refer to
To specify ECU-specific settings for the selected device. ECU Information Properties on page 306
To specify general settings of the selected platform/device. General Settings Properties on page 313
To specify inheritance settings for the selected device. Inheritance Settings Properties on page 329
To specify XCP on CANspecific communication settings for the selected XCP on CAN Settings Properties on page 349
device.
To specify advanced settings for the selected XCP or DCIGSI2 device. XCP/GSI2 Settings Advanced Properties
on page 353
To specify checksum calculation settings for the selected XCP or XCP/GSI2 Settings Checksum Calculation Properties
DCIGSI2 device. on page 358
To prepare ControlDesk and the ECU for quick start measurement. XCP/GSI2 Settings Prepare Quick Start Property
on page 360
To specify quick start settings for the selected XCP or DCIGSI2 device. XCP/GSI2 Settings Quick Start Property
on page 361
To specify seed and key settings for the selected XCP device. XCP Settings Seed and Key Settings Properties
on page 353
Related commands The XCP on CAN device provides the following commands:
Purpose Refer to
To save calibration data from the active memory page to the ECUs Activate Data Page Freezing on page 368
nonvolatile memory.
To insert a platform/device into the active project or experiment. Insert Platform / Add Platform/Device on page 479
To add a new variable description, and (if applicable) a new ECU Image Add Variable Description ( ControlDesk
file, to a platform/device. Next Generation Variable Management)
To initiate a consistency check (EPK check) manually. Check EPK on page 401
To clear the quick start measurement configuration in the ECUs Clear Quick Start Configuration on page 404
nonvolatile memory.
To configure the platform/device selected in ControlDesk and assign it to Configure Platform/Device on page 431
the available hardware or VEOS.
To establish a logical connection between ControlDesk and the selected Connect Platform/Device on page 467
platform/device hardware or VPU.
To copy the reference page to the working page. Copy Reference Page to Working Page
( ControlDesk Next Generation Calibration and
Data Set Management)
To copy the working page to the reference page. Copy Working Page to Reference Page
( ControlDesk Next Generation Calibration and
Data Set Management)
To add columns to the platform/device list or to remove them from it. Customize Columns (Platform/Device Manager)
on page 469
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To filter the platform/device list. Filter on page 475
To open the dSPACE ECU Flash Programming Tool. Flash ECU on page 476
Purpose Refer to
To import the entire contents of a data set container (variable Import Data Set Container ( ControlDesk
description, data sets, ECU Image files). Next Generation Calibration and Data Set
Management)
To view, customize, add, and delete memory segments of the memory Memory Segments on page 489
of the selected device.
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
XCP on Ethernet
Introduction to XCP and the For an introduction, refer to Introduction to the Features of XCP
XCP devices ( XCP Feature Reference).
Configuring the device For instructions on configuring the device, refer to How to Configure
an XCP on Ethernet Device on page 215.
Device properties The device provides the following properties and settings:
Purpose Refer to
To specify common properties of the platform/device. Common Properties on page 301
To specify ECU-specific settings for the selected device. ECU Information Properties on page 306
To specify Ethernet settings for the selected platform/device. Ethernet Settings Properties on page 307
To specify general settings of the selected platform/device. General Settings Properties on page 313
To specify inheritance settings for the selected device. Inheritance Settings Properties on page 329
To specify network adapter settings for the selected platform/device. Network Adapter Properties on page 338
To specify the settings of the transport layer on the ECU with XCP/DCI- Transport Layer Settings Properties on page 343
GSI2.
To specify the communication settings of the selected platform/device. XCP on Ethernet/GSI2 Ethernet Settings Properties
on page 350
To specify advanced settings for the selected XCP or DCIGSI2 device. XCP/GSI2 Settings Advanced Properties
on page 353
To specify checksum calculation settings for the selected XCP or XCP/GSI2 Settings Checksum Calculation Properties
DCIGSI2 device. on page 358
To prepare ControlDesk and the ECU for quick start measurement. XCP/GSI2 Settings Prepare Quick Start Property
on page 360
To specify quick start settings for the selected XCP or DCIGSI2 device. XCP/GSI2 Settings Quick Start Property
on page 361
To specify seed and key settings for the selected XCP device. XCP Settings Seed and Key Settings Properties
on page 353
Related commands The XCP on Ethernet device provides the following commands:
Purpose Refer to
To save calibration data from the active memory page to the ECUs Activate Data Page Freezing on page 368
nonvolatile memory.
To insert a platform/device into the active project or experiment. Insert Platform / Add Platform/Device on page 479
To add a new variable description, and (if applicable) a new ECU Image Add Variable Description ( ControlDesk
file, to a platform/device. Next Generation Variable Management)
To initiate a consistency check (EPK check) manually. Check EPK on page 401
To clear the quick start measurement configuration in the ECUs Clear Quick Start Configuration on page 404
nonvolatile memory.
To configure the platform/device selected in ControlDesk and assign it to Configure Platform/Device on page 431
the available hardware or VEOS.
To establish a logical connection between ControlDesk and the selected Connect Platform/Device on page 467
platform/device hardware or VPU.
To copy the reference page to the working page. Copy Reference Page to Working Page
( ControlDesk Next Generation Calibration and
Data Set Management)
Purpose Refer to
To copy the working page to the reference page. Copy Working Page to Reference Page
( ControlDesk Next Generation Calibration and
Data Set Management)
To add columns to the platform/device list or to remove them from it. Customize Columns (Platform/Device Manager)
on page 469
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To filter the platform/device list. Filter on page 475
To open the dSPACE ECU Flash Programming Tool. Flash ECU on page 476
To import the entire contents of a data set container (variable Import Data Set Container ( ControlDesk
description, data sets, ECU Image files). Next Generation Calibration and Data Set
Management)
To view, customize, add, and delete memory segments of the memory Memory Segments on page 489
of the selected device.
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
XCP on FlexRay
Introduction to XCP and the For an introduction, refer to Introduction to the Features of XCP
XCP devices ( XCP Feature Reference).
Configuring the device For instructions on configuring the device, refer to How to Configure
an XCP on FlexRay Device on page 217.
Device properties The device provides the following properties and settings:
Purpose Refer to
To specify common properties of the platform/device. Common Properties on page 301
To specify ECU-specific settings for the selected device. ECU Information Properties on page 306
To select the FlexRay interface type for the selected device. FlexRay Interface Properties on page 308
To specify FlexRay-specific settings for the selected device. FlexRay Settings Properties on page 309
To specify general settings of the selected platform/device. General Settings Properties on page 313
To specify the settings of the transport layer on the ECU with XCP/DCI- Transport Layer Settings Properties on page 343
GSI2.
To specify XCP on FlexRayspecific communication settings for the XCP on FlexRay Settings Properties on page 351
selected device.
To specify advanced settings for the selected XCP or DCIGSI2 device. XCP/GSI2 Settings Advanced Properties
on page 353
To specify checksum calculation settings for the selected XCP or XCP/GSI2 Settings Checksum Calculation Properties
DCIGSI2 device. on page 358
To prepare ControlDesk and the ECU for quick start measurement. XCP/GSI2 Settings Prepare Quick Start Property
on page 360
To specify quick start settings for the selected XCP or DCIGSI2 device. XCP/GSI2 Settings Quick Start Property
on page 361
To specify seed and key settings for the selected XCP device. XCP Settings Seed and Key Settings Properties
on page 353
Related commands The XCP on FlexRay device provides the following commands:
Purpose Refer to
To insert a platform/device into the active project or experiment. Insert Platform / Add Platform/Device on page 479
To add a new variable description, and (if applicable) a new ECU Image Add Variable Description ( ControlDesk
file, to a platform/device. Next Generation Variable Management)
To initiate a consistency check (EPK check) manually. Check EPK on page 401
Purpose Refer to
To configure the platform/device selected in ControlDesk and assign it to Configure Platform/Device on page 431
the available hardware or VEOS.
To establish a logical connection between ControlDesk and the selected Connect Platform/Device on page 467
platform/device hardware or VPU.
To copy the reference page to the working page. Copy Reference Page to Working Page
( ControlDesk Next Generation Calibration and
Data Set Management)
To copy the working page to the reference page. Copy Working Page to Reference Page
( ControlDesk Next Generation Calibration and
Data Set Management)
To add columns to the platform/device list or to remove them from it. Customize Columns (Platform/Device Manager)
on page 469
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To filter the platform/device list. Filter on page 475
To import the entire contents of a data set container (variable Import Data Set Container ( ControlDesk
description, data sets, ECU Image files). Next Generation Calibration and Data Set
Management)
To view, customize, add, and delete memory segments of the memory Memory Segments on page 489
of the selected device.
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
Configuring the platform For instructions on registering and configuring the platform, refer to
XIL API MAPort Platform Configuration on page 111.
Platform properties The platform provides the following properties and settings:
Purpose Refer to
To specify the assignment of the selected platform in the experiment to Assignment Properties on page 281
a registered platform.
To specify common properties of the platform/device. Common Properties on page 301
To specify general settings of the selected platform/device. General Settings Properties on page 313
To display information on the model access port (XIL API MAPort) Model Access Port Properties on page 337
implementation that is used.
Related commands The XIL API MAPort platform provides the following commands:
Purpose Refer to
To add a registered platform to the currently active project. Add to Active Experiment on page 397
To insert a platform/device into the active project or experiment. Insert Platform / Add Platform/Device on page 479
To add a new variable description, and (if applicable) a new ECU Image Add Variable Description ( ControlDesk
file, to a platform/device. Next Generation Variable Management)
To configure the platform/device selected in ControlDesk and assign it to Configure Platform/Device on page 431
the available hardware or VEOS.
To establish a logical connection between ControlDesk and the selected Connect Platform/Device on page 467
platform/device hardware or VPU.
To add columns to the platform/device list or to remove them from it. Customize Columns (Platform/Device Manager)
on page 469
To deactivate the platform/device in the experiment. Disable Platform/Device on page 469
To stop communication between ControlDesk and the hardware or Disconnect Platform/Device on page 471
VEOS that belongs to the selected platform/device.
To activate the platform/device in the experiment. Enable Platform/Device on page 473
To filter the platform/device list. Filter on page 475
Purpose Refer to
To import the entire contents of a data set container (variable Import Data Set Container ( ControlDesk
description, data sets, ECU Image files). Next Generation Calibration and Data Set
Management)
To disconnect the MAPort. MAPort - Disconnect on page 486
To configure the MAPort with an MAPort configuration. MAPort - Load and Configure on page 487
To reload the currently loaded MAPort configuration to the selected MAPort - Reload on page 488
MAPort.
To view the properties of the selected platform/device. Properties (Platform/Device) on page 501
To remove an item from the currently loaded project. Remove (from Project) ( ControlDesk
Next Generation Project and Experiment
Management)
To change the name of the selected platform/device in the experiment. Rename Platform/Device on page 524
To start the simulation at the MAPort. Start (XIL API MAPort) on page 529
To start online calibration and measurement for the currently selected Start Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To start measurement for the selected platform/device. Start Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To start online calibration for the selected platform/device. Start Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
To stop the simulation at the MAPort. Stop (XIL API MAPort) on page 530
To stop measurement and online calibration for the currently selected Stop Calibration & Measurement (for Single
platform/device. Platform/Device) ( ControlDesk Next Generation
Measurement and Recording)
To stop measurement for the currently selected platform/device. Stop Measurement (for Single Platform/Device)
( ControlDesk Next Generation Measurement
and Recording)
To stop online calibration for the selected platform/device. Stop Online Calibration (for Single Platform/Device)
( ControlDesk Next Generation Calibration and
Data Set Management)
Platform/Device-Related Properties
Note
In the operator mode, none of the properties related to
platforms/devices can be changed. All the properties are read-
only.
Purpose To display and configure the ODX database specified for the selected
ECU Diagnostics device.
Note
For ODX 2.2.0 diagnostics databases, database optimization is
always performed. You cannot change this setting. So if you
work with an ODX 2.2.0 database, ControlDesk always uses the
binary format instead of ODX data for the diagnostics database.
Select ODX files (Available only for the currently active ODX
database of an ECU Diagnostics device) Displays the name of the
currently active diagnostics database of the ECU Diagnostics device
and lets you open the Select ODX Files dialog to modify the active
database. Refer to Select ODX Files page on page 373.
Selected ODX template (Available only for the currently active
ODX database of an ECU Diagnostics device) Displays the name of the
database template selected for the active ODX database. If no ODX
template is assigned to the active ODX database, 'No ODX database
template selected.' is displayed.
Related devices These properties are available for the following devices:
n ECU Diagnostics on page 251
Properties Transport buffer size (Available only if the Use custom size
property is activated) Lets you specify the size of the image buffer (in
KBytes) used to transport the video data. If you use the Integrated
capture mode, the image buffer size equals the measurement array
size.
Related devices These properties are available for the following devices:
n Video Capturing on page 265
Assignment Properties
Properties Alias name Lets you specify the alias name of the connection that is
used for assignment.
Board name Lets you specify the board name used to identify the
board or processing unit.
Connection type Lets you specify the connection type of the
platform hardware.
n Select BUS if the platform hardware is installed in the host PC or in
an expansion box connected to the host PC via a bus interface.
n Select NET if the platform hardware is connected to the host PC
via Ethernet.
IP address / Net client Lets you specify the network client for
assignment as an IP address.
or
Lets you specify the network client for assignment as an IP address or
alias.
MAC address Lets you specify the MAC address of the selected
processing unit of the SCALEXIO system, the selected processor board
of the DS1007 platform, or selected platform of the DS1202
MicroLabBox platform. The MAC address is used to uniquely identify
the hardware.
Mode Lets you select the assignment mode for the platform. The
available assignment modes depend on the platform type.
Assignment Description
Mode
Assign to first (Not available for the Multiprocessor System platform) ControlDesk automatically assigns the platform to the
available platform first registered and unassigned platform of the relevant platform type it finds.
Assign to any ControlDesk assigns the platform to a registered and unassigned platform of the relevant platform type,
equal platform according to the following assignment settings:
n Alias name
n Board name
n Connection type
n Net client
n Port address
n XIL API MAPort implementation
The above assignment settings are platform-type-specific. The list below shows the settings available for the
platform types:
n DS1005, DS1006, DS1103: Port address and/or Board name, Connection type, Net Client (only for the
Net connection type)
n DS1104: Board name
n MicroAutoBox: Board name (optional), Connection type, Net Client
n Multiprocessor System: Connection type
Multiprocessor System members: Port address
n DS1007, DS1202 MicroLabBox, SCALEXIO: IP address or Board name
n VEOS: none
n XIL API MAPort platform: XIL API MAPort implementation
Assign to identical (Not available for the VEOS and XIL API MAPort platforms) ControlDesk assigns the platform to registered
platform and unassigned dSPACE hardware of the relevant platform type, according to the following assignment
settings:
n Connection type
n Serial number
n MAC address
The above assignment settings are platform-type-specific. The list below shows the settings available for the
platform types:
n DS1005, DS1006, DS1103, DS1104, MicroAutoBox, Multiprocessor System members: Serial number
n Multiprocessor System: Connection type
Multiprocessor System members: Serial number
n DS1007, DS1202 MicroLabBox, SCALEXIO: MAC address
Note
If several platforms are assigned to dSPACE hardware in one step
(for example, if you call the Refresh Platform Configuration
command), the assignment modes are applied to the platforms
in a certain order:
1. Assign to identical platform
2. Assign to any equal platform
3. Assign to first available platform
Related platforms These properties are available for the following platforms:
n DS1005 PPC Board on page 238
n DS1006 Processor Board on page 240
n DS1007 PPC Processor Board on page 242
n DS1103 PPC Controller Board on page 245
n DS1104 R&D Controller Board on page 246
n DS1202 MicroLabBox on page 248
n MicroAutoBox on page 255
n Multiprocessor System on page 258
n SCALEXIO on page 260
n VEOS on page 262
n XIL API MAPort on page 273
Properties Audio codec (Available only in Separate capture mode) Lets you
choose an audio codec to compress audio data. If audio data capture
is enabled, you can select any of the audio codecs that are installed
on the host PC for the Video Capturing device.
Audio device (Available only in Separate capture mode) Lets you
select the audio device, if audio data capture is enabled. The list
contains all the audio devices that are currently connected to the
host PC (microphones integrated in the connected cameras and
stand-alone microphones). If you have selected a virtual camera to
stream video data, Virtual Audio is displayed. If audio data capture is
disabled, 'No Audio' is displayed.
Audio format (Available only in Separate capture mode) Lets you
specify the audio format to be used. If audio data capture is enabled,
you can select a suitable combination of sample rate, bits per sample,
and mono or stereo mode from the list.
Capture audio (Available only in Separate capture mode) Lets you
enable or disable the capturing of audio data. If you select the
checkbox, you can specify further configuration settings for audio
data capture. If the checkbox is cleared, no audio data is captured
with the Video Capturing device.
Related devices These properties are available for the following devices:
n Video Capturing on page 265
Backplane Properties
Related platforms These properties are available for the following platforms:
n SCALEXIO on page 260
Related platforms These properties are available for the following platforms:
n DS1005 PPC Board on page 238
n DS1006 Processor Board on page 240
n DS1007 PPC Processor Board on page 242
n DS1103 PPC Controller Board on page 245
n DS1104 R&D Controller Board on page 246
n DS1202 MicroLabBox on page 248
n MicroAutoBox on page 255
Related platforms These properties are available for the following platforms:
n DS1007 PPC Processor Board on page 242
n DS1202 MicroLabBox on page 248
n SCALEXIO on page 260
Properties Data rate Displays the data rate for placing data in the
measurement data file in MByte/min. The rate depends on the
selected capture mode, the resolution of the video, the frame rate
and other parameters. Note that the data rate is not calculated in real
time. If you change parameters that influence the data rate, such as
the resolution of the video, it may take a moment until the data rate
is refreshed.
Exposure time range Displays the camera's minimal and maximal
supported exposure time for each image frame in ms.
Frame rate range Displays the camera's minimal and maximal
supported frames per second [fps]. The framerate range depends on
the selected capture mode.
Viewport height range Displays the camera's minimal and
maximal viewport height in pixels [px].
Viewport width range Displays the camera's minimal and maximal
viewport width in pixels [px].
Related devices These properties are available for the following devices:
n Video Capturing on page 265
Properties Focus Lets you specify the focus value in millimeters [mm]. Select
Automatic to enable autofocus.
Iris Lets you specify the iris value in millimeters [mm]. The iris is an
adjustable opening which controls the amount of light passing the
lens.
Pan Lets you specify the pan (horizontal) angle value in degrees [].
Reset category to default Lets you set all the Camera Control
Settings properties to their default values.
Roll Lets you specify the roll angle value in degrees [].
Tilt Lets you specify the tilt (vertical) angle value in degrees [].
Zoom Lets you specify the zoom value in millimeters [mm].
Related devices These properties are available properties for the following devices:
n Video Capturing on page 265
Camera Properties
Related devices These properties are available for the following devices:
n Video Capturing on page 265
Note
If you place the camera in a dark environment while the
AutoExposure property is active, the exposure time for each
single frame is raised. This may lower the frame rate of the
video.
Color mode Lets you select one of the following color modes:
n RGB 24 bit color
n Grayscale 8 bit
This property affects the quality of your video as well as the amount
of size it requires.
Exposure time (Available only if the Auto Exposure property is
deactivated) Lets you specify how long the camera is exposed to light
in ms. Cameras in dark environments need more exposure time than
cameras in well-lit environments.
Flip horizontal Lets you flip the image horizontally.
Flip vertical Lets you flip the image vertically.
Frame rate Lets you specify the camera's frame rate in frames per
second [fps]. Depending on the lighting conditions of the
environment, the camera will then try to achieve the nominal values.
This property affects the quality of your video as well as the amount
of size it requires.
Height Lets you specify the height of the video. This property
affects the quality of your video as well as the amount of size it
requires.
Reset category to default Lets you set all the Camera Settings
properties to their default values.
Viewport Lets you specify the viewport of the image.
Width Lets you specify the width of the video. This property affects
the quality of your video as well as the amount of size it requires.
Related devices These properties are available for the following devices:
n Video Capturing on page 265
Properties Interface search attributes Lets you specify the search attributes
for interface selection.
Interface selection Lets you select the type of the CAN interface.
Refer to Interface Selection (CAN-, LIN-, and FlexRay-based devices)
page on page 451.
IP address Lets you enter the IP address used as the search attribute
value for interface selection. CAN interfaces which have this IP
address are searched for. The found interfaces are displayed for
selection in the Interface Selection dialog.
IP addresses Lets you specify IP addresses as search attributes for
CAN interface selection. Select Add in the context menu or click
to add an edit field to specify an IP address, or click to delete the
selected IP address.
Related devices These properties are available for the following devices:
n CAN Bus Monitoring on page 231
n CCP on page 233
n XCP on CAN on page 266
Properties Baud rate (Not available for the ECU Diagnostics device) Lets you
specify the baud rate.
Note
The baud rate must be the same for each bus member of a CAN
bus.
Bit time segment 1 Lets you specify the period of time before the
sample point in tq (time quantum).
Bit time segment 2 Lets you specify the period of time after the
sample point in tq (time quantum).
CAN Lets you specify CAN settings for the selected CAN-based
device. The CAN settings are used to define the standard data rate.
CAN FD Lets you specify CAN FD settings for the selected CAN-
based device. The CAN FD settings are used to define the data rate
for the data phase. The data phase can be configured to have a
higher bit rate than the arbitration phase. During the arbitration
process, the standard data rate is used.
Clock frequency Lets you specify the clock frequency.
Enabled Lets you enable CAN FD mode. If the checkbox is selected,
you can configure the data rate for the data phase of CAN FD
messages.
Nominal bit time Lets you specify the time period of one bit in tq
(time quantum). The nominal bit time consists of two time segments
(time segment 1 and 2) and a synchronization segment.
1 bit time
Sync-
Seg TSeg1 TSeg2
Prescaler Lets you specify the value of the baud rate prescaler.
Sample point Lets you specify the sample point within the bit time,
that is, the point in time at which the bus voltage level (CAN-H, CAN-
L) is read and interpreted as a bit value.
Samples Lets you specify the number of samples per bit for the
selected device.
n When you select '1', the CAN controller of the selected device
samples each bit once to decide whether it is recessive or
dominant.
n When you select '3', the CAN controller of the selected device
samples a bit three times and uses the majority to decide if a bit is
recessive or dominant.
Synchronization jump width Lets you specify the synchronization
jump width in tq (time quantum), which defines how far the CAN
controller can shift the location of the sample point to synchronize
itself to the other bus members.
Related devices These properties are available for the following devices:
n CAN Bus Monitoring on page 231
n CCP on page 233
n XCP on CAN on page 266
Properties Capture mode Lets you specify one of the following modes of
capturing video data:
Note
To record large videos with high resolution and high quality,
it is recommended to use the Separate capture mode to
reduce the size of the measurement data files. However, to
work with large MF4 or IDF files in ControlDesk, you can split
them using the DSSIGCONV tool. Refer to How to Extract
Data from a Measurement Data File ( ControlDesk
Next Generation Measurement and Recording).
Note
Video data saved separately with the Separate capture mode
is not saved with the Save Buffer command.
Related devices These properties are available for the following devices:
n Video Capturing on page 265
Properties Read CCP settings from A2L Lets you specify to use the CCP
service configuration information from a variable description that you
add or reload. Using information from the new/reloaded variable
description overwrites the configuration information that is currently
used by the device. If there are inconsistencies between the currently
used configuration information and the corresponding information
contained in the new/reloaded A2L file, a dialog opens for you to
specify whether to still use the current value or to use the value from
the new/reloaded A2L file for each single inconsistent ECU interface
setting.
n If enabled, ControlDesk reads the CCP service configuration
information from the new/reloaded A2L file. If this differs from the
currently used ECU interface settings, ControlDesk lets you specify
whether to use the current value or the value from the
new/reloaded variable description for each single ECU interface
setting concerned.
n If disabled, ControlDesk does not read the CCP service
configuration information from the new/reloaded variable
description, but continues to use the ECU interface settings
currently used by the device.
Read CCP settings from ECU Lets you enable or disable the upload
of CCP service configuration information from the ECU when the
CCP device connects to the ECU. Uploading information from the
ECU overwrites the configuration information that is currently used by
the device. If there are inconsistencies between the currently used
configuration information and the corresponding configuration
information on the ECU, a dialog opens for you to specify whether to
use the current value or to upload the value from the ECU for each
single inconsistent ECU interface setting.
n If enabled, ControlDesk reads CCP service configuration
information from the ECU when the CCP device connects to the
ECU. If it differs from the currently used ECU interface settings,
you can select to use the current value or upload the value from
the ECU for each inconsistent setting.
n If disabled, ControlDesk does not read the CCP service
configuration information from the ECU, but continues to use the
ECU interface settings currently used by the device.
Cyclic status detection Lets you enable or disable the cyclic
transmission of ECU status detection requests. If enabled,
ControlDesk cyclically sends requests to get the current status of the
ECU as soon as the CCP device is in the connected state.
Split array into base types Lets you enable or disable splitting the
measurement array into single measurement variables of base types
according to the size of each measurement value in the measurement
array.
Service byte order Lets you specify the byte order used by CCP
commands. Select one of the formats below:
n Intel
n Motorola
The CCP byte order usually is defined in the ECUs A2L file and
displayed in the edit field.
Overload indication Lets you enable or disable the overload
indication. Depending on the amount of data to be transmitted and
on the ECU hardware, new data might be sampled before data
transmission for the previous sampling step has finished. In other
words: the ECU's DAQ processor might be overloaded. If the MSB is
set in the DAQ messages to indicate overload and overload indication
is enabled, ControlDesk issues a warning when overload occurs.
Page concept properties Lets you specify the ECU page settings.
Reference page Lets you specify the reference page settings.
Reference page - Address Lets you specify the address of the
ECUs reference page.
ControlDesk requires the address to carry out the SELECT_CAL_PAGE
CCP command for activating the reference page.
The ECUs reference page address usually is defined in the ECUs A2L
file and is displayed in the edit field.
Reference page - Address extension Lets you specify the address
extension of the ECUs reference page.
ControlDesk requires the address extension to carry out the
SELECT_CAL_PAGE CCP command for activating the reference page.
The address extension of the ECUs reference page usually is defined
in the ECUs A2L file and is displayed in the edit field.
Working page Lets you specify the working page settings.
Working page - Address Lets you specify the address of the ECUs
working page.
ControlDesk requires the address to carry out the SELECT_CAL_PAGE
CCP command for activating the working page.
The ECUs working page address usually is defined in the ECUs A2L
file and is displayed in the edit field.
Working page - Address extension Lets you specify the address
extension of the ECUs working page.
ControlDesk requires the address extension to carry out the
SELECT_CAL_PAGE CCP command for activating the working page.
The address extension of the ECUs working page usually is defined in
the ECUs A2L file and is displayed in the edit field.
Protocol layer logging Lets you specify how to save the protocol layer logging information.
properties Configuration Lets you specify the logging level of the CCP
configuration. The following options are available:
n Off: No logging message is written.
n All: Detailed information on connected devices and the selected
device is written to the CCP_Configuration_<device name>.log file
located in the log file path.
Communication Lets you specify the logging level of the CCP data
communication. The following options are available:
n Off: No logging message is written.
n All: The CCP configuration and all communication data is written
to the CCP_ProtocolTrace_<device name>.log file located in the log
file path.
n Exclude DAQ data: Detailed information on connected devices and
the selected device except DAQ data is written to the
CCP_ProtocolTrace_<device name>.log file located in the log file
path.
Log file path Lets you specify a folder to save the log files. The
default folder is the Logs folder in the user-specific Local Program
Data folder. The log files located in the default folder can be selected
for being collected by the dSPACE Installation Manager.
Maximum file size Lets you specify the maximum size of the log
files. The default file size is 32 MB.
Related devices These properties are available for the following devices:
n CCP on page 233
Purpose To specify checksum calculation settings for the selected CCP device.
host PC to the ECU. Only the memory blocks for which ControlDesk
calculates different checksums are equalized.
If a memory segment for which a checksum is to be calculated
exceeds the maximum block length, ControlDesk automatically splits
the segment into smaller parts before checksum calculation.
Tip
If the ECU has large calibration memory segments, defining a
block length smaller than the memory segment length can
significantly reduce the amount of data to be transferred. This
saves time when you start online calibration.
Related devices These properties are available for the following devices:
n CCP on page 233
Properties CCP version Displays the CCP protocol version of the CCP service
implemented in your ECU code.
Master identifier Lets you specify the master CAN identifier for the
selected CCP device. ControlDesks CCP device sends its CCP
commands using this CAN identifier. You can also specify whether
the identifier is sent according to the 'Standard' (11 bit, compliant
with the CAN 2.0 A specification) or 'Extended' (29 bit, compliant
with the CAN 2.0 B specification) identifier format.
Note
ControlDesk does not block ECU access by more than one CCP
device. If you have one ECU with CCP connected to the host PC,
and two CCP devices in ControlDesk with the same CCP
identifier pairs, both CCP devices can access the ECU. This may
lead to unpredictable calibration results.
Prepare quick start Lets you prepare ControlDesk and the ECU for
quick start measurement.
Note
ControlDesk can perform quick start measurement on an ECU
with XCP/CCP/DCI-GSI2 only if the ECU and the loaded
ControlDesk experiment were prepared for quick start
measurement beforehand. The ECU must have stored the
appropriate quick start measurement configuration to its
nonvolatile memory, and the current experiment must contain
information on this configuration.
Note
ControlDesk does not block ECU access by more than one CCP
device. If you have one ECU with CCP connected to the host PC,
and two CCP devices in ControlDesk with the same CCP
identifier pairs, both CCP devices can access the ECU. This may
lead to unpredictable calibration results.
Related devices These properties are available for the following devices:
n CCP on page 233
Purpose To specify seed and key settings for the selected CCP device.
Properties Calibration Lets you specify the path and name of the Seed&Key
DLL file that controls access to the ECU calibration (CAL) resources.
Data acquisition Lets you specify the path and name of the
Seed&Key DLL file that controls access to the ECU data acquisition
(DAQ) resources.
Programming Lets you specify the path and name of the Seed&Key
DLL file that controls access to the ECUs flash programming (PGM)
resources.
Related devices These properties are available for the following devices:
n CCP on page 233
Channels Properties
Related platforms These properties are available for the following platforms:
n DS1202 MicroLabBox on page 248
Common Properties
Board version Displays the board version of the selected I/O board.
CAN channels (Available only for the MicroLabBox platform)
Displays the number of CAN channels available on the selected CAN
module.
Configuration check (Available only for the DCIGSI2 device)
Displays the result of the DCIGSI2 configuration consistency check.
Configuration consistency is checked automatically when a
connection to the DCIGSI2 is established, if the check is enabled in
the IF_DATA DSPACE_XCP entry in the A2L file.
Description (Available only for some I/O boards and I/O modules)
Displays a description of the selected board.
ECU image file (Available only for measurement and calibration
devices) Displays the ECU Image file if available.
ECU state (Available only for the DCIGSI1 device) Displays the ECU
state.
EPK A2L (Available only for measurement and calibration devices)
Displays the value of the optional EPK attribute of the ECUs A2L file.
EPK ECU (Available only for measurement and calibration devices)
Displays the value of the EPK string of the ECU.
EPK image (Available only for measurement and calibration devices)
Displays the value of the optional EPK attribute of the ECU Image file.
Memory segments (Available only for measurement and
calibration devices) Opens the Memory Segments dialog, which lets
you manage the memory segments of the selected device. Refer to
Memory Segments on page 489.
Module description (Available only for FlexRay and CAN FD
interface modules) Displays a description of the selected I/O module.
Module type Displays the type of the selected I/O module.
Module version Displays the module version of the selected I/O
module.
Page concept (Available only for measurement and calibration
devices) Displays the calibration memory pages provided by the ECU.
This property value is read from the A2L file.
Platform name Displays the name of the selected platform/device.
The name was specified during platform registration.
Platform name in experiment Displays the name of the
platform/device in the currently active experiment.
Related platforms/devices These properties are available for the following platforms and devices:
n CAN Bus Monitoring on page 231
n CCP on page 233
n DCIGSI1 on page 234
n DCI-GSI2 on page 236
n DS1005 PPC Board on page 238
n DS1006 Processor Board on page 240
n DS1007 PPC Processor Board on page 242
n DS1103 PPC Controller Board on page 245
n DS1104 R&D Controller Board on page 246
n DS1202 MicroLabBox on page 248
n ECU Diagnostics on page 251
n FlexRay Bus Monitoring on page 252
n LIN Bus Monitoring on page 254
n MicroAutoBox on page 255
n Multiprocessor System on page 258
n SCALEXIO on page 260
n VEOS on page 262
n Video Capturing on page 265
Properties Image compression Lets you turn the image compression on/off
for the video data. You can modify the image compression using the
Quality property. In the Separate mode, this property is always active
to save hardware resources during the transfer of video data.
Image compression settings Lets you specify the image
compression settings for the device.
Quality Lets you specify the image compression quality in percent
[%]. The default image compression quality setting is 75%.
Video codec (Available only in Separate capture mode) Lets you
choose a video codec for compressing video data. You can select all
the video codecs that are installed on the host PC for the Video
Capturing device. For example, you can use the Xvid codec
(http://www.xvid.org). The default codec is Microsoft Video 1.
Related devices These properties are available for the following devices:
n Video Capturing on page 265
Related platforms These properties are available for the following platforms:
n DS1005 PPC Board on page 238
n DS1006 Processor Board on page 240
n DS1007 PPC Processor Board on page 242
n DS1103 PPC Controller Board on page 245
n DS1104 R&D Controller Board on page 246
n DS1202 MicroLabBox on page 248
n MicroAutoBox on page 255
Purpose To specify the byte order format for the DAQ data.
Properties Intel format Lets you specify one of the following byte order
formats:
n Forward
n Sequential
Motorola format Lets you specify one of the following byte order
formats:
n Forward MSB
n Forward LSB
n Backward
n Sequential
For details, refer to Basics on Byte Order Formats and Bit Positioning
on page 142.
Related devices These properties are available for the following devices:
n CAN Bus Monitoring on page 231
Properties DiagCom parameter limits check Lets you select whether the
limits of the DiagCom parameters in the Diagnostics Instrument are
checked.
n If the checkbox is cleared, ControlDesk does not check the value
limits defined in the ODX database. All the values that are valid for
the current data type are permitted.
n If the checkbox is selected, ControlDesk checks for valid parameter
values and lets you use only values that are within the allowed
value range defined in the ODX database.
In both cases the computation method specified in the ODX database
is applied to the parameter values. By default, the parameter limits
check is enabled.
For some parameter types (for example, parameters which use the
SCALE-LINEAR computation method) the value limits cannot be fully
determined since there can be more than one valid value interval for a
parameter. Currently, ControlDesk supports working with one valid
value interval only. For this reason, not all valid intervals might be
available for such a parameter. You can prevent ControlDesk from
checking the value ranges by clearing the checkbox, but remember
that the physical datatype-specific value ranges are still active and
the computation method is still applied to the value.
Related devices These properties are available for the following device:
n ECU Diagnostics on page 251
Properties ECU resources (Not available for the DCIGSI2 device) Displays the
available XCP resources on the ECU. A green icon before an ECU
resource indicates that it is supported on the ECU. A red icon
indicates that it is not supported on the ECU.
ECU state Displays the ECU session state as the returned value of
the GET_STATUS XCP command. A green icon before an ECU state
indicates that it is active on the ECU. A red icon indicates that it is
inactive.
Protocol layer version Displays the XCP protocol layer version as
returned by the connect command.
Slave identification Displays the identification of the ECU as a
result of the GET_ID XCP command, or the EXCHANGE_ID CCP
command. The ECU returns this value to ControlDesk when the
device changes from the disconnected to the connected state in
ControlDesk.
Transport layer version Displays the version number of the
transport layer. The version number is taken from the transport
layerspecific IF_DATA element in the ECU's A2L file.
Unlocked resources (Not available for the DCIGSI2 device)
Displays the protection states of the CCP or XCP resources on the
ECU. A green icon before a resource indicates that it is accessible. A
red icon indicates that it is not accessible.
Related devices These properties are available for the following devices:
n CCP on page 233
n DCI-GSI2 on page 236
n XCP on CAN on page 266
n XCP on Ethernet on page 268
n XCP on FlexRay on page 271
Related devices These properties are available for the following devices:
n DCI-GSI2 on page 236
n XCP on Ethernet on page 268
Related platforms These properties are available for the following platforms:
n SCALEXIO on page 260
Purpose To select the FlexRay interface type for the selected device.
Properties Interface Selection Lets you select the type of the FlexRay
interface. Refer to Interface Selection (CAN-, LIN-, and FlexRay-based
devices) page on page 451.
Related devices These properties are available for the following devices:
n FlexRay Bus Monitoring on page 252
n XCP on FlexRay on page 271
Note
If you specified an external FIBEX file for use with the current
device, this property contains an empty list. The communication
controller settings specified in the external FIBEX file are not
displayed here.
Note
If you specified an external FIBEX file for use with the current
device, this property contains an empty list. The communication
controller settings specified in the external FIBEX file are not
displayed here.
Key slot properties Lets you specify the key slot usage settings.
Slot identifier Lets you specify the slot to be used as the key slot. If
you selected Startup sync or Sync in the Key Slot Using Type property,
you must enter a slot ID.
Type (Available only for the FlexRay Bus Monitoring device) Lets you
select whether the key slot specified by Key Slot ID is to be used for
cluster startup and synchronization, for cluster synchronization only,
or not used at all.
Usually, the key slot usage information is taken from the FIBEX file.
However, it can be useful to specify it manually, for example, when
an ECU is to be put into operation not using the complete FlexRay
cluster.
Type (Available only for the XCP on FlexRay device) Lets you select
whether the key slot specified by Key Slot ID is to be used for cluster
startup and synchronization, for cluster synchronization only, or not
used at all.
Usually, the key slot usage information is taken from the FIBEX file.
However, it can be useful to specify it manually, for example, when
an ECU is to be put into operation not using the complete FlexRay
cluster but only the XCP master controller.
Related devices These properties are available for the following devices:
n FlexRay Bus Monitoring on page 252
n XCP on FlexRay on page 271
FPGA Properties
Properties Block RAM size (Available only for FPGA modules of MicroLabBox,
the DS2655 FPGA Base Board, and the DS2656 I/O Solution Base
Board) Displays the size of the block RAM available on the selected
FPGA module or the userprogrammable FPGA chip.
Default version (Available only for the DS2655 FPGA Base Board
and the DS2656 I/O Solution Base Board) Displays the default
bitstream version of the userprogrammable FPGA. The default
bitstream is used internally during the initialization phase.
Device type (Available only for FPGA modules of MicroLabBox, the
DS2655 FPGA Base Board, and the DS2656 I/O Solution Base Board)
Displays the FPGA device type provided by the selected FPGA module
or the FPGA chip device type provided by the userprogrammable
FPGA base board.
DSP slices (Available only for FPGA modules of MicroLabBox, the
DS2655 FPGA Base Board, and the DS2656 I/O Solution Base Board)
Displays the number of DSP slices available on the selected FPGA
module or userprogrammable FPGA chip.
FPGA application information (Available only for FPGA modules
of MicroAutoBox) Displays information on the FPGA application.
FPGA firmware version (Available only for FPGA modules of
MicroAutoBox) Displays the version of the FPGA firmware.
FPGA type (Available only for FPGA modules of MicroAutoBox)
Displays the type of the FPGA module.
Logic cells (Available only for FPGA modules of MicroLabBox, the
DS2655 FPGA Base Board, and the DS2656 I/O Solution Base Board)
Displays the number of logic cells available on the selected FPGA
module.
Module count (Available only for the DS2655 FPGA Base Board and
DS2656 I/O Solution Base Board) Displays the maximum number of
FPGA I/O modules that can be mounted on the FPGA base board.
Related platforms These properties are available for the following platforms:
n DS1202 MicroLabBox on page 248
n MicroAutoBox on page 255
n SCALEXIO on page 260
General Properties
Properties Date Displays the date when the selected application was created.
Source Displays the path and file name of the selected application.
Related platforms These properties are available for applications that are added to the
experiment and assigned to the following platforms:
n SCALEXIO on page 260
n VEOS on page 262
Note
You can specify general settings for a platform/device only if it is
in the 'disconnected' state.
Note
The automatic reconnecting feature is always enabled for
MicroAutoBox platforms. If a MicroAutoBox platform is in the
unplugged state, ControlDesk tries to reestablish the connection
to the hardware.
Note
Add all the devices and the VEOS platform created for an
offline simulation application to a simulation time group, and
ensure that the Model is executed in real time setting is
cleared for all the devices in that group.
Note
n Since no synchronized time base is used, you should
not perform a measurement on VEOS and on another
simulation platform at the same time.
n Using hardware polling rasters and the OnChange
raster is not useful in virtual validation scenarios
involving the VEOS platform and/or XCP on Ethernet
devices accessing V-ECUs since there is no time
reference between the values measured with these
rasters and values measured with other measurement
rasters.
Tip
This allows you to investigate start-up scenarios in an
offline simulation, for example.
Note
For a platform/device without a working data
set, selecting the 'upload connected variables'
option the first time online calibration is started
prevents ControlDesk from creating a working
and a reference data set. However,
ControlDesk needs a working data set to save
calibration data in ControlDesk. Use the
'upload' option for the first online transition
instead.
Note
You must ensure data integrity yourself.
1)
Not possible for the following platforms: DS1005 PPC Board, DS1006 Processor Board, DS1007 PPC Processor Board, DS1103
PPC Controller Board, DS1104 R&D Controller Board, MicroAutoBox, DS1202 MicroLabBox, SCALEXIO, VEOS.
2) If you selected one or more data sets for downloading on calibration start, the parameter values of these data sets are
downloaded in any case. They are downloaded even if you specified, for example, Upload as the Start online calibration
behavior for the related platform. Refer to How to Select Additional Data Sets for Downloading on Online Calibration Start
( ControlDesk Next Generation Calibration and Data Set Management).
3) ControlDesk compares the parameter values on the connected hardware or VPU and in ControlDesk by calculating CRC
checksum values for the defined memory segments.
4) If no initial data set is available for the platform/device, ControlDesk nevertheless opens the Calibration Memory dialog the
first time you start online calibration.
5) ControlDesk uploads/downloads only memory segments that differ. Memory segments that are equal on the ECU memory
and on the mirrored memory are not up/downloaded. This speeds up the up/download.
Note
Before specifying the start online calibration behavior of a
platform/device, you must decide between safe and fast online
transition.
Related platforms/devices These properties are available for the following platforms and devices:
n CCP on page 233
n DCIGSI1 on page 234
n DCI-GSI2 on page 236
n DS1005 PPC Board on page 238
n DS1006 Processor Board on page 240
n DS1007 PPC Processor Board on page 242
n DS1103 PPC Controller Board on page 245
n DS1104 R&D Controller Board on page 246
n DS1202 MicroLabBox on page 248
n ECU Diagnostics on page 251
n MicroAutoBox on page 255
n Multiprocessor System on page 258
n SCALEXIO on page 260
n VEOS on page 262
n XCP on CAN on page 266
n XCP on Ethernet on page 268
n XCP on FlexRay on page 271
n XIL API MAPort on page 273
Note
Information on the Gigalink connections is updated
automatically as long as no real-time applicaton is loaded to the
system. If an application is currently loaded and you change
Gigalink connections, the display is not updated. Therefore,
change Gigalink connections only if no application is currently
loaded.
Related platforms These properties are available for the following platforms:
n DS1007 PPC Processor Board on page 242
Tip
If you have only one DCIGSI1 connected to the host PC, you do
not have to assign it to a DCIGSI1 device in ControlDesk. It is
assigned automatically.
Related devices These properties are available for the following devices:
n DCIGSI1 on page 234
Related devices These properties are available for the following devices:
n DCIGSI1 on page 234
Related platforms These properties are available for the following platforms:
n DS1007 PPC Processor Board on page 242
n DS1202 MicroLabBox on page 248
n SCALEXIO on page 260
Properties I/O board revision Displays the revision of the I/O board of
MicroAutoBox.
I/O board serial number Displays the serial number of the I/O
board of MicroAutoBox.
I/O board type Displays the type of the I/O board of MicroAutoBox.
Related platforms These properties are available for the following platforms:
n MicroAutoBox on page 255
Related platforms These properties are available for the following platforms:
n DS1005 PPC Board on page 238
n DS1006 Processor Board on page 240
n DS1007 PPC Processor Board on page 242
n MicroAutoBox on page 255
Identification Properties
Properties Board name (Available only for SCALEXIO processing units and for
VEOS) Lets you specify the board name of the selected platform. The
board name must match the setting specified in the application to be
loaded. For VEOS platforms, the board name is displayed and cannot
be changed.
Board type Displays the board type.
DS number (Available only for the DS1007 PPC Processor Board,
DS1202 MicroLabBox, SCALEXIO processing units, and SCALEXIO I/O
boards) Displays the dSPACE identity number.
Identifier (Available only for SCALEXIO processing units) Displays
the serial number/identifier of the selected SCALEXIO processing unit.
IP address (Available only for SCALEXIO processing units and for
VEOS) Displays the IP address of the board.
MAC address (Available only for SCALEXIO processing units)
Displays the MAC address of the SCALEXIO processing unit.
Max. number of cylinders (Available only for SCALEXIO angle
units) Displays the maximum number of cylinders/pistons the virtual
combustion machine can have.
Member of rack (Available only for SCALEXIO processing units and
SCALEXIO I/O units) Lets you specify the name of the rack the
SCALEXIO processing unit belongs to (the rack name must match the
setting in the application to be loaded), or displays the rack the I/O
unit or the DS2907 controller is installed in.
Member of unit (Available only for SCALEXIO I/O boards) Displays
the name of the I/O unit the board is inserted into.
Name (Available only for SCALEXIO I/O units) Lets you specify or
displays the name of the selected I/O unit.
Resolution (Available only for SCALEXIO angle units) Displays the
resolution of the angle counter.
Serial number (Not available for the SCALEXIO Processing Unit)
Displays the serial number of the board.
Slot(s) (Available only for SCALEXIO I/O boards) Displays the slot
number the board is installed in. If the board uses more than one slot,
all required slots are listed.
Solution (Available only for the DS2656 I/O Solution Base Board)
Displays the name of the current FPGA I/O solution.
System name (Available only for SCALEXIO processing units)
Displays the system name of the SCALEXIO processing unit.
Type (Not available for VEOS) Displays the type of the selected
board, I/O unit, SCALEXIO processing unit, IOCNET router, or IOCNET
link board.
Unit name (Available only for the DS2551 IOCNET Router and the
DS2680 I/O Unit) Displays the I/O Unit the DS2551 IOCNET Router or
DS2680 I/O Unit belongs to.
Related platforms These properties are available for the following platforms:
n DS1007 PPC Processor Board on page 242
n DS1202 MicroLabBox on page 248
n SCALEXIO on page 260
n VEOS on page 262
Related devices These properties are available for the following devices:
n Video Capturing on page 265
Related devices These properties are available for the following devices:
n CAN Bus Monitoring on page 231
n CCP on page 233
n LIN Bus Monitoring on page 254
n XCP on CAN on page 266
n XCP on Ethernet on page 268
Related platforms These properties are available for the following platforms:
n SCALEXIO on page 260
Purpose To select the LIN interface type for the selected device.
Properties Interface search attributes Lets you specify the search attributes
for interface selection.
Interface selection Lets you select the type of the LIN interface.
Refer to Interface Selection (CAN-, LIN-, and FlexRay-based devices)
page on page 451.
IP address Lets you enter the IP address used as search the attribute
value for interface selection. LIN interfaces which have this IP address
are searched for. The found interfaces are displayed for selection in
the Interface Selection dialog.
IP addresses Lets you specify IP addresses as search attributes for
LIN interface selection. Select Add in the context menu or click to
add an edit field to specify an IP address, or click to delete the
selected IP address.
Related devices These properties are available for the following devices:
n LIN Bus Monitoring on page 254
Properties Baud rate Lets you specify the baud rate. The baud rate is usually
defined in the variable description and displayed in the edit field. You
can change the baud rate, if necessary. The following baud rates are
supported:
n 1200 bps
n 2400 bps
n 4800 bps
n 9600 bps
n 19200 bps
n You can also specify a custom baud rate. It must not exceed the
range from 1000 bps to 20000 bps and must be a multiple of
100.
Protocol version Lets you specify the LIN protocol version.
ControlDesk reads the value from the LDF file. You can specify a
different LIN protocol version, if necessary.
ControlDesk supports the following protocol versions:
n 2.1
n 2.0
n 1.3
Checksum calculation Displays all the LIN communication frames.
Checksum calculation - Frame identifier Displays the identifiers
of the LIN communication frames. The identifiers of LIN
communication frames are in the range 0 59.
Checksum calculation - Checksum type Lets you specify the
checksum calculation type individually for each LIN communication
frame. The following checksum calculation types are available:
Related devices These properties are available for the following devices:
n LIN Bus Monitoring on page 254
Purpose To select logical links for ECU diagnostics, to display the active logical
links of the ECU Diagnostics device with their configurations, and to
specify connection check settings and configure communication
parameters individually for each active logical link.
Properties Active logical links Displays all the logical links that are currently
selected for use with the ECU Diagnostics device and also the links'
configurations. The list is sorted according to hierarchical layers. The
listed logical links can be used for diagnostic communication via the
Diagnostics and Fault Memory Instruments.
Whether the long names or short names of the logical links are
displayed depends on the settings made on the Diagnostics
Management page of the ControlDesk NG Options dialog. Refer to
Diagnostics Management Page ( ControlDesk Next Generation ECU
Diagnostics).
Communication parameters Lets you open the Communication
Parameters page of the Active Logical Links dialog to specify
configuration settings for the communication parameters (COMPARAMs)
that are relevant for the active logical links. You can define
userdefined values for the communication parameters, and specify
whether to use the userdefined value or the ODX value for
communication individually for each communication parameter. Refer
to Active Logical Links page on page 386.
Related devices These properties are available for the following devices:
n ECU Diagnostics on page 251
Properties CPU (Available only for the DS1007 platform) Displays the CPU of
the processor boards belonging to the selected DS1007
multiprocessor system.
Name (Available only for the Multiprocessor System platform)
Displays the names of the DS1005 or DS1006 boards that form the
selected multiprocessor system. These are the platform names which
are used for the processor boards in the experiment.
Platform name (Available only for the Multiprocessor System
platform) Displays assignment information for the members of the
DS1005based or DS1006based multiprocessor system. If the
member is currently assigned to hardware, the platform name of the
assigned processor board is displayed. If the member is currently not
assigned, 'unassigned' is displayed.
Port address (Available only for the Multiprocessor System platform
and only for the 'Assign to any equal platform' assignment mode)
Displays the base address of the board as specified with the DIP
switches or rotary switches on the DS1005 or DS1006, or lets you
specify the base address of the board. When you register a
multiprocessor system, the default processor names and board port
addresses are specified like this: MASTER, 0x300 (first board), SLAVE,
0x310 (second board), SLAVE_B, 0x320 (third board), SLAVE_C,
0x330 (fourth board), etc. You should set a port addresses suitable
for your realtime hardware.
Processor board (Available only for the DS1007 platform) Displays
the names of the DS1007 boards that constitute the selected DS1007
multiprocessor system.
Processor name (Relevant only for the Multiprocessor System
platform) Displays the name specified for the selected processor
board during hardware registration.
When you register a multiprocessor system based on DS1005 or
DS1006, the default processor names and board port addresses are
specified like this: MASTER, 0x300 (first board), SLAVE, 0x310 (second
board), SLAVE_B, 0x320 (third board), SLAVE_C, 0x330 (fourth
board), etc. You can change the names manually. When a variable
Related platforms These properties are available for the following platforms:
n Multiprocessor System on page 258
n DS1007 PPC Processor Board on page 242
Memory Properties
Properties Flash EEPROM size Displays the size of the boards flash memory.
Global RAM size Displays the size of the boards global RAM.
L2 cache size Displays the size of the boards L2 cache.
Local RAM size Displays the size of the boards local RAM.
Related platforms These properties are available for the following platforms:
n DS1005 PPC Board on page 238
n DS1006 Processor Board on page 240
n DS1103 PPC Controller Board on page 245
n DS1104 R&D Controller Board on page 246
n MicroAutoBox on page 255
Purpose To display information on the model access port (XIL API MAPort)
implementation that is used.
Properties Product name Displays the product name of the XIL API MAPort
implementation.
Product version Displays the product version of the XIL API MAPort
implementation.
Vendor name Displays the vendor of the XIL API MAPort
implementation.
XIL API version Displays the XIL API version of the MAPort
implementation.
Related platforms These properties are available for the following platforms:
n XIL API MAPort platform on page 610
Properties Network adapter selection Lets you select the network interface
card to communicate with the ECU or VPU. The names and IP
addresses of the network interface cards currently available on your
host PC are displayed. You can select one of the network interface
cards available in the host PC.
Bind to local port Lets you enable or disable the communication
with the ECU or VPU via a certain local port of the host PC.
Generally, the Ethernet port for outgoing communication is assigned
by the system randomly and you can keep the property disabled.
However, if a firewall is installed on the PC and a specific port is
mandatory for communication, you can enable the property to bind
to a specific local port. You must then specify the local port number.
Note
Keep in mind that this port is on the host PC, not on the ECU.
Local port Lets you specify the local port number of the host PC if
the property Bind to Local Port is enabled.
Note
A local port can be used for communication by only one process
on the host PC. You must therefore ensure that the local port
number is not used by another program or another
device/platform within ControlDesk to avoid assignment
conflicts.
Related devices These properties are available for the following devices:
n DCI-GSI2 on page 236
n XCP on Ethernet on page 268
Related platforms These properties are available for the following platforms:
n DS1007 PPC Processor Board on page 242
n DS1202 MicroLabBox on page 248
n SCALEXIO on page 260
n VEOS on page 262
Related devices These properties are available for the following devices:
n DCIGSI1 on page 234
Related platforms These properties are available for the following platforms:
n DS1005 PPC Board on page 238
n DS1006 Processor Board on page 240
n DS1007 PPC Processor Board on page 242
n DS1103 PPC Controller Board on page 245
n DS1104 R&D Controller Board on page 246
n DS1202 MicroLabBox on page 248
n MicroAutoBox on page 255
n SCALEXIO on page 260
Simulation Properties
Related platforms These properties are available for the following platforms:
n XIL API MAPort platform on page 610
Speed Properties
Properties Max. speed 360 Displays the lower (reverse rotation) and upper
limits of speed measurement for the 360-angle operating range.
Max. speed 720 Displays the lower (reverse rotation) and upper
limits of speed measurement for the 720-angle operating range.
Related platforms These properties are available for the following platforms:
n SCALEXIO on page 260
Related platforms These properties are available for the following platforms:
n Multiprocessor System on page 258
Purpose To specify the settings of the transport layer on the ECU with
XCP/DCI-GSI2.
Properties Communication thread priority Lets you specify the priority of the
communication thread in the transport layer. The following priorities
are available:
n Normal (default)
n Above normal
n Highest
Ethernet receive buffer size (Available only for XCP on Ethernet
and DCIGSI2 devices) Lets you specify the size of the receive buffer
for Ethernet messages in bytes. The maximum size of the receive
buffer is 10 MB.
Ethernet send buffer size (Available only for XCP on Ethernet and
DCIGSI2 devices) Lets you specify the size of the send buffer for
Ethernet messages in bytes. The maximum size of the send buffer is
10 MB.
Interpolate time stamp values (Not available for the DCIGSI2
device) Lets you enable or disable the interpolation of time stamp
values for XCP packets that are received from the receive buffer at
the same time.
Message buffer size Lets you specify the size of the internal
message buffer.
n XCP on FlexRay device: The default size is 100 messages. You can
select a value in the range 1 10,000.
n DCI-GSI2 and XCP on Ethernet devices: You specify the size of the
internal message buffer as a multiple of the receive buffer by
entering the factor. The default factor is '1', which means the size
of the internal message buffer matches the receive buffer size.
You can select a factor in the range 1 10.
Transport layer logging Lets you specify how logging information is saved to log files.
properties Configuration Lets you specify the logging level of the XCP
configuration. The following options are available:
n Off: No logging message is written.
n All: Detailed information on connected devices and the selected
device is written to the XCP_<TransportLayer>Configuration.log
file located in the log file path.
Communication Lets you specify the logging level of the XCP data
communication. The following options are available:
n Off: No logging message is written.
n All: The XCP configuration and all transport layer data is written to
the XCP_<TransportLayer>NetworkLayer.log file located in the log
file path.
Log file path Lets you specify a folder to save the log files. The
default folder is the Logs folder in the user-specific Local Program
Data folder. The log files located in the default folder can be selected
for being collected by the dSPACE Installation Manager.
Maximum file size Lets you specify the maximum size of the log
files. The default file size is 32 MB.
Related devices These properties are available for the following devices:
n DCI-GSI2 on page 236
n XCP on FlexRay on page 271
n XCP on Ethernet on page 268
Related platforms These properties are available for the following platforms:
n SCALEXIO on page 260
Purpose To display the vehicle that is selected to be used with the selected
ECU Diagnostics device and to select another vehicle.
Properties Select vehicle Displays the name of the vehicle currently selected
for the ECU Diagnostics device, and lets you open the Select Vehicle
dialog to select another vehicle. Refer to Select Vehicle page
on page 379.
Whether the long name or short name of the vehicle is displayed
depends on the settings made on the Diagnostics Management page
of the ControlDesk NG Options dialog. Refer to Diagnostics
Management Page ( ControlDesk Next Generation ECU
Diagnostics).
Related devices These properties are available for the following devices:
n ECU Diagnostics on page 251
Related platforms These properties are available for the following platforms:
n VEOS on page 262
Purpose To specify timing settings for the VEOS simulation for the selected
platform.
Properties Break time Lets you enter a time in seconds where the simulation
breaks automatically. You can resume the simulation via the Start or
Single Step command. Infinity indicates that the simulation must not
pause automatically.
Real-time acceleration factor Lets you specify a factor to
accelerate or decelerate the simulation run in relation to real time.
With a factor of 1, the simulation run is (nearly) executed in real time.
A factor greater than 1 accelerates the simulation run, a factor less
than 1 decelerates it. A value of 0 means that the simulation run is
executed as fast as possible.
Single step time Lets you specify the duration of one simulation
step in seconds. The duration specification is used when you perform
a single-step simulation, refer to Single Step on page 528. If you
specify a duration of 0 seconds, one single simulation command is
executed per simulation step.
Stop time Lets you specify the simulation duration in seconds.
Specify infinity for an endless simulation run.
Related platforms These properties are available for the following platforms:
n VEOS on page 262
Version Properties
Properties FPGA type Displays the FPGA type of the selected hardware.
Piggy-back module version Displays the version of the selected
piggy-back module.
Version Displays the software versions and statuses related to the
platform.
Version Displays the module versions of the hardware and the
software of a DS1005 PPC Board, DS1006 Processor Board, DS1103
PPC Controller Board, DS1104 R&D Controller Board, or
MicroAutoBox, the application and the connected periphery boards
(I/O modules in the case of MicroAutoBox).
Related platforms These properties are available for the following platforms:
n DS1005 PPC Board on page 238
n DS1006 Processor Board on page 240
n DS1103 PPC Controller Board on page 245
n DS1104 R&D Controller Board on page 246
n MicroAutoBox on page 255
VPU Properties
Related platforms These properties are available for the following platforms:
n VEOS on page 262
Related devices These properties are available for the following devices:
n XCP on CAN on page 266
n XCP on Ethernet on page 268
n XCP on FlexRay on page 271
Properties Master identifier Lets you specify the master CAN identifier for the
ECU with XCP on CAN. The ECU with XCP on CAN sends its XCP
commands to ControlDesk using this CAN identifier. You can also
specify whether the identifier is sent according to the 'Standard' (11
bit, compliant with the CAN 2.0 A specification) or 'Extended' (29 bit,
compliant with the CAN 2.0 B specification) identifier format.
Note
ControlDesk does not block ECU access by more than one XCP
on CAN device. If you have one ECU with XCP on CAN
connected to the host PC, and two XCP on CAN devices in
ControlDesk with the same XCP identifier pairs, both XCP on
CAN devices can access the ECU. This may lead to unpredictable
calibration results.
Slave identifier Lets you specify the slave CAN identifier for the
ECU with XCP on CAN. The ECU with XCP on CAN sends its XCP
responses to ControlDesk using this CAN identifier. You can also
specify whether the identifier is sent according to the 'Standard' (11
bit, compliant with the CAN 2.0 A specification) or 'Extended' (29 bit,
compliant with the CAN 2.0 B specification) identifier format.
Note
ControlDesk does not block ECU access by more than one XCP
on CAN device. If you have one ECU with XCP on CAN
connected to the host PC, and two XCP on CAN devices in
ControlDesk with the same XCP identifier pairs, both XCP on
CAN devices can access the ECU. This may lead to unpredictable
calibration results.
Maximum DLC required Lets you enable or disable sending all the
XCP packets with a data length code of 8.
Set DAQ identifier Lets you enable or disable sending the XCP
SET_DAQ_ID command.
CAN Acknowledge Lets you specify CAN acknowledge settings.
Acknowledge check Lets you specify whether to evaluate the
acknowledge for the successful transmission of a CAN message.
Timeout Lets you specify the time to wait for an acknowledge after
a CAN message was copied to the send buffer.
Related devices These properties are available for the following devices:
n XCP on CAN on page 266
Properties ECU IP address (Disabled for the XCP on Ethernet device if the
IP address inheritance setting is selected. Refer to Inheritance Settings
Properties on page 329.) Lets you specify the IP address of the
connected ECU or VECU (XCP on Ethernet device) or the connected
DCIGSI2 (DCIGSI2 device).
ECU port Lets you specify the port number of the connected ECU or
VPU (XCP on Ethernet device) or the connected DCI-GSI2 (DCI-GSI2
device).
Related devices These properties are available for the following devices:
n DCI-GSI2 on page 236
n XCP on Ethernet on page 268
Properties Cluster identifier Lets you select the cluster (FlexRay bus) to be
used for controller configuration. The Cluster ID is initially taken from
the specified A2L file. If you did not specify an A2L file for the device,
you can enter the ID.
Header type Lets you select the header type of the FlexRay
transport layer. The possible types are defined in the XCP on
FlexRayspecific AML file. The value is taken from the A2L file.
Master controller node Displays the name of the FlexRay controller
node which is identified as the XCP master by the CMD Slot ID in the
FIBEX file and the cluster ID.
NAX Lets you specify the network access extension. The ID is used
for identifying the ECU.
Packet alignment Lets you select the packet alignment to be used
in building transport layer data packets. The possible packet
alignments are defined in the XCP on FlexRay-specific AML file. The
value is taken from the A2L file.
T1 FLX Lets you specify the timeout for connecting to the FlexRay
cluster.
Pool buffer properties Lets you specify the pool buffer properties.
Cycle repetition Lets you specify the cycle repetition value for the
pool buffer.
DAQ Lets you specify whether the pool buffer is used for data
acquisition.
Length Lets you specify the maximum length of the data to be
transmitted using the pool buffer.
Offset Lets you specify the cycle offset value for the pool buffer.
Slot identifier Lets you specify the FlexRay slot to be used as the
pool buffer. The slot is used for receiving DAQ data from the ECU.
Initial CMD buffer Lets you specify settings for the initial CMD buffer, which is used for
properties sending commands to the ECU.
Channel Lets you specify the FlexRay channel for the CMD slot used
to transmit commands to the ECU.
Cycle repetition Lets you specify the cycle repetition value for the
CMD slot.
Length Lets you specify the maximum length of the data to be
transmitted.
Offset Lets you specify the cycle offset value for the CMD slot.
Slot identifier Lets you specify the FlexRay slot to be used for CMD
messages. This slot is used for sending commands from the XCP
master to the ECU.
Initial RES_ERR buffer Lets you specify settings for the initial RES_ERR buffer which is used
properties to send responses from the ECU to ControlDesk.
Channel Lets you specify the FlexRay channel the ECU uses to
transmit the response of an XCP command.
Cycle repetition Lets you specify the cycle repetition value for the
RES_ERR slot.
DAQ Lets you specify whether the initial RES_ERR buffer can be
used for receiving DAQ data or not. If you specify 'FIXED', a transport
layer command is sent to the ECU to enable the ECU buffer for DAQ
data transmission.
Length Lets you specify the maximum length of the data to be
transmitted.
Offset Lets you specify the cycle offset value for the RES_ERR slot.
Slot identifier Lets you specify the FlexRay slot to be used for
RES_ERR messages. This slot is used for receiving responses from the
ECU.
Related devices These properties are available for the following devices:
n XCP on FlexRay on page 271
Purpose To specify seed and key settings for the selected XCP device.
Properties Seed and Key DLL Lets you specify the path and name of the seed
and key DLL file that controls access to the ECU calibration (CAL) and
DAQ resources.
Related devices These properties are available for the following devices:
n XCP on CAN on page 266
n XCP on Ethernet on page 268
n XCP on FlexRay on page 271
Purpose To specify advanced settings for the selected XCP or DCIGSI2 device.
Properties Cyclic status detection Lets you enable or disable the cyclic
transmission of ECU status detection requests. If enabled,
ControlDesk cyclically sends requests to get the current status of the
ECU as soon as the XCP device is in the connected state.
MAX_DTO (Not available for the DCIGSI2 device) Lets you specify
the maximum size of an XCP data transmission object (DTO) packet.
Note
The MAX_DTO value you specify must be equal to the value
internally used by the ECU. Otherwise, ControlDesk's
measurement data might be incorrect.
MAX_CTO (Not available for the DCIGSI2 device) Lets you specify
the maximum size of an XCP command transmission object (CTO)
packet.
Note
The MAX_CTO value you specify must be equal to the value
internally used by the ECU. Otherwise, the behavior of
ControlDesk is unpredictable.
Note
n PID OFF is not supported for the XCP on Ethernet device.
n To enable the PID OFF mode, some preconditions must be
met. Refer to Measurement Features ( XCP Feature
Reference).
Read XCP settings from A2L (Not available for the DCIGSI2
device) Lets you specify to use the XCP service configuration
information from a variable description that you add or reload. Using
information from the new/reloaded variable description overwrites
the configuration information that is currently used by the device. If
there are inconsistencies between the currently used configuration
information and the corresponding information contained in the
new/reloaded A2L file, a dialog opens for you to specify whether to
use the current value or to use the value from the new/reloaded
A2L file for each single inconsistent ECU interface setting.
n If enabled, ControlDesk reads the XCP service configuration
information from the new/reloaded A2L file. If this differs from the
currently used ECU interface settings, you can select to use the
Note
To support enhanced memory page handling, ControlDesk
requires memory page information, such as the number of
pages, in the ECU's A2L file. The information must be consistent
with the configuration of the XCP service that is implemented in
the ECU code.
Service byte order (Not available for the DCIGSI2 device) Lets you
specify the byte order used by XCP commands. Select one of the
formats below:
n Intel
n Motorola
The XCP byte order usually is defined in the ECUs A2L file. In this
case, it is displayed in the edit field.
Split array into base types (Not available for the DCIGSI2 device)
Lets you enable or disable splitting the measurement array into single
measurement variables of base types according to the size of each
measurement value in the measurement array.
XCP driver version Displays the XCP driver version as the returned
value of the XCP command GET_COMM_MODE_INFO.
Communication modes (Not available for the DCIGSI2 device) Lets you specify the master
properties and slave block transfer mode settings.
Slave block mode Lets you enable or disable the slave block
transfer mode.
Master block mode Lets you enable or disable the master block
transfer mode.
MAX_BS Lets you specify the maximum block size for transferring
data in the master block transfer mode.
MIN_ST Lets you specify the minimum time interval between two
data packets in the master block transfer mode.
Protocol layer logging Lets you specify how to save the XCP protocol logging information.
properties Configuration Lets you specify the logging level of the XCP
configuration. The following options are available:
n Off: No logging message is written.
n All: Detailed information on connected devices and the selected
device is written to the XCP_Configuration_<device name>.log file
located in the log file path.
Communication Lets you specify the logging level of the XCP data
communication. The following options are available:
n Off: No logging message is written.
n All: The XCP configuration and all communication data is written
to the XCP_ProtocolTrace_<device name>.log file located in the log
file path.
n Exclude DAQ data: Detailed information on connected devices and
the selected device except DAQ data is written to the
XCP_ProtocolTrace_<device name>.log file located in the log file
path.
Log file path Lets you specify a folder to save the log files. The
default folder is the Logs folder in the user-specific Local Program
Data folder. The log files located in the default folder can be selected
for being collected by the dSPACE Installation Manager.
Maximum file size Lets you specify the maximum size of the log
files. The default file size is 32 MB.
Time stamp settings (Not available for the DCIGSI2 device) Lets you specify the time
properties stamp settings.
Resolution Lets you specify the resolution of the XCP time stamps.
Size Lets you specify the size of the XCP time stamps.
Time stamps Lets you specify how the data measured from the
connected ECU gets time stamps.
n When XCP timestamping is enabled, ControlDesk uses the XCP
time stamps generated by the ECU with XCP.
n When XCP timestamping is disabled, measured data gets time
stamps from the interface between the host PC and the ECU with
XCP.
Note
With XCP on CAN, XCP timestamping significantly decreases
the data throughput on the CAN bus. To get the optimum data
throughput, you should disable XCP timestamping.
Ticks Lets you specify the ticks of the XCP time stamps.
Related devices These properties are available for the following devices:
n DCI-GSI2 on page 236
n XCP on CAN on page 266
n XCP on Ethernet on page 268
n XCP on FlexRay on page 271
Properties Algorithm Lets you specify the algorithm which is used by the ECU
for checksum calculation. ControlDesk provides the following options:
n ECU defined
By default, the checksum calculation configuration is ECU defined.
ControlDesk uses the checksum algorithm of the ECU.
n User defined DLL
ControlDesk uses the checksum calculation specified in the
Checksum DLL configuration.
n Disabled
You can disable checksum calculation. ControlDesk also disables
checksum calculation if the BUILD_CHECKSUM command is not
defined in the A2L file.
n Checksum algorithm
You can select one of the checksum algorithms from the drop-
down list. ControlDesk overwrites the ECUdefined checksum
algorithm in this case.
Note
For DCIGSI2 devices, the algorithm is always set to 'ECU
defined' and cannot be changed.
Checksum DLL (Not available for the DCIGSI2 device) Lets you
specify the path and name of a DLL file defining a custom checksum
algorithm.
You must specify a DLL file if userdefined checksum calculation is
specified in the XCP service via the XCP_CHECKSUM_USER_DEFINED
option.
ControlDesk reads the name of the DLL file from the devices A2L file.
ControlDesk uses the A2L file path as the path for the DLL file.
Note
The algorithm defined in the specified DLL file must correspond
to the algorithm that is implemented in the ECU code.
Tip
If the ECU has large calibration memory segments, defining a
block length smaller than the memory segment length can
significantly reduce the amount of data to be transferred. This
saves time when you start online calibration.
Related devices These properties are available for the following devices:
n DCI-GSI2 on page 236
n XCP on CAN on page 266
Purpose To prepare ControlDesk and the ECU for quick start measurement.
Property Prepare quick start Lets you prepare ControlDesk and the ECU for
quick start measurement.
Before you can perform a quick start measurement on an ECU with
XCP or DCIGSI2, you must configure the measurement in
ControlDesk. The configuration must be transferred to the ECUs
nonvolatile memory.
n If you select the checkbox, you can prepare the experiment and
the ECU for quick start measurement. ControlDesk's behavior
when starting measurement is as follows:
n ControlDesk does not start an actual measurement, that is, no
measurement data is displayed in the ControlDesk instruments.
n The current measurement configuration is transmitted to the
ECU. The ECU is triggered to store the configuration in its
nonvolatile memory. The ECU saves the configuration later, for
example, during the next shutdown.
n ControlDesk saves the measurement configuration in the
current experiment.
n If you clear the checkbox, the experiment and the ECU cannot be
prepared for quick start measurement.
For instructions on preparing and performing a quick start
measurement on an ECU with XCP or DCIGSI2, refer to:
n How to Prepare a Quick Start Measurement on an ECU with XCP
or DCI-GSI2 ( ControlDesk Next Generation Measurement and
Recording).
n How to Perform a Quick Start Measurement on an ECU with XCP
or DCIGSI2 ( ControlDesk Next Generation Measurement and
Recording).
Purpose To specify quick start settings for the selected XCP or DCIGSI2
device.
Property Quick start Lets you activate or deactivate the quick start mode in
ControlDesk.
To perform quick start measurement, ControlDesk must be in the
quick start mode.
Note
ControlDesk can perform quick start measurement on an ECU
with XCP/CCP/DCI-GSI2 only if the ECU and the loaded
ControlDesk experiment were prepared for quick start
measurement beforehand. The ECU must have stored the
appropriate quick start measurement configuration to its
nonvolatile memory, and the current experiment must contain
information on this configuration.
Platform/Device-Related Commands
Activate Application
Access This command is available only for SCALEXIO and VEOS platforms,
and only in combination with an inactive application. You can access
it via:
Ribbon None
Context menu of Project Manager platform inactive
application
Description Only one application can be active for a platform at a time. All the
other applications are inactive.
When you add a new application to a platform in the experiment via
the Real-Time Application - Add to Experiment, Offline Simulation
Application - Add to Experiment, or Add multiple platforms/devices
command, the application is automatically activated. To change back
to an older one later on, you have to activate it manually.
Access This command is available only for the XCP and CCP devices whose
device hardware is connected to the host PC. You can access it via:
Ribbon None
Context menu of n Project Manager XCP on CAN device,
XCP on Ethernet device, XCP on FlexRay
device, and CCP device
n Platform/Device Manager XCP on CAN
device, XCP on Ethernet device, XCP on
FlexRay device, and CCP device
Shortcut key None
Icon None
Purpose To save calibration data from the active memory page to the ECUs
nonvolatile memory.
Result Calibration data from the active memory page is saved to the ECUs
nonvolatile memory.
Note
To use the Activate Data Page Freezing command, the service
implemented in the ECU code (XCP or CCP service) must support
data page freezing.
Description When you use the Activate Data Page Freezing command,
ControlDesk requests the ECU to save calibration data to nonvolatile
memory. Data storage is handled completely by the service
implemented in the ECU code. Data is usually stored at a later point
in time, for example, during the next ECU shutdown.
n For an ECU with XCP, ControlDesk sets the STORE_CAL_REQ bit
using the SET_REQUEST XCP command.
n For an ECU with CCP, ControlDesk sets the STORE bit using the
SET_S_STATUS CCP command.
Access This command is available only for the ECU Diagnostics device, and
only in combination with an inactive diagnostics database. You can
access it via:
Ribbon None
Context menu of Project Manager ECU Diagnostics device
inactive diagnostics database
Shortcut key None
Icon None
Description Only one diagnostics database can be active for an ECU Diagnostics
device at a time. All the other diagnostics databases are inactive. A
diagnostics database must be active to be used with an ECU
Diagnostics device.
When you activate a diagnostics database, ControlDesk activates its
variable description, if available.
Access This command is available only if online calibration has not been
started. You can access it via:
Ribbon None
Context menu of n Project Manager active experiment
Purpose To add and configure all platforms and devices that are required to
experiment with virtual ECUs simulated by a VEOS/SCALEXIO
application.
Description This command lets you add and configure platforms and devices that
refer to an application containing virtual ECUs and optionally an
environment model, executed on VEOS or SCALEXIO. After importing
a variable description or simulation application, ControlDesk analyzes
the OSA/RTA information and identifies the required hosting platform
(VEOS/SCALEXIO) and XCP on Ethernet devices (used to access the
virtual ECUs). The platforms/devices are displayed for selection for the
active experiment and configuration. For each selected XCP on
Ethernet device, you can specify with a single click to inherit the
settings from the parent VEOS or SCALEXIO platform.
ControlDesk lets you add an OSA or RTA file instead of a variable
description file in the experiment. This can be useful if you work with
an application without an environment model, for example. However,
performing measurement or calibration is not possible for platforms
without a variable description.
Result ControlDesk opens the Add Multiple Platforms/Devices dialog for you
to import the variable description or simulation application file to be
used. After you select and configure the relevant platform and
devices, ControlDesk performs the following steps:
n The parent platform (VEOS/SCALEXIO) and the selected XCP on
Ethernet devices are added to the experiment.
n In the case of offline simulation with VEOS, the VEOS platform
and the XCP on Ethernet devices are automatically added to a new
simulation time group.
n The application and variable descriptions are added to the
experiment and assigned to the platform/devices.
Add Multiple Selected File Displays the path and name of the selected variable
Platforms/Devices dialog description or simulation application file.
Import from file Opens a standard Windows Open dialog for you
to choose one of the following files:
n SDF: If you select an SDF file, the variable description is added to
the platform. Selecting a variable description file lets you perform
calibration and measurement with the platform later on.
n OSA/RTA: If you select an OSA or RTA file, the simulation
application file is added to the platform. Selecting a simulation
application file prevents you from performing measurement or
calibration with the platform later on.
Note
You cannot add a variable description file to the platform
after the platform is added to the experiment.
Add Lets you specify whether to add the platform or device to the
currently active experiment. A warning icon is displayed next to the
checkbox if the configuration is not valid (e.g., if the file specified in
the File path field does not exist or could not be imported).
Access This command is available only for the ECU Diagnostics device. You
can access it via:
Ribbon None
Context menu of n Project Manager ECU Diagnostics device
Description For an ECU Diagnostics device, only one diagnostics database can be
active at a time. The new diagnostics database is automatically
activated, and the previously active diagnostics database is
deactivated. To change back to an older one later on, you must
activate it manually.
Select ODX Files page To specify a diagnostics database for the selected ECU Diagnostics
device.
This page is available for the ECU Diagnostics devices.
ODX database name Lets you enter a name for the ODX
diagnostics database. The default is 'ODX DB'.
When database selection has finished, the ODX database with the
specified name is displayed in the Project Manager. ControlDesk also
adds a folder with this name to the projects folder structure on your
file system. The folder contains all the files belonging to the ODX
database.
Tip
You can specify several diagnostics databases for an ECU
Diagnostics device. You should then change their default names
for clarity and better handling.
Note
Disable automatic ODX version detection only if you are very
familiar with ODX databases and the used database files.
Note
Using the binary format results in faster experiment loading, and
allows you to work with large ODX databases because memory
usage is reduced. On the other hand, generating the binary
format takes some time.
Using the binary format is useful in the following cases:
n Experiments that are frequently loaded, and whose
diagnostics database is modified only rarely
n Experiments that require large ODX databases
Note
For ODX 2.2.0 diagnostics databases, database optimization is
always performed. You cannot change this setting. So if you
work with an ODX 2.2.0 database, ControlDesk always uses the
binary format instead of ODX data for the diagnostics database.
Files list Displays all the files imported so far for the ODX
diagnostics database for your ECU Diagnostics device. The following
information is shown for each file:
n Intended action (column on the left)
Displays the action that is to be performed on the file according to
the ODX database configuration currently active for the ECU
Diagnostics device. Each action is indicated by a symbol.
n File name
n File type
An ODX database typically contains files of the following types:
Extension Description
ODX File format for all the files containing ODX data
ODX-D File format for specifications of diagnostic services and diagnostic jobs
(DIAGLAYERCONTAINER)
ODX-C File format for communication parameter specifications (COMPARAMSPEC)
ODX-V File format for vehicle information specifications (VEHICLEINFOSPEC)
ODX-M File format for specifications of multipleECU jobs (MULTIPLEECUJOBSPEC)
ODX-F File format for ECU flash programming specifications (FLASH)
PDX File container for ODX data (also called PDX package). All the files to be exchanged are
packaged in one file container. The content of the container is described in a container
catalog (PDX package catalog), which is also stored in the PDX package. Besides the
ODX data, a PDX package can contain files of any format.
Note
To execute diagnostic jobs and/or perform ECU flash memory programming, it is
not sufficient that the related files (such as CLASS, JAR, or HEX files) are in the
PDX package. You have to import these files in addition to the PDX package.
The folder with the ODX database can also contain the following file
types and files:
File Description
CLASS, JAR File formats for diagnostic jobs
HEX, MOT, S19, File formats for flash data (ECU Image files)
simulation.txt Contains the simulated ECU.
This file can be used for simulating ECU diagnostics.
File Description
DS_Service_Config<...>.xml Maps ODX semantics to ControlDesk functions.
This configuration file is required for setting up services others than
the default services provided by ControlDesk, for example, for reading
the fault memory and environment data, clearing fault memory entries
and performing measurement and calibration, which can then be used
in ControlDesk. For further information, refer to Basics of the XML
Configuration File ( ControlDesk Next Generation ECU Diagnostics).
File info field Displays information on the file currently selected in
the files list.
Database Template Displays information on the selected ODX
database template (if one is currently selected).
Files Add (Not available if an ODX database template is used) Lets
you import one or more files to the ODX diagnostics database. The
imported files are added to the files list.
The command is also available via context menu. As an alternative,
you can press the Insert or + key.
Files Reload (Not available if an ODX database template is used)
Lets you reload the selected files. If possible, ControlDesk loads the
selected files from their original source paths again.
The command is also available via context menu.
Files Remove (Not available if an ODX database template is used)
Removes the selected files from the files list. File deletion does not
take effect on the diagnostics database configuration currently active
for the ECU Diagnostics device until you click Next or Finish.
The command is also available via context menu. As an alternative,
you can press the Delete or - key to remove the selected files from
the files list.
Files Remove All (Not available if an ODX database template is
used) Removes all the files from the files list.
The command is also available via context menu.
Template Add (Available only if no files have been imported for
the ODX diagnostics database, or if an ODX database template is
used) Lets you import an ODX database template. An ODX database
template is a valid ODX database that cannot be modified.
The ODX Database Templates dialog opens for you to select the ODX
database template.
Via the Select template source dropdown list, you must select
whether to import a builtin or a custom ODX database template.
ControlDesk provides builtin ODX database templates for different
diagnostic protocols (some in binary format). They are displayed for
selection. If you select to add a custom ODX database template,
ControlDesk lists all the custom ODX database templates on the
custom ODX database template source path. The source path is
specified on the Diagnostics Management page of the
ControlDesk NG Options dialog.
After you select an ODX database template, the Database Template
tab displays information on the selected database template. The files
contained in the ODX database template are displayed in the files list.
Template Remove (Available only if an ODX database template is
used) Removes the currently selected ODX database template.
Sort By File Name (Ascending) (Available via context menu) Lets
you sort the files list alphabetically in ascending order by the File
Name column.
Sort By File Extension (Ascending) (Available via context menu)
Lets you sort the files list alphabetically in ascending order by the File
Type column.
Sort By File Action (Ascending) (Available via context menu)
Lets you sort the files list in ascending order by the file action type.
Sort By File Name (Descending) (Available via context menu)
Lets you sort the files list alphabetically in descending order by the File
Name column.
Sort By File Extension (Descending) (Available via context
menu) Lets you sort the files list alphabetically in descending order by
the File Type column.
Tip
You can also sort the files list alphabetically in ascending or
descending order by clicking the appropriate column header.
Show Removed Files (Available via context menu) Lets you specify
to display files that are to be removed from the diagnostics database
configuration currently active for the ECU Diagnostics device in the
files list. If enabled, the files selected for deletion are displayed in the
files list, marked with the symbol. This allows you to check the
files selected for deletion.
Select Vehicle page To select a vehicle for the selected ECU Diagnostics device.
This page is available for the ECU Diagnostics devices.
Vehicle list Displays all the vehicles related to the specified ODX
database, and lets you select a vehicle for the selected ECU
Diagnostics device.
If no vehicle information is specified in the ODX database, a default
vehicle named "VI_GlobalVehicleInfor" (short name) or "Global
Vehicle Information" (long name) is automatically generated and
added to the list.
Vehicle info field Displays information on the vehicle selected in
the vehicle list.
Select Logical Links page To select the logical links to be used with the selected ECU
Diagnostics device, and specify their physical connections and
diagnostic protocols.
This page is available for the ECU Diagnostics devices.
Logical Link Name Displays all the logical links available for the
selected vehicle in the ODX database, and lets you select the logical
links that are to be used with the ECU Diagnostics device.
The names of the logical links are specified in the ODX database.
Whether the logical links short names or long names are displayed,
depends on the settings made on the Diagnostics Management page
of the ControlDesk NG Options dialog. Refer to Diagnostics
Management Page ( ControlDesk Next Generation ECU
Diagnostics).
You can select the logical links that are to be used with the ECU
Diagnostics device via the checkboxes on the left of the list. An
activated checkbox indicates that the logical link is selected for ECU
diagnostics. ControlDesk does not allow you to work with more than
one simulated logical link. If you select two or more logical links with
"Simulation" as the physical connection, a dialog opens for you to
specify a valid logical link selection.
If the ODX database contains no vehicle information specification and
the VI_GlobalVehicleInfor (short name) or Global Vehicle Information
(long name) vehicle is selected for use instead, the logical link list
contains only automatically generated logical links. Logical links are
generated according to a specified pattern (described here with the
logical links short names):
n GeneratedLogicalLink_ProtocolShortName
n GeneratedLogicalLink_FunctionalGroupShortName_
ProtocolShortName
n GeneratedLogicalLink_BaseVariantShortName_
FunctionalGroupShortName_ProtocolShortName
n EcuVariantDiagLayerShortName_GeneratedLogicalLink_
BaseVariantShortName_FunctionalGroupShortName
Note
The pattern depends on the structure of the underlying
database.
You can select an identified ECU variant to be used with the ECU
Diagnostics device.
Color of Description
Progress Bar
Green Identification process ran successfully.
Yellow Identification process has finished, no ECU
variant has been identified.
Red Error occurred during identification process.
Note
Variant identification is possible only if communication with the
ECU is available. This means that the ECU is connected, and the
physical connection and the communication parameters have
suitable settings for the logical links.
Connection Lets you select the physical connection for the logical
link. The available physical connections depend on the selected
diagnostic protocol:
Note
Fault read services and DTC variables always use the information
from the protocol specification, regardless of whether the Use
additional protocol information option is enabled or not.
Expand All (Available via context menu) Lets you expand all the
nodes and subnodes of the logical links tree. If enabled, all the logical
links to all hierarchical layers available for the selected vehicle are
displayed in the tree.
Expand Selected Logical Links (Available via context menu) Lets
you display only the selected logical links and their superordinate
nodes in the logical links tree. All the other nodes of the logical links
tree are hidden.
Collapse All (Available via context menu) Lets you collapse all the
subordinate nodes in the logical links tree. If enabled, only the logical
links of the topmost hierarchy level are displayed.
Hide Protocol and Functional Group (Available via context menu)
Lets you specify whether all the logical links to all hierarchical layers
(protocol, functional group, ECU base variant, ECU variant) or only
the logical links to ECU base variants and ECU variants are to be
displayed. If enabled, the logical links to the protocol and functional
group layers are hidden.
Active Logical Links page To specify connection check settings and configure communication
parameters for the logical links selected to be used with the selected
ECU Diagnostics device.
This page is available for the ECU Diagnostics device.
ControlDesk provides the following pages for configuration:
Active Logical Links - To display the communication parameters specified in the ODX
Communication Parameters database for each individual active logical link with their
page configurations, and to specify userdefined values for single
communication parameters.
This page is available for the ECU Diagnostics device. It is located on
the Active Logical Links page.
Select logical link Lets you select one of the logical links selected to
be used with the selected ECU Diagnostics device for further
configuration.
Column Description
Name Displays the name (short name without the prefix "CP_") specified for the
communication parameter in the ODX database.
Active Value1) Displays the currently active value of the communication parameter. A value is
displayed only if the selected logical link is in the 'connected', 'online
calibration started' or 'measuring' state.
Diff (compared Displays a symbol indicating whether the currently active value and the
Active with configured value for the communication parameter are equal or unequal.
Configured)1)
n indicates that the currently active value and the userdefined value
specified for the selected communication parameter are equal.
n indicates that a value different from the userdefined value is currently
active for the communication parameter.
Configured Value Lets you specify a user-defined value for the selected communication
parameter. If you did not specify a user-defined value, the configured value is
equal to the ODX value.
The tendency symbol in the Diff column makes it easy to see whether the
configured value is equal to or differs from the ODX value.
The Configured Value fields are editable only if the Use configured ComParam
values checkbox is selected.
Column Description
Reset Lets you reset the configured value of the communication parameter to its
original ODX value. After you click Reset, the configured value and the ODX
value are identical for the selected communication parameter. Resetting the
configured value does not affect the currently active value until the device
state changes from 'disconnected' to 'connected' with the Use configured
ComParam values checkbox selected.
Diff (compared Displays a symbol indicating whether the configured value and the ODX value
Configured with for the communication parameter are equal or unequal.
ODX)
n indicates that the userdefined value and the original value specified in
the ODX database for the selected communication parameter are equal.
n indicates that a userdefined value different from the default ODX
value has been specified for the communication parameter.
ODX Value Displays the value specified for the communication parameter in the ODX
database.
Unit Displays the unit specified for the communication parameter in the ODX
database.
Value Range Displays the value range specified for the communication parameter in the
ODX database.
Class Displays the COMPARAM class of the communication parameter. The classes are
specified in the PDU API specification. If no appropriate class is available, the
general COM class is used.
1) Column is available only if the Communication Parameters page of the Active Logical Links dialog is opened via the Properties
controlbar.
Tip
You can sort the parameters list alphabetically in ascending or
descending order by clicking the appropriate column header.
Active Logical Links - To specify connection check settings for the active logical links.
Connection Check page This page is available for the ECU Diagnostics device. It is located on
the Active Logical Links page.
Global (Re)Connection Check To specify globally to execute the
TesterPresent service and/or the StartCommunication control primitive
for the ECU Diagnostics device during the connection check and the
reconnection check.
Note
The specified global connection check settings are used as the
default settings for all logical links. If an option is enabled, the
associated logicallinkspecific properties are activated and
evaluated. You can specify this setting individually for each active
logical link (see Logicallink-specific (Re)Connection Check
on page 391). If an option is disabled, it is disabled for all logical
links. Thus, the associated logicallinkspecific properties are
deactivated and do not take effect.
Note
For KLinebased diagnostic protocols, the StartCommunication
control primitive must be executed to initialize the bus. So if you
want to access an ECU via KLine, you are recommended to
select the checkbox, because otherwise communication with an
ECU via KLine might be impossible.
Tip
For example, enabling the Execute StartComm option ensures
that ControlDesk regularly sends TesterPresent messages to
the ECU if enabled in the ODX database. You can disable the
cyclic transmission via the configuration of the COMPARAMs.
Tip
Disabling the Execute StartComm option can be useful in
connection with test automation. It lets you prevent
ControlDesk from sending TesterPresent messages to the
ECU without having to disable cyclic transmission of
TesterPresent messages in the ODX database or in the
configuration of the COMPARAMs.
Note
For KLinebased diagnostic protocols, the StartCommunication
control primitive must be executed to initialize the bus. So if you
want to access an ECU via KLine, you should not disable this
option, because otherwise communication with an ECU via
KLine might be impossible.
Tip
StartCommunication control primitives with the NoOperation
property set to True are indicated by a symbol.
Note
You should not disable the execution of StartCommunication
control primitives whose NoOperation property is set to FALSE.
If you do, a symbol is displayed.
Note
This setting takes effect only if the global Execute StartComm
option is enabled. If it is, the logicallink-specific property is
available (not grayed out), and you can override the setting
individually.
Note
This setting takes effect only if the global Execute TesterPresent
option is enabled. If it is, the logicallink-specific property is
available (not grayed out), and you can override the setting
individually.
Note
This setting takes effect only if the global cyclic connection state
check option is enabled. If it is, the Cyclic connection state check
(executes TesterPresent) property is activated (not grayed out),
and you can override the setting individually. For example,
different TesterPresent configurations can be used for different
logical links, or the check can be disabled for single logical links.
Access This command is available only for platforms that are registered but
not yet added to the currently active experiment of the open project.
You can access this command via:
Ribbon None
Context menu of Platform/Device Manager platform
Shortcut key None
Icon None
Note
This command is not available in the operator mode.
Result Before adding the platform to the active project, ControlDesk opens
the Define platform name dialog prompting you to specify a name for
the platform to be used in the experiment. The name must be unique
within the experiment.
Define platform name Enter a platform name Lets you enter a platform name that is
dialog used for the platform in the experiment. The platform name must be
unique within the experiment.
OK Adds the registered platform to the currently active experiment,
using the specified name as the platform name.
Assembly View
Access This dialog opens when one of the following commands is invoked:
n Go Online ( ControlDesk Next Generation Calibration and Data
Set Management)
n Start Measuring ( ControlDesk Next Generation Measurement
and Recording)
n Start Immediate (Recording) ( ControlDesk Next Generation
Measurement and Recording)
n Start Triggered (Recording) ( ControlDesk Next Generation
Measurement and Recording)
provided one of the following conditions is true:
n The parameter values on the hardware or VPU and in ControlDesk
differ.
n The active experiment contains at least one platform whose start
online calibration behavior is set to 'Prompt user'.
Note
If you specified a different default start online calibration
behavior for a platform/device, ControlDesk equalizes the
parameter values in ControlDesk's mirrored memory and the
connected hardware or VPU without opening the Calibration
Memory dialog and prompting you. For information on this
configuration setting, refer to General Settings Properties
on page 313.
Calibration Memory dialog To get identical parameter values in ControlDesk's mirrored memory
and on the platform/device.
Platform/Device/Page Lists the platforms/devices (and their
memory pages) whose parameter values on the connected dSPACE
real-time hardware, VPU or ECU differ from those in ControlDesk's
mirrored memory.
Data Set CRC Lists the CRC checksum values of the memory pages
in ControlDesk's mirrored memory.
ECU CRC Lists the CRC checksum values of the memory pages on
the connected dSPACE real-time hardware, VPU or ECU.
Command Lets you specify for each individual platform/device and
memory page whether parameter values should be uploaded from
the connected hardware or VPU to ControlDesk, or downloaded from
ControlDesk to the hardware or VPU. The commands that are actually
available depend on the selected platform/device type and the ECUs
memory page concept.
Command Description
Upload1) ControlDesk uploads the parameter values from the hardware or VPU to
ControlDesk.
Download ControlDesk downloads the parameter values from ControlDesk to the
hardware or VPU.
Command Description
Upload connected ControlDesk uploads the values of all the parameters and writable
variables1) measurements that are currently selected for calibration from the hardware
or VPU to the host PC. These are the parameters and writable measurements
that are currently connected to an instrument and visualized on a layout.
They are shown in the Variable Browser with a red chain symbol.
Note
For a platform/device without a working data set, selecting the 'upload
connected variables' option the first time online calibration is started
prevents ControlDesk from creating a working and a reference data set.
However, ControlDesk needs a working data set to save calibration data
in ControlDesk. Use the 'upload' option for the first online transition
instead.
Download connected ControlDesk downloads the values of all the parameters and writable
variables measurements that are currently selected for calibration from ControlDesk to
the hardware or VPU. These are the parameters and writable measurements
that are currently connected to an instrument and visualized on a layout.
They are shown in the Variable Browser with a red chain symbol.
1) If data sets are selected for downloading on calibration start, their parameter values are always downloaded. Refer to How to
Select Additional Data Sets for Downloading on Online Calibration Start ( ControlDesk Next Generation Calibration and Data
Set Management).
Check EPK
Note
ControlDesk does not check whether the topology of the
connected boards is compatible with the topology required
by the realtime application to be loaded to the system, i.e., it
does not check whether the correct Gigalink ports of the
processor boards are used for interconnection.
Clear Flash
Access This command is available only for platforms (except for DS1103 and
SCALEXIO platforms). The hardware must be connected to the host
PC. You can access the command via:
Ribbon None
Context menu of n Project Manager platforms
Result ControlDesk opens the Clear Flash dialog, which lets you completely
or partly clear the flash memory of the selected platform. The
realtime processor(s) must be reset for this. If an application is
running on the selected platform when the Clear Flash dialog opens,
you are asked to stop the running RTP(s).
Access This command is available only for XCP and DCIGSI2 devices whose
device hardware is connected to the host PC. You can access it via:
Ribbon None
Context menu of n Project Manager device
n Platform/Device Manager device
Result All DAQ lists in the ECUs nonvolatile memory are cleared.
Description When you use the Clear Quick Start Configuration command,
ControlDesk requests the ECU to clear the quick start measurement
configuration from its nonvolatile memory. Use the command to clear
a measurement configuration that was stored before into the ECUs
nonvolatile memory, and that you do not want to use any longer.
ControlDesk sets the CLEAR_DAQ_REQ bit using the SET_REQUEST XCP
command.
Clear System
Purpose To clear the entire system you are currently working with.
Note
n This command deletes any registered platform from the
recent platform configuration and not only the platform you
are currently working with.
n Clearing the recent platform configuration is relevant to each
dSPACE software installed on your PC that provides platform
management.
Tip
Before clearing the system, you can use the Manage Recent
Platform Configuration dialog, to export the currently active
recent platform configuration. Importing this configuration
allows you to recover the system after you have cleared it.
Refer to Manage Platforms on page 483.
Collapse
Access This command is available only for the ECU Diagnostics device, and
only in connection with the currently active diagnostics database for
the device.
Ribbon None
Context menu of Project Manager ECU Diagnostics device
active diagnostics database
Purpose To configure the currently active diagnostics database for the ECU
Diagnostics device, or to change the vehicle selection and/or logical
links selection related to the currently active diagnostics database.
Select ODX Files page To specify a diagnostics database for the selected ECU Diagnostics
device.
This page is available for the ECU Diagnostics devices.
ODX database name Lets you enter a name for the ODX
diagnostics database. The default is 'ODX DB'.
When database selection has finished, the ODX database with the
specified name is displayed in the Project Manager. ControlDesk also
adds a folder with this name to the projects folder structure on your
file system. The folder contains all the files belonging to the ODX
database.
Tip
You can specify several diagnostics databases for an ECU
Diagnostics device. You should then change their default names
for clarity and better handling.
Note
Disable automatic ODX version detection only if you are very
familiar with ODX databases and the used database files.
Note
Using the binary format results in faster experiment loading, and
allows you to work with large ODX databases because memory
usage is reduced. On the other hand, generating the binary
format takes some time.
Using the binary format is useful in the following cases:
n Experiments that are frequently loaded, and whose
diagnostics database is modified only rarely
n Experiments that require large ODX databases
Note
For ODX 2.2.0 diagnostics databases, database optimization is
always performed. You cannot change this setting. So if you
work with an ODX 2.2.0 database, ControlDesk always uses the
binary format instead of ODX data for the diagnostics database.
Files list Displays all the files imported so far for the ODX
diagnostics database for your ECU Diagnostics device. The following
information is shown for each file:
n Intended action (column on the left)
Displays the action that is to be performed on the file according to
the ODX database configuration currently active for the ECU
Diagnostics device. Each action is indicated by a symbol.
n File name
n File type
An ODX database typically contains files of the following types:
Extension Description
ODX File format for all the files containing ODX data
ODX-D File format for specifications of diagnostic services and diagnostic jobs
(DIAGLAYERCONTAINER)
ODX-C File format for communication parameter specifications (COMPARAMSPEC)
ODX-V File format for vehicle information specifications (VEHICLEINFOSPEC)
ODX-M File format for specifications of multipleECU jobs (MULTIPLEECUJOBSPEC)
ODX-F File format for ECU flash programming specifications (FLASH)
PDX File container for ODX data (also called PDX package). All the files to be exchanged are
packaged in one file container. The content of the container is described in a container
catalog (PDX package catalog), which is also stored in the PDX package. Besides the
ODX data, a PDX package can contain files of any format.
Note
To execute diagnostic jobs and/or perform ECU flash memory programming, it is
not sufficient that the related files (such as CLASS, JAR, or HEX files) are in the
PDX package. You have to import these files in addition to the PDX package.
The folder with the ODX database can also contain the following file
types and files:
File Description
CLASS, JAR File formats for diagnostic jobs
HEX, MOT, S19, File formats for flash data (ECU Image files)
simulation.txt Contains the simulated ECU.
This file can be used for simulating ECU diagnostics.
File Description
DS_Service_Config<...>.xml Maps ODX semantics to ControlDesk functions.
This configuration file is required for setting up services others than
the default services provided by ControlDesk, for example, for reading
the fault memory and environment data, clearing fault memory entries
and performing measurement and calibration, which can then be used
in ControlDesk. For further information, refer to Basics of the XML
Configuration File ( ControlDesk Next Generation ECU Diagnostics).
File info field Displays information on the file currently selected in
the files list.
Database Template Displays information on the selected ODX
database template (if one is currently selected).
Files Add (Not available if an ODX database template is used) Lets
you import one or more files to the ODX diagnostics database. The
imported files are added to the files list.
The command is also available via context menu. As an alternative,
you can press the Insert or + key.
Files Reload (Not available if an ODX database template is used)
Lets you reload the selected files. If possible, ControlDesk loads the
selected files from their original source paths again.
The command is also available via context menu.
Files Remove (Not available if an ODX database template is used)
Removes the selected files from the files list. File deletion does not
take effect on the diagnostics database configuration currently active
for the ECU Diagnostics device until you click Next or Finish.
The command is also available via context menu. As an alternative,
you can press the Delete or - key to remove the selected files from
the files list.
Files Remove All (Not available if an ODX database template is
used) Removes all the files from the files list.
The command is also available via context menu.
Template Add (Available only if no files have been imported for
the ODX diagnostics database, or if an ODX database template is
used) Lets you import an ODX database template. An ODX database
template is a valid ODX database that cannot be modified.
The ODX Database Templates dialog opens for you to select the ODX
database template.
Via the Select template source dropdown list, you must select
whether to import a builtin or a custom ODX database template.
ControlDesk provides builtin ODX database templates for different
diagnostic protocols (some in binary format). They are displayed for
selection. If you select to add a custom ODX database template,
ControlDesk lists all the custom ODX database templates on the
custom ODX database template source path. The source path is
specified on the Diagnostics Management page of the
ControlDesk NG Options dialog.
After you select an ODX database template, the Database Template
tab displays information on the selected database template. The files
contained in the ODX database template are displayed in the files list.
Template Remove (Available only if an ODX database template is
used) Removes the currently selected ODX database template.
Sort By File Name (Ascending) (Available via context menu) Lets
you sort the files list alphabetically in ascending order by the File
Name column.
Sort By File Extension (Ascending) (Available via context menu)
Lets you sort the files list alphabetically in ascending order by the File
Type column.
Sort By File Action (Ascending) (Available via context menu)
Lets you sort the files list in ascending order by the file action type.
Sort By File Name (Descending) (Available via context menu)
Lets you sort the files list alphabetically in descending order by the File
Name column.
Sort By File Extension (Descending) (Available via context
menu) Lets you sort the files list alphabetically in descending order by
the File Type column.
Tip
You can also sort the files list alphabetically in ascending or
descending order by clicking the appropriate column header.
Show Removed Files (Available via context menu) Lets you specify
to display files that are to be removed from the diagnostics database
configuration currently active for the ECU Diagnostics device in the
files list. If enabled, the files selected for deletion are displayed in the
files list, marked with the symbol. This allows you to check the
files selected for deletion.
Select Vehicle page To select a vehicle for the selected ECU Diagnostics device.
This page is available for the ECU Diagnostics devices.
Vehicle list Displays all the vehicles related to the specified ODX
database, and lets you select a vehicle for the selected ECU
Diagnostics device.
If no vehicle information is specified in the ODX database, a default
vehicle named "VI_GlobalVehicleInfor" (short name) or "Global
Vehicle Information" (long name) is automatically generated and
added to the list.
Vehicle info field Displays information on the vehicle selected in
the vehicle list.
Select Logical Links page To select the logical links to be used with the selected ECU
Diagnostics device, and specify their physical connections and
diagnostic protocols.
This page is available for the ECU Diagnostics devices.
Logical Link Name Displays all the logical links available for the
selected vehicle in the ODX database, and lets you select the logical
links that are to be used with the ECU Diagnostics device.
The names of the logical links are specified in the ODX database.
Whether the logical links short names or long names are displayed,
depends on the settings made on the Diagnostics Management page
of the ControlDesk NG Options dialog. Refer to Diagnostics
Management Page ( ControlDesk Next Generation ECU
Diagnostics).
You can select the logical links that are to be used with the ECU
Diagnostics device via the checkboxes on the left of the list. An
activated checkbox indicates that the logical link is selected for ECU
diagnostics. ControlDesk does not allow you to work with more than
one simulated logical link. If you select two or more logical links with
"Simulation" as the physical connection, a dialog opens for you to
specify a valid logical link selection.
If the ODX database contains no vehicle information specification and
the VI_GlobalVehicleInfor (short name) or Global Vehicle Information
(long name) vehicle is selected for use instead, the logical link list
contains only automatically generated logical links. Logical links are
generated according to a specified pattern (described here with the
logical links short names):
n GeneratedLogicalLink_ProtocolShortName
n GeneratedLogicalLink_FunctionalGroupShortName_
ProtocolShortName
n GeneratedLogicalLink_BaseVariantShortName_
FunctionalGroupShortName_ProtocolShortName
n EcuVariantDiagLayerShortName_GeneratedLogicalLink_
BaseVariantShortName_FunctionalGroupShortName
Note
The pattern depends on the structure of the underlying
database.
You can select an identified ECU variant to be used with the ECU
Diagnostics device.
Color of Description
Progress Bar
Green Identification process ran successfully.
Yellow Identification process has finished, no ECU
variant has been identified.
Red Error occurred during identification process.
Note
Variant identification is possible only if communication with the
ECU is available. This means that the ECU is connected, and the
physical connection and the communication parameters have
suitable settings for the logical links.
Connection Lets you select the physical connection for the logical
link. The available physical connections depend on the selected
diagnostic protocol:
Note
Fault read services and DTC variables always use the information
from the protocol specification, regardless of whether the Use
additional protocol information option is enabled or not.
Expand All (Available via context menu) Lets you expand all the
nodes and subnodes of the logical links tree. If enabled, all the logical
links to all hierarchical layers available for the selected vehicle are
displayed in the tree.
Expand Selected Logical Links (Available via context menu) Lets
you display only the selected logical links and their superordinate
nodes in the logical links tree. All the other nodes of the logical links
tree are hidden.
Collapse All (Available via context menu) Lets you collapse all the
subordinate nodes in the logical links tree. If enabled, only the logical
links of the topmost hierarchy level are displayed.
Hide Protocol and Functional Group (Available via context menu)
Lets you specify whether all the logical links to all hierarchical layers
(protocol, functional group, ECU base variant, ECU variant) or only
the logical links to ECU base variants and ECU variants are to be
displayed. If enabled, the logical links to the protocol and functional
group layers are hidden.
Active Logical Links page To specify connection check settings and configure communication
parameters for the logical links selected to be used with the selected
ECU Diagnostics device.
This page is available for the ECU Diagnostics device.
ControlDesk provides the following pages for configuration:
Active Logical Links - To display the communication parameters specified in the ODX
Communication Parameters database for each individual active logical link with their
page configurations, and to specify userdefined values for single
communication parameters.
This page is available for the ECU Diagnostics device. It is located on
the Active Logical Links page.
Select logical link Lets you select one of the logical links selected to
be used with the selected ECU Diagnostics device for further
configuration.
Column Description
Name Displays the name (short name without the prefix "CP_") specified for the
communication parameter in the ODX database.
Active Value1) Displays the currently active value of the communication parameter. A value is
displayed only if the selected logical link is in the 'connected', 'online
calibration started' or 'measuring' state.
Diff (compared Displays a symbol indicating whether the currently active value and the
Active with configured value for the communication parameter are equal or unequal.
Configured)1)
n indicates that the currently active value and the userdefined value
specified for the selected communication parameter are equal.
n indicates that a value different from the userdefined value is currently
active for the communication parameter.
Configured Value Lets you specify a user-defined value for the selected communication
parameter. If you did not specify a user-defined value, the configured value is
equal to the ODX value.
The tendency symbol in the Diff column makes it easy to see whether the
configured value is equal to or differs from the ODX value.
The Configured Value fields are editable only if the Use configured ComParam
values checkbox is selected.
Column Description
Reset Lets you reset the configured value of the communication parameter to its
original ODX value. After you click Reset, the configured value and the ODX
value are identical for the selected communication parameter. Resetting the
configured value does not affect the currently active value until the device
state changes from 'disconnected' to 'connected' with the Use configured
ComParam values checkbox selected.
Diff (compared Displays a symbol indicating whether the configured value and the ODX value
Configured with for the communication parameter are equal or unequal.
ODX)
n indicates that the userdefined value and the original value specified in
the ODX database for the selected communication parameter are equal.
n indicates that a userdefined value different from the default ODX
value has been specified for the communication parameter.
ODX Value Displays the value specified for the communication parameter in the ODX
database.
Unit Displays the unit specified for the communication parameter in the ODX
database.
Value Range Displays the value range specified for the communication parameter in the
ODX database.
Class Displays the COMPARAM class of the communication parameter. The classes are
specified in the PDU API specification. If no appropriate class is available, the
general COM class is used.
1) Column is available only if the Communication Parameters page of the Active Logical Links dialog is opened via the Properties
controlbar.
Tip
You can sort the parameters list alphabetically in ascending or
descending order by clicking the appropriate column header.
Active Logical Links - To specify connection check settings for the active logical links.
Connection Check page This page is available for the ECU Diagnostics device. It is located on
the Active Logical Links page.
Global (Re)Connection Check To specify globally to execute the
TesterPresent service and/or the StartCommunication control primitive
for the ECU Diagnostics device during the connection check and the
reconnection check.
Note
The specified global connection check settings are used as the
default settings for all logical links. If an option is enabled, the
associated logicallinkspecific properties are activated and
evaluated. You can specify this setting individually for each active
logical link (see Logicallink-specific (Re)Connection Check
on page 425). If an option is disabled, it is disabled for all logical
links. Thus, the associated logicallinkspecific properties are
deactivated and do not take effect.
Note
For KLinebased diagnostic protocols, the StartCommunication
control primitive must be executed to initialize the bus. So if you
want to access an ECU via KLine, you are recommended to
select the checkbox, because otherwise communication with an
ECU via KLine might be impossible.
Tip
For example, enabling the Execute StartComm option ensures
that ControlDesk regularly sends TesterPresent messages to
the ECU if enabled in the ODX database. You can disable the
cyclic transmission via the configuration of the COMPARAMs.
Tip
Disabling the Execute StartComm option can be useful in
connection with test automation. It lets you prevent
ControlDesk from sending TesterPresent messages to the
ECU without having to disable cyclic transmission of
TesterPresent messages in the ODX database or in the
configuration of the COMPARAMs.
Note
For KLinebased diagnostic protocols, the StartCommunication
control primitive must be executed to initialize the bus. So if you
want to access an ECU via KLine, you should not disable this
option, because otherwise communication with an ECU via
KLine might be impossible.
Tip
StartCommunication control primitives with the NoOperation
property set to True are indicated by a symbol.
Note
You should not disable the execution of StartCommunication
control primitives whose NoOperation property is set to FALSE.
If you do, a symbol is displayed.
Note
This setting takes effect only if the global Execute StartComm
option is enabled. If it is, the logicallink-specific property is
available (not grayed out), and you can override the setting
individually.
Note
This setting takes effect only if the global Execute TesterPresent
option is enabled. If it is, the logicallink-specific property is
available (not grayed out), and you can override the setting
individually.
Note
This setting takes effect only if the global cyclic connection state
check option is enabled. If it is, the Cyclic connection state check
(executes TesterPresent) property is activated (not grayed out),
and you can override the setting individually. For example,
different TesterPresent configurations can be used for different
logical links, or the check can be disabled for single logical links.
Configure Platform/Device
Note
This command is not available in the operator mode.
Description ControlDesk successively opens the following dialogs, which let you
configure the selected platform/device:
Note
Whenever you finish the configuration of a platform/device,
ControlDesk checks if the currently configured platform/device is
in the "connected" state. If the connection cannot be
established, ControlDesk displays the Platform/Device State
Overview dialog on page 500 for that platform/device.
Active Logical Links page To specify connection check settings and configure communication
parameters for the logical links selected to be used with the selected
ECU Diagnostics device.
This page is available for the ECU Diagnostics device.
Active Logical Links - To display the communication parameters specified in the ODX
Communication Parameters database for each individual active logical link with their
page configurations, and to specify userdefined values for single
communication parameters.
This page is available for the ECU Diagnostics device. It is located on
the Active Logical Links page.
Select logical link Lets you select one of the logical links selected to
be used with the selected ECU Diagnostics device for further
configuration.
Use configured ComParam values Lets you specify to activate the
user-defined values for ECU communication for all the
communication parameters belonging to the selected logical link. If
the checkbox is selected, the configured values are set automatically
as the active values during the device state transition from
'disconnected' to 'connected'. If the selected logical link is in the
'connected', 'online calibration started' or 'measuring' state, the
configured values are set as the active values when you exit the dialog
via the OK button. If the checkbox is cleared, the configured values
are not taken into account for ECU communication, but the default
ODX values are set as the active values.
Reset All Values Lets you reset all the configured values for the
communication parameters belonging to the selected logical link to
their original ODX values in a single step. After you click the Reset All
Values button, the configured value is equal to the ODX value for
each communication parameter.
Communication parameters list The list displays all the
communication parameters available in the ODX database for the
selected logical link with their configurations, and lets you specify
userdefined values for the single communication parameters. The list
provides the following predefined columns:
Column Description
Name Displays the name (short name without the prefix "CP_") specified for the
communication parameter in the ODX database.
Active Value1) Displays the currently active value of the communication parameter. A value is
displayed only if the selected logical link is in the 'connected', 'online
calibration started' or 'measuring' state.
Diff (compared Displays a symbol indicating whether the currently active value and the
Active with configured value for the communication parameter are equal or unequal.
Configured)1)
n indicates that the currently active value and the userdefined value
specified for the selected communication parameter are equal.
n indicates that a value different from the userdefined value is currently
active for the communication parameter.
Configured Value Lets you specify a user-defined value for the selected communication
parameter. If you did not specify a user-defined value, the configured value is
equal to the ODX value.
The tendency symbol in the Diff column makes it easy to see whether the
configured value is equal to or differs from the ODX value.
The Configured Value fields are editable only if the Use configured ComParam
values checkbox is selected.
Reset Lets you reset the configured value of the communication parameter to its
original ODX value. After you click Reset, the configured value and the ODX
value are identical for the selected communication parameter. Resetting the
configured value does not affect the currently active value until the device
state changes from 'disconnected' to 'connected' with the Use configured
ComParam values checkbox selected.
Diff (compared Displays a symbol indicating whether the configured value and the ODX value
Configured with for the communication parameter are equal or unequal.
ODX)
n indicates that the userdefined value and the original value specified in
the ODX database for the selected communication parameter are equal.
n indicates that a userdefined value different from the default ODX
value has been specified for the communication parameter.
ODX Value Displays the value specified for the communication parameter in the ODX
database.
Unit Displays the unit specified for the communication parameter in the ODX
database.
Value Range Displays the value range specified for the communication parameter in the
ODX database.
Column Description
Class Displays the COMPARAM class of the communication parameter. The classes are
specified in the PDU API specification. If no appropriate class is available, the
general COM class is used.
1)
Column is available only if the Communication Parameters page of the Active Logical Links dialog is opened via the Properties
controlbar.
Tip
You can sort the parameters list alphabetically in ascending or
descending order by clicking the appropriate column header.
Active Logical Links - To specify connection check settings for the active logical links.
Connection Check page This page is available for the ECU Diagnostics device. It is located on
the Active Logical Links page.
Global (Re)Connection Check To specify globally to execute the
TesterPresent service and/or the StartCommunication control primitive
for the ECU Diagnostics device during the connection check and the
reconnection check.
Note
The specified global connection check settings are used as the
default settings for all logical links. If an option is enabled, the
associated logicallinkspecific properties are activated and
evaluated. You can specify this setting individually for each active
logical link (see Logicallink-specific (Re)Connection Check
on page 438). If an option is disabled, it is disabled for all logical
links. Thus, the associated logicallinkspecific properties are
deactivated and do not take effect.
Note
For KLinebased diagnostic protocols, the StartCommunication
control primitive must be executed to initialize the bus. So if you
want to access an ECU via KLine, you are recommended to
select the checkbox, because otherwise communication with an
ECU via KLine might be impossible.
Tip
For example, enabling the Execute StartComm option ensures
that ControlDesk regularly sends TesterPresent messages to
the ECU if enabled in the ODX database. You can disable the
cyclic transmission via the configuration of the COMPARAMs.
Tip
Disabling the Execute StartComm option can be useful in
connection with test automation. It lets you prevent
ControlDesk from sending TesterPresent messages to the
ECU without having to disable cyclic transmission of
TesterPresent messages in the ODX database or in the
configuration of the COMPARAMs.
Note
For KLinebased diagnostic protocols, the StartCommunication
control primitive must be executed to initialize the bus. So if you
want to access an ECU via KLine, you should not disable this
option, because otherwise communication with an ECU via
KLine might be impossible.
Tip
StartCommunication control primitives with the NoOperation
property set to True are indicated by a symbol.
Note
You should not disable the execution of StartCommunication
control primitives whose NoOperation property is set to FALSE.
If you do, a symbol is displayed.
Note
This setting takes effect only if the global Execute StartComm
option is enabled. If it is, the logicallink-specific property is
available (not grayed out), and you can override the setting
individually.
Note
This setting takes effect only if the global Execute TesterPresent
option is enabled. If it is, the logicallink-specific property is
available (not grayed out), and you can override the setting
individually.
Note
This setting takes effect only if the global cyclic connection state
check option is enabled. If it is, the Cyclic connection state check
(executes TesterPresent) property is activated (not grayed out),
and you can override the setting individually. For example,
different TesterPresent configurations can be used for different
logical links, or the check can be disabled for single logical links.
Advanced Settings page To specify diagnostic settings and general settings for the selected
ECU Diagnostics device.
This page is available for the ECU Diagnostics device.
DiagCom parameter limits check Lets you select whether the
limits of the DiagCom parameters in the Diagnostics Instrument are
checked.
n If the checkbox is cleared, ControlDesk does not check the value
limits defined in the ODX database. All the values that are valid for
the current data type are permitted.
n If the checkbox is selected, ControlDesk checks for valid parameter
values and lets you use only values that are within the allowed
value range defined in the ODX database.
In both cases the computation method specified in the ODX database
is applied to the parameter values. By default, the parameter limits
check is enabled.
For some parameter types (for example, parameters which use the
SCALE-LINEAR computation method) the value limits cannot be fully
determined since there can be more than one valid value interval for a
parameter. Currently, ControlDesk supports working with one valid
value interval only. For this reason, not all valid intervals might be
available for such a parameter. You can prevent ControlDesk from
checking the value ranges by clearing the checkbox, but remember
that the physical datatype-specific value ranges are still active and
the computation method is still applied to the value.
Start online calibration behavior Lets you specify ControlDesk's
default behavior when online calibration is started. You can specify
how parameter values are to be up/downloaded if the parameter
values in ControlDesk and on the hardware or VPU differ. The
available default behaviors depend on the ECU's memory page
concept, the selected platform/device type, and on whether
calibration memory segments are defined in the ECU's A2L file or not.
Display status information (Available only for measurement and
calibration devices, the ECU Diagnostics device, and MicroAutoBox)
Lets you specify whether to bring up message boxes displaying status
information for the selected platform/device.
n If you select the checkbox, message boxes containing
platform/devicespecific status information are displayed.
n If you clear the checkbox, the display of message boxes is
suppressed. This can be useful, for example, if you want to
automate calibration, measurement, and diagnostic tasks using
ControlDesk's remote-control interface.
Automatic reconnect behavior (Available only for measurement
and calibration devices and the ECU Diagnostics device, and the XIL
API MAPort platform) Lets you specify ControlDesk's default behavior
when the unplugged state is detected for the selected
platform/device:
n Resume measurement and online calibration: ControlDesk
periodically tries to reestablish the logical connection. When the
platform/device is reconnected to the platform/device hardware,
ControlDesk resumes measurement and online calibration.
n Disconnect Platform/Device: ControlDesk does not try to
reestablish the logical connection for the platform/device, but sets
the platform/device state to disconnected.
Resume online calibration behavior (Available only for
measurement and calibration devices, the ECU Diagnostics device,
and DS1007 PPC Processor Board, DS1202 MicroLabBox,
MicroAutoBox, SCALEXIO, and XIL API MAPort platforms) Lets you
specify ControlDesk's default behavior when online calibration is
started and measurement is resumed after ControlDesk has
Assignment Description
Mode
Assign to any ControlDesk assigns the platform to a registered and unassigned platform of the relevant platform type,
equal platform according to the following assignment settings:
n Alias name
n Board name
n Connection type
n Net client
n Port address
n XIL API MAPort implementation
The above assignment settings are platform-type-specific. The list below shows the settings available for the
platform types:
n DS1005, DS1006, DS1103: Port address and/or Board name, Connection type, Net Client (only for the
Net connection type)
n DS1104: Board name
n MicroAutoBox: Board name (optional), Connection type, Net Client
n Multiprocessor System: Connection type
Multiprocessor System members: Port address
n DS1007, DS1202 MicroLabBox, SCALEXIO: IP address or Board name
n VEOS: none
n XIL API MAPort platform: XIL API MAPort implementation
Assign to identical (Not available for the VEOS and XIL API MAPort platforms) ControlDesk assigns the platform to registered
platform and unassigned dSPACE hardware of the relevant platform type, according to the following assignment
settings:
n Connection type
n Serial number
n MAC address
The above assignment settings are platform-type-specific. The list below shows the settings available for the
platform types:
n DS1005, DS1006, DS1103, DS1104, MicroAutoBox, Multiprocessor System members: Serial number
n Multiprocessor System: Connection type
Multiprocessor System members: Serial number
n DS1007, DS1202 MicroLabBox, SCALEXIO: MAC address
Note
If several platforms are assigned to dSPACE hardware in one step
(for example, if you call the Refresh Platform Configuration
command), the assignment modes are applied to the platforms
in a certain order:
1. Assign to identical platform
2. Assign to any equal platform
3. Assign to first available platform
Note
Currently, only DS1007 systems containing one DS1007
processor board are supported.
Note
Currently, only DS1007 systems containing one DS1007
processor board are supported.
Port address Lets you specify the base address of the board as set
with the DIP switches or the rotary switches on the board.
Board name Lets you specify the board name used to identify the
board or processing unit.
Serial number Lets you specify the serial number of the board. The
number is used to uniquely identify the hardware.
Connection type Lets you specify the connection type of the
platform hardware.
n Select BUS if the platform hardware is installed in the host PC or in
an expansion box connected to the host PC via a bus interface.
n Select NET if the platform hardware is connected to the host PC
via Ethernet.
Note
n Since a DS1104 R&D Controller Board is installed in a PCI slot
in the host PC, no connection type (BUS or NET) has to be
configured for the DS1104 platform.
Net client Lets you specify the network client for assignment as an
IP address or alias.
Alias name Lets you specify the alias name of the connection that is
used for assignment.
IP address Lets you specify the network client for assignment as an
IP address.
MAC address Lets you specify the MAC address of the selected
processing unit of the SCALEXIO system, the selected processor board
of the DS1007 platform, or selected platform of the DS1202
MicroLabBox platform. The MAC address is used to uniquely identify
the hardware.
Camera Selection page To select a connected camera or a virtual camera for the selected
Video Capturing device.
This dialog is available for the Video Capturing device.
Automatic assignment Lets you select a connected camera
automatically.
DirectShow List of Camera Lets you select one of the cameras
connected to your PC to be assigned to the selected device. All
cameras that are available with DirectShow are listed below the
DirectShow object.
Cameras in Use Displays the cameras already associated to another
Video Capturing device in the current experiment. They cannot be
selected.
Virtual File Lets you select a virtual camera to replay recorded
videos and specify the video file you want to display. If you select the
checkbox or double-click the entry, the Select a video file to serve as a
virtual camera dialog opens for you to select the video file. The
supported video formats are AVI, MPG and WMV. You can specify
the video behavior settings for the selected file:
Setting Description
Auto-repeat Once finished, the video is automatically repeated.
Online Calibration The video starts after you have started online calibration.
Restart Video on Measurement Start The video automatically restarts with every new measurement.
Measurement The video starts upon initializing a measurement.
Virtual Stream Lets you select a virtual camera to play streamed
video data. If you select the checkbox or double-click the entry, the
Select streaming source dialog opens for you to specify the streaming
source setting. The supported format is MJPEG (Motion JPEG).
Setting Description
URL Lets you specify the URL of the streaming source.
User Displays the user name extracted from the specified URL, if available, or lets you
subsequently enter or modify the user name if the specified URL requires the user
name specification.
The field is editable only if Use input assist is selected.
Password Displays the password extracted from the specified URL, if available, or lets you
subsequently enter or modify a password if the specified URL requires the password
specification.
The field is editable only if Use input assist is selected.
Use input Enables or disables the User and Password edit fields. If the checkbox is selected, the
assist fields are writable, and there is a bidirectional link between the URL and the
user/password values. If the specified URL does not contain a user/password
combination in the appropriate syntax, the URL is updated with the user and password
values when you have entered them. If the checkbox is cleared, the User and Password
fields are readonly.
General Configuration page To specify general multiprocessor configuration settings for the
selected Multiprocessor System platform.
This page is available for the Multiprocessor System platform.
Available platforms Displays the registered multiprocessor
platforms that match the current configuration but are not yet
assigned to any Multiprocessor System platform in the current
ControlDesk project, and lets you select one of them to assign the
Multiprocessor System platform. After selection, the members of the
selected multiprocessor system and their settings are displayed on the
Multiprocessor Configuration page.
Mode Lets you select the assignment mode for the platform.
Assignment Description
Mode
Assign to first (Not available for the Multiprocessor System platform) ControlDesk automatically assigns the platform to the
available platform first registered and unassigned platform of the relevant platform type it finds.
Assignment Description
Mode
Assign to any ControlDesk assigns the platform to a registered and unassigned platform of the relevant platform type,
equal platform according to the following assignment settings:
n Alias name
n Board name
n Connection type
n Net client
n Port address
n XIL API MAPort implementation
The above assignment settings are platform-type-specific. The list below shows the settings available for the
platform types:
n DS1005, DS1006, DS1103: Port address and/or Board name, Connection type, Net Client (only for the
Net connection type)
n DS1104: Board name
n MicroAutoBox: Board name (optional), Connection type, Net Client
n Multiprocessor System: Connection type
Multiprocessor System members: Port address
n DS1007, DS1202 MicroLabBox, SCALEXIO: IP address or Board name
n VEOS: none
n XIL API MAPort platform: XIL API MAPort implementation
Assign to identical (Not available for the VEOS and XIL API MAPort platforms) ControlDesk assigns the platform to registered
platform and unassigned dSPACE hardware of the relevant platform type, according to the following assignment
settings:
n Connection type
n Serial number
n MAC address
The above assignment settings are platform-type-specific. The list below shows the settings available for the
platform types:
n DS1005, DS1006, DS1103, DS1104, MicroAutoBox, Multiprocessor System members: Serial number
n Multiprocessor System: Connection type
Multiprocessor System members: Serial number
n DS1007, DS1202 MicroLabBox, SCALEXIO: MAC address
Note
If several platforms are assigned to dSPACE hardware in one step
(for example, if you call the Refresh Platform Configuration
command), the assignment modes are applied to the platforms
in a certain order:
1. Assign to identical platform
2. Assign to any equal platform
3. Assign to first available platform
Note
For Multiprocessor System platforms, the connection type and
IP address are specified for the multiprocessor system. Thus,
these settings are valid for all the processor boards belonging to
the multiprocessor system. Changes made for one processor
board automatically affect the settings of all the other processor
boards of the multiprocessor system.
Interface Selection (CAN-, To select the physical interface for the selected device.
LIN-, and FlexRay-based This dialog is available for devices that require a CAN, LIN, or FlexRay
devices) page interface.
Lets you select the physical CAN, LIN, or FlexRay interface to be
assigned to the selected device. Connected interfaces are listed with
their IDs and serial numbers (S/N).
CAN and LIN channels of SCALEXIO or VEOS are listed only if they
were explicitly made available to the device before. Refer to:
n How to Configure a CAN Bus Monitoring Device on page 159
n How to Configure a LIN Bus Monitoring Device on page 164
n How to Configure an XCP on CAN Device on page 211
n How to Configure a CCP Device on page 168
For an overview of the interfaces for accessing a communication bus
supported by ControlDesk, refer to Supported Interfaces for
Accessing a Communication Bus on page 43.
Automatic assignment Lets you select a connected interface
automatically.
If several interfaces are connected to the host PC, ControlDesk selects
an interface in the following way:
1. A connected bus channel of SCALEXIO or VEOS takes priority over
connected PCbased interfaces.
If CAN FD mode is enabled, CANFDcapable channels have
priority.
Setting Description
User identifier Lets you specify the user ID of the interface
to be assigned to the selected device.
Controller index Lets you select the interface's controller to
be assigned to the selected device.
Note
n The user ID string is limited to 124 characters.
n If you work with an interface which is connected to the host
PC via Ethernet, specify the user ID as an IP address.
Tip
Selecting a specific ECU interface (DCIGSI1) is necessary only if
you have several DCIGSI1s connected to the host PC.
KLine Interface Selection To select the physical KLine interface for the selected logical link.
page This dialog is available for the ECU Diagnostics device.
Lets you select the physical KLine interface to be assigned to the
selected logical link. All the KLine interfaces that are connected to
the host PC are listed with their serial numbers.
For information on the supported interfaces, refer to Supported
KLine Interfaces on page 47.
Automatic assignment Lets you select a connected KLine
interface automatically.
n If only one KLine interface is connected to the host PC, it is
assigned to the logical link regardless of its serial number.
n If several KLine interfaces are connected to the host PC, the
interface that has the smallest serial number is assigned to the
logical link.
Note
ControlDesk can use only one (physical) K-Line interface at a
time.
Member Configuration To view the members that belong to the selected Multiprocessor
page System platform and specify configuration settings for them.
This page is available for the Multiprocessor System platform.
Multiprocessor configuration Lets you view the processors that
belong to the selected Multiprocessor System platform with their port
addresses or serial numbers.
Processor name Displays the name of the selected member. The
name is taken from the variable description (SDF file) of the selected
Multiprocessor System platform.
Port address (Available only if "Assign to identical platform" or
"Assign to any equal platform" is selected as the assignment mode)
Lets you specify the board's port address as specified with the DIP
switches or the rotary switches on the board. You can adapt the port
addresses to the requirements of your realtime hardware, since the
assignment between processor names and port addresses determines
which application is assigned to which processor.
Serial number (Enabled only if the "Assign to identical platform"
assignment mode is selected) Lets you specify the serial number of
the board. The number is used to identify the identical hardware.
Network Adapter page To select the network adapter for the selected device.
This dialog is available for the XCP on Ethernet device.
Lets you select the network interface card to communicate with the
ECU or VPU. The names and IP addresses of the network interface
cards currently available on your host PC are displayed. You can select
one of the network interface cards available in the host PC.
Select Logical Links page To select the logical links to be used with the selected ECU
Diagnostics device, and specify their physical connections and
diagnostic protocols.
This page is available for the ECU Diagnostics devices.
Logical Link Name Displays all the logical links available for the
selected vehicle in the ODX database, and lets you select the logical
links that are to be used with the ECU Diagnostics device.
The names of the logical links are specified in the ODX database.
Whether the logical links short names or long names are displayed,
depends on the settings made on the Diagnostics Management page
Note
The pattern depends on the structure of the underlying
database.
Color of Description
Progress Bar
Green Identification process ran successfully.
Yellow Identification process has finished, no ECU
variant has been identified.
Red Error occurred during identification process.
Note
Variant identification is possible only if communication with the
ECU is available. This means that the ECU is connected, and the
physical connection and the communication parameters have
suitable settings for the logical links.
Connection Lets you select the physical connection for the logical
link. The available physical connections depend on the selected
diagnostic protocol:
Note
Fault read services and DTC variables always use the information
from the protocol specification, regardless of whether the Use
additional protocol information option is enabled or not.
Expand All (Available via context menu) Lets you expand all the
nodes and subnodes of the logical links tree. If enabled, all the logical
links to all hierarchical layers available for the selected vehicle are
displayed in the tree.
Expand Selected Logical Links (Available via context menu) Lets
you display only the selected logical links and their superordinate
nodes in the logical links tree. All the other nodes of the logical links
tree are hidden.
Collapse All (Available via context menu) Lets you collapse all the
subordinate nodes in the logical links tree. If enabled, only the logical
links of the topmost hierarchy level are displayed.
Hide Protocol and Functional Group (Available via context menu)
Lets you specify whether all the logical links to all hierarchical layers
(protocol, functional group, ECU base variant, ECU variant) or only
the logical links to ECU base variants and ECU variants are to be
displayed. If enabled, the logical links to the protocol and functional
group layers are hidden.
Select ODX Files page To specify a diagnostics database for the selected ECU Diagnostics
device.
This page is available for the ECU Diagnostics devices.
ODX database name Lets you enter a name for the ODX
diagnostics database. The default is 'ODX DB'.
When database selection has finished, the ODX database with the
specified name is displayed in the Project Manager. ControlDesk also
adds a folder with this name to the projects folder structure on your
file system. The folder contains all the files belonging to the ODX
database.
Tip
You can specify several diagnostics databases for an ECU
Diagnostics device. You should then change their default names
for clarity and better handling.
Note
Disable automatic ODX version detection only if you are very
familiar with ODX databases and the used database files.
Note
Using the binary format results in faster experiment loading, and
allows you to work with large ODX databases because memory
usage is reduced. On the other hand, generating the binary
format takes some time.
Using the binary format is useful in the following cases:
n Experiments that are frequently loaded, and whose
diagnostics database is modified only rarely
n Experiments that require large ODX databases
Note
For ODX 2.2.0 diagnostics databases, database optimization is
always performed. You cannot change this setting. So if you
work with an ODX 2.2.0 database, ControlDesk always uses the
binary format instead of ODX data for the diagnostics database.
Files list Displays all the files imported so far for the ODX
diagnostics database for your ECU Diagnostics device. The following
information is shown for each file:
n Intended action (column on the left)
Displays the action that is to be performed on the file according to
the ODX database configuration currently active for the ECU
Diagnostics device. Each action is indicated by a symbol.
n File name
n File type
An ODX database typically contains files of the following types:
Extension Description
ODX File format for all the files containing ODX data
ODX-D File format for specifications of diagnostic services and diagnostic jobs
(DIAGLAYERCONTAINER)
ODX-C File format for communication parameter specifications (COMPARAMSPEC)
ODX-V File format for vehicle information specifications (VEHICLEINFOSPEC)
ODX-M File format for specifications of multipleECU jobs (MULTIPLEECUJOBSPEC)
ODX-F File format for ECU flash programming specifications (FLASH)
PDX File container for ODX data (also called PDX package). All the files to be exchanged are
packaged in one file container. The content of the container is described in a container
catalog (PDX package catalog), which is also stored in the PDX package. Besides the
ODX data, a PDX package can contain files of any format.
Note
To execute diagnostic jobs and/or perform ECU flash memory programming, it is
not sufficient that the related files (such as CLASS, JAR, or HEX files) are in the
PDX package. You have to import these files in addition to the PDX package.
The folder with the ODX database can also contain the following file
types and files:
File Description
CLASS, JAR File formats for diagnostic jobs
HEX, MOT, S19, File formats for flash data (ECU Image files)
simulation.txt Contains the simulated ECU.
This file can be used for simulating ECU diagnostics.
File Description
DS_Service_Config<...>.xml Maps ODX semantics to ControlDesk functions.
This configuration file is required for setting up services others than
the default services provided by ControlDesk, for example, for reading
the fault memory and environment data, clearing fault memory entries
and performing measurement and calibration, which can then be used
in ControlDesk. For further information, refer to Basics of the XML
Configuration File ( ControlDesk Next Generation ECU Diagnostics).
File info field Displays information on the file currently selected in
the files list.
Database Template Displays information on the selected ODX
database template (if one is currently selected).
Files Add (Not available if an ODX database template is used) Lets
you import one or more files to the ODX diagnostics database. The
imported files are added to the files list.
The command is also available via context menu. As an alternative,
you can press the Insert or + key.
Files Reload (Not available if an ODX database template is used)
Lets you reload the selected files. If possible, ControlDesk loads the
selected files from their original source paths again.
The command is also available via context menu.
Files Remove (Not available if an ODX database template is used)
Removes the selected files from the files list. File deletion does not
take effect on the diagnostics database configuration currently active
for the ECU Diagnostics device until you click Next or Finish.
The command is also available via context menu. As an alternative,
you can press the Delete or - key to remove the selected files from
the files list.
Files Remove All (Not available if an ODX database template is
used) Removes all the files from the files list.
The command is also available via context menu.
Template Add (Available only if no files have been imported for
the ODX diagnostics database, or if an ODX database template is
used) Lets you import an ODX database template. An ODX database
template is a valid ODX database that cannot be modified.
The ODX Database Templates dialog opens for you to select the ODX
database template.
Via the Select template source dropdown list, you must select
whether to import a builtin or a custom ODX database template.
ControlDesk provides builtin ODX database templates for different
diagnostic protocols (some in binary format). They are displayed for
selection. If you select to add a custom ODX database template,
ControlDesk lists all the custom ODX database templates on the
custom ODX database template source path. The source path is
specified on the Diagnostics Management page of the
ControlDesk NG Options dialog.
After you select an ODX database template, the Database Template
tab displays information on the selected database template. The files
contained in the ODX database template are displayed in the files list.
Template Remove (Available only if an ODX database template is
used) Removes the currently selected ODX database template.
Sort By File Name (Ascending) (Available via context menu) Lets
you sort the files list alphabetically in ascending order by the File
Name column.
Sort By File Extension (Ascending) (Available via context menu)
Lets you sort the files list alphabetically in ascending order by the File
Type column.
Sort By File Action (Ascending) (Available via context menu)
Lets you sort the files list in ascending order by the file action type.
Sort By File Name (Descending) (Available via context menu)
Lets you sort the files list alphabetically in descending order by the File
Name column.
Sort By File Extension (Descending) (Available via context
menu) Lets you sort the files list alphabetically in descending order by
the File Type column.
Tip
You can also sort the files list alphabetically in ascending or
descending order by clicking the appropriate column header.
Show Removed Files (Available via context menu) Lets you specify
to display files that are to be removed from the diagnostics database
configuration currently active for the ECU Diagnostics device in the
files list. If enabled, the files selected for deletion are displayed in the
files list, marked with the symbol. This allows you to check the
files selected for deletion.
Select Vehicle page To select a vehicle for the selected ECU Diagnostics device.
This page is available for the ECU Diagnostics devices.
Vehicle list Displays all the vehicles related to the specified ODX
database, and lets you select a vehicle for the selected ECU
Diagnostics device.
If no vehicle information is specified in the ODX database, a default
vehicle named "VI_GlobalVehicleInfor" (short name) or "Global
Vehicle Information" (long name) is automatically generated and
added to the list.
Vehicle info field Displays information on the vehicle selected in
the vehicle list.
Connect Platform/Device
Access This command is available only for enabled platforms/devices that are
currently in the 'disconnected' state. You can access it via:
Ribbon None
Context menu of Project Manager platform/device
Purpose To add columns to the platform/device list or to remove them from it.
Result ControlDesk opens a dialog displaying the columns that can be added
to the list. To add a column, drag it from the dialog to the
platform/device list header. To remove a column from the list, drag its
header below the list.
Disable Platform/Device
Access This command is available only for platforms/devices that are currently
enabled and for which online calibration is stopped. You can access it
via:
Ribbon None
Context menu of Project Manager platform/device
Shortcut key None
Icon (Checkbox)
Note
This command is not available in the operator mode.
Note
n A disabled platform is disconnected and deactivated for the
experiment. It is still available in your recent hardware
configuration.
n All accesses to a disabled device are blocked. A disabled
device is not displayed in the Platform/Device Manager.
Disconnect Platform/Device
Access This command is available only for platforms/devices that are currently
in the 'connected' state. You can access it via:
Ribbon None
Context menu of Project Manager platform/device
Shortcut key None
Icon None
Ribbon None
Context menu of n Platform/Device Manager DS1007
platform
n Platform/Device Manager Multiprocessor
System platform
Shortcut key None
Icon None
Result The Edit Processor Names dialog opens for you to enter processor
names and apply them to the processor boards belonging to the
multiprocessor system.
The processor names are editable only if online calibration has not
been started, if no application is currently running on the selected
platform, and if the platform is not yet assigned to the experiment.
Otherwise, the processor names are only displayed.
Edit Processor Names dialog To specify processor names for the boards of the selected
multiprocessor system.
Platforms Lists the selected DS1007 or Multiprocessor System
platform with all its members.
Processor Name Displays the processor names already specified for
the members of the multiprocessor system, and lets you enter new
processor names and modify existing names of the members. Only
the edit fields that are marked by colored background are writable.
The processor names must be unique for each member of a
multiprocessor system. The valid characters are 'a ... z', 'A ... Z',
'0 ... 9', and '_'. A processor name must not exceed 8 characters.
After you click OK or Apply to confirm the new valid processor
names, the names are stored in the recent platform configuration.
Enable Platform/Device
Access This command is available only for platforms/devices that are currently
disabled. You can access it via:
Ribbon None
Context menu of Project Manager platform/device
Shortcut key None
Icon (Checkbox)
Note
This command is not available in the operator mode.
Expand
Purpose To save the flight recorder data currently available in a USB mass
storage device connected to the platform hardware.
Result ControlDesk opens the USB Flight Recorder Contents dialog, which
displays the connected platform hardware and lists the files which
were written to the USB mass storage device during flight recording.
Flight recorder data is written in BIN format. You can select BIN files
from the list and upload them to the host PC. Multiple selection is
possible by pressing Ctrl or Shift when clicking a file. The target
folder is selected in a standard Windows dialog. After uploading, you
can import the BIN files and save them to measurement data file via
the Measurement Data folder in the Project Manager. Refer to Import
(Measurement Data File) ( ControlDesk Next Generation
Measurement and Recording).
You can also delete obsolete BIN files from the USB mass storage
device.
Description The dialog's status bar displays information on the selected file (file
type, modification date, and size).
USB Flight Recorder To display the files stored in a USB mass storage device, and to
Contents dialog upload BIN files to the host PC or delete BIN files from the USB mass
storage device. In the dialog, you can access the following commands
via the context menu:
Upload Lets you upload the selected BIN files to the specified target
folder on the host PC.
Delete Lets you delete the selected BIN files from the USB mass
storage device.
Filter
Result ControlDesk opens the Filter dialog for you to filter the
platform/device list.
Dialog settings You can filter the platform/device list via the Filter dialog. The
platform/device list shows the platforms/devices that match the
specified filter settings, and the Platform/Device Manager displays the
specified filter.
Flash ECU
Access This command is available only for DCIGSI1, DCIGSI2, XCP on CAN,
and XCP on Ethernet devices, and if online calibration has not been
started. You can access it via:
Ribbon None
Context menu of n Project Manager device
Result The dSPACE ECU Flash Programming Tool allows you to program the
flash memory of ECUs equipped with a DCIGSI1 or DCIGSI2, ECUs
with XCP on CAN, or ECUs with XCP on Ethernet. For details on the
dSPACE ECU Flash Programming Tool and on how to work with it,
refer to the ECU Flash Programming document.
Access This command is available only for the ECU Diagnostics device, if the
device is in the disconnected state, and if at least one logical link is
selected in the active ODX diagnostics database for the device. You
can access it via:
Ribbon None
Context menu of n Project Manager ECU Diagnostics device
Result ControlDesk opens the ECU Flash Programming dialog, which lets you
specify the ECU to be flashed, select the flash session and the data to
be programmed to the ECU, and start the ECU flash programming
operation.
ECU Flash Programming To specify the ECU to be flashed and the data to be programmed to
dialog the ECU, and start the ECU flash programming operation.
Note
For KLinebased diagnostic protocols, the StartCommunication
control primitive must be executed first to initialize the bus.
Otherwise, communication with an ECU via KLine is impossible.
Set Options to Default Lets you reset the Flash job contains start
communication option for the selected flash session to its default
value. The default value is specified on the Diagnostics Management
page in the ControlDesk NG Options dialog. Refer to Diagnostics
Access This command is available only if a project is open. You can access it
via:
Ribbon Platforms Experiment
Context menu of Project Manager
Shortcut key None
Icon
Note
This command is not available in the operator mode.
2. The Select Variable Description dialog on page 481 lets you select
an A2L, DBC, SDF, or LDF file corresponding to the
platform/device.
3. The Select ECU Image File dialog on page 483 lets you select a
corresponding HEX, MOT or S19 file. This dialog is available only
for measurement and calibration devices.
These dialogs are not all required by every platform/device type. The
Project Wizard displays only the dialogs needed by the
platform/device type you have selected.
You must configure the selected platform/device appropriately to
associate it with the hardware if you want to work online (see
Configure Platform/Device on page 431).
Add Platform/Device dialog To specify the type and name of the platform/device to be added to
the experiment and/or project.
Platform/device name Displays the default name for the
platform/device, or lets you specify a different name to be used for
the platform/device in the current experiment.
Note
The platform/device name must be unique within the
experiment. It must differ from other platform/device names by
at least one character. Differences in upper/lower case are not
sufficient.
Note
n It is recommended to not enable this option for
multiprocessor platforms.
n Since an ECU Diagnostics device cannot be made available to
several experiments of the same project, you should not
make it a global device.
Tip
In the ControlDesk NG Options dialog, you can specify import
options for variable descriptions in the SDF and FIBEX formats.
Refer to Variables Page ( ControlDesk Next Generation
Variable Management).
Tip
In the ControlDesk NG Options dialog, you can specify import
options for variable descriptions in the SDF and FIBEX formats.
Refer to Variables Page ( ControlDesk Next Generation
Variable Management).
Select ECU Image File dialog (Available only for measurement and calibration devices) To specify an
ECU Image file for the selected variable description.
Select ECU Image file Enter the path and name of the ECU Image
file (HEX, MOT, S19, file) or select it via the BROWSE button.
ControlDesk can handle ECU Image files that contain code and data
or only data.
< Back Opens the previous dialog.
Finish Confirms the specified configuration and closes the dialog.
This button is enabled only if an ECU Image file is specified.
Cancel Closes the dialog without saving any of your settings.
Manage Platforms
Purpose To display and manage the platforms that were registered in your
system.
Manage Recent Platform To manage the registered platforms and import or export the
Configuration dialog configuration of registered platforms.
Recent Platform Configuration Lists the platforms that were
registered in your system and whose registration data is stored in the
recent platform configuration, and displays some information on the
registered platforms. The platform list also provides an Active switch
for each platform. Via the switch, you can specify whether to display
the platform as an assignable platform during platform addition or
configuration in ControlDesk. If the switch is 0, the platform is
hidden. It is neither contained in the Available Platforms dropdown
lists in the Add Platform/Device or Configure platforms dialog, nor
displayed in the Platform/Device Manager. If the switch is 1, the
platform is listed in the Available Platforms dropdown lists and
displayed in the Platform/Device Manager.
Commands The following commands are available via buttons and
from the menus or context menus:
Group by Active View menu Lets you group the platforms according to their Active
State state.
Group by View menu Lets you group the platforms according to their
Platform Type platform type.
Import n Button Lets you select the XML file containing the platform
n File menu configuration you want to import. The currently active
n Shortcut key: Alt+I platform configuration is replaced by the content of
the imported XML file.
Note
You are recommended to import only recent
platform configurations that you previously
exported.
Refresh n View menu Lets you refresh the visualization of the recent platform
n Context menu of a configuration in the dialog.
platform
n Shortcut key: F5
Remove n Button Lets you remove the currently selected platform from
n Edit menu the recent hardware configuration. The platform is no
n Context menu of a longer available as an assignable registered platform
platform and is no longer displayed in the Platform/Device
n Shortcut key: Del Manager.
Note
You are recommended to perform the Refresh
Interface Connections command after removing a
platform that required registration at the device
driver.
Note
You are recommended to perform the Refresh
Interface Connections command after removing a
platform that required registration at the device
driver.
Remove Context menu of a Lets you remove the selected Multiprocessor System
Multiprocessor Multiprocessor System platform from the recent hardware configuration.
platform However, all the DS1005 or DS1006 processor boards
of the multiprocessor system are converted to single
platforms, which are then listed as separate platforms
in the platform list.
Select All n Context menu of a Lets you select all the items in the platform list.
platform
n Shortcut key: Ctrl+A
Sort View menu Lets you sort the platform list alphabetically in
Alphabetically ascending order by platform names.
MAPort - Disconnect
Access This command is available only for the XIL API MAPort platform, and
if an MAPort configuration is loaded. You can access this command
via:
Ribbon None
Context menu of n Project Manager XIL API MAPort
platform
n Platform/Device Manager XIL API
MAPort platform
Shortcut key None
Icon None
Access This command is available only for the XIL API MAPort platform and
only if online calibration has not been started. You can access this
command via:
Ribbon None
Context menu of n Project Manager XIL API MAPort
platform
n Platform/Device Manager XIL API
MAPort platform
Shortcut key None
Icon None
Mouse Use the right mouse button to drag an
MAPort configuration file from Windows
Explorer to the platform in the
Platform/Device Manager.
MAPort - Reload
Access This command is available only for the XIL API MAPort platform, and
if an MAPort configuration is currently loaded. You can access this
command via:
Ribbon None
Context menu of n Project Manager XIL API MAPort
platform
n Platform/Device Manager XIL API
MAPort platform
Shortcut key None
Icon None
Description ControlDesk disconnects the MAPort, and then reloads the MAPort
configuration from its original source path.
Memory Segments
Note
This command is not available in the operator mode.
Result ControlDesk opens the Memory Segments dialog, which lets you
manage the memory segments of the selected device.
For instructions, refer to How to Customize Calibration Memory
Segments on page 139.
Memory Segments dialog To view, customize, add, and delete memory segments of the
memory of the selected device.
List of memory segments Lets you view, add, and customize the
names, start and end addresses, sizes, segment types, memory types,
and descriptions of the memory segments for the selected device. The
end address of a memory segment cannot be edited directly but
results from the segment's start address and size. You can also specify
individually for each memory segment whether it is used to evaluate
the memory pages of your ECU when online calibration is started,
and whether it is to be exported when an ECU Image file is
generated. A symbol representing the memory segments origin is
displayed to the left of the segment name. The symbols have the
following meanings:
Symbol Description
The memory segment was taken from the A2L file.
Note
To apply your selection, the ECU Image Creation column must
remain displayed. If it is hidden (because the Memory-segment-
based ECU Image creation checkbox is not selected), the whole
ECU memory image is always exported.
Network View
Pause
Access This command is available only for the VEOS platform, and if an
application is currently running. You can access this command via:
Ribbon None
Context menu of Platform/Device Manager VEOS platform -
application
Shortcut key None
Icon None
Dialog settings Seek connected platforms on startup Lets you specify whether to
search for registered platforms when ControlDesk is started manually
(Platform Seeking) or via automation (Platform Seeking via Tool
Automation).
n If the checkbox is selected, ControlDesk scans the recent hardware
configuration and searches:
n For registered platforms connected via bus interface
n For connected platforms that do not need to be registered
(MicroAutoBox connected via bus, and DS1104)
n For registered and connected SCALEXIO systems, DS1007
boards, MicroLabBoxes, and VEOS
The platforms that are found are displayed in the Platform/Device
Manager.
Note
When you enable this option, the startup process can be
affected by long timeouts.
Note
n API version 1.0 does not support the DS1007,
MicroLabBox, and SCALEXIO systems with multiple
processing units. Use version 2.0 instead.
n API version 1.0 is provided for compatibility reasons only.
It is being supported for the last time with dSPACE
Release 2016A.
n Version 2.0:
API version 2.0 was introduced with dSPACE Release 2014A. It is
the successor of API version 1.0 and has all its features. Unlike
API version 1.0, API version 2.0 will be developed further.
Version 2.0 is selected by default.
Note
Platform automation API versions 1.0 and 2.0 are incompatible.
To migrate to API version 2.0 and reuse automation scripts
originally developed according to API version 1.0, you might
have to perform some migration steps.
Refer to Platform Management Automation API Versions
on page 545.
You can select the version via automation, as shown in the following
Python listing:
# Select platform automation API version 2.0
Application.PlatformManagement.PlatformAutomationAPIVersion = Enums.AutomationAPIVersion.APIVersion2
Platform/Device Manager
Network client
DS1005 platform
SCALEXIO platform
SCALEXIO application
Application processes
SCALEXIO processing unit
XCP on CAN device
, , , , Measurement is running.
1) An application is running on the
, , , ,
hardware or in VEOS. XIL API MAPort
platform: The simulation has been
started at the MAPort.
,
2) An application was loaded from the flash
memory of the dSPACE real-time
hardware. The application is running.
3)
, , , , The application is stopped, and the
hardware or VEOS is reset. XIL API
MAPort platform: The simulation at the
MAPort is stopped.
4) The application that was loaded from the
flash memory of the dSPACE real-time
hardware is stopped. This icon is
available for DS1007 and MicroLabBox
platforms only.
5)
(None) The application is loaded on the
hardware, but it was terminated. It must
be reloaded.
(None) 6) The status of the application is undefined
or unknown.
n The undefined status is only a
temporary status. For example, it can
occur when the application is loaded
but not all application processes
belonging to the parent application
are loaded, started or stopped yet.
When the loading process is
completed, the status of the
application changes from undefined
to running (from flash), stopped (from
flash), or unknown.
n The unknown status occurs if not all
the application processes belonging
to the parent application can be
found (e.g., because they are
missing), or if the contained
application processes have different
statuses(e.g., some application
processes are running, some are
stopped).
Platform/Device Description
Membership
Platform/device that belongs to the currently
active experiment.
Global platform/device that belongs to the
project and also to the currently active
experiment.
Global platform/device that belongs to the
project but not to the currently active
experiment.
Platform that is registered or connected to
the host PC without having to be registered,
but does not belong to the project.
For platforms/devices that belong to a ControlDesk experiment, the
name used for the platform/device in the experiment is displayed next
to the membership icon.
For details on experimentspecific and projectglobal
platforms/devices, refer to Basics of Platforms/Devices on page 25.
Views of platforms For SCALEXIO platforms, the Platform/Device
Manager provides two views of the displayed platforms. You can
switch between them via context menu.
n Assembly view: The platform's mechanical topology is displayed.
The platform is displayed with assembly components, such as
racks and units arranged according to the assembly structure.
n Network view: The networkbased view of the registered
hardware is displayed. The platform is displayed without assembly
components like racks and units.
Positioning the controlbar You can shift controlbars to any
position inside the working area or dock them at the border of the
working area. For instructions on positioning controlbars, refer to
How to Customize the Screen Arrangement ( ControlDesk
Next Generation User Interface Handling).
Platform/Device State To get details on the configuration and connection state for
Overview dialog platforms/devices in the active experiment.
State Displays a symbol representing the current configuration and
connection state individually for each platform/device. The symbols
have the following meanings:
Symbol Description
The platform/device hardware or VEOS is connected
and configured correctly. Starting online calibration
for the platform/device is possible. 1)
Symbol Description
The platform/device hardware or VEOS is either not
connected or not configured correctly. Starting
online calibration for the platform/device will fail. 2)
1)
For an ECU Diagnostics device containing more than one logical link selected for use
this means that at least one of the logical links is connected and configured
correctly, and that online calibration is possible for these logical links. The Project
Manager displays status information individually for each logical link.
2) For an ECU Diagnostics device this means that none of the contained logical links
selected for use is connected or configured correctly, and that starting online
calibration will fail for each logical link.
Properties (Platform/Device)
Access This command is available only for the following platforms: DS1005,
DS1006, DS1103, DS1104, MicroAutoBox, and Multiprocessor
System. The platform hardware must be connected to the host PC.
You can access the command via:
Ribbon None
Context menu of n Project Manager platform
n Platform/Device Manager platform
Result ControlDesk opens a standard Open dialog that lets you select an
application or variable description file. The file must be in the PPC/x86
or SDF file format.
Access This command is available only for the following platforms: DS1005,
DS1006, DS1104, MicroAutoBox, and Multiprocessor System. The
platform hardware must be connected to the host PC. You can access
the command via:
Ribbon None
Context menu of n Project Manager platform
n Platform/Device Manager platform
Result ControlDesk opens a standard Open dialog that lets you select an
application. The application file does not need to be within an
experiment.
The application is loaded to the flash memory, copied to the RAM
and then started.
Note
An application that was already in the RAM will be overwritten
when you load an application to the flash memory.
Access This command is available only for the following platforms: DS1007
and DS1202 MicroLabBox. The platform hardware must be connected
to the host PC. You can access the command via:
Ribbon None
Context menu of n Project Manager platform
n Platform/Device Manager platform
Note
Relevant for DS1007 platforms: The command is available only
for DS1007 systems registered as a single processor system.
Loading an application to the flash memory of a DS1007 system
consisting of two or more DS1007 PPC Processor Boards is not
possible.
Result A standard Open dialog is opened for you to select an application file
or the corresponding variable description file. The file must be in the
RTA or SDF file format. After loading, the application state is STOPPED.
Note
An application that was already in the RAM will be overwritten
when you load an application to the flash memory.
from the flash memory to the RAM. If the platform is rebooted, the
application in the flash memory is automatically started.
Access This command is available only for the following platforms: DS1007
and DS1202 MicroLabBox. The platform hardware must be connected
to the host PC. You can access the command via:
Ribbon None
Context menu of n Project Manager platform
Note
Relevant for DS1007 platforms: The command is available only
for DS1007 systems registered as a single processor system.
Loading an application to the flash memory of a DS1007 system
consisting of two or more DS1007 PPC Processor Boards is not
possible.
Result ControlDesk opens a standard Open dialog that lets you select an
application. The application file does not need to be within an
experiment.
The application is loaded to the flash memory, copied to the RAM
and then started.
Note
An application that was already in the RAM will be overwritten
when you load an application to the flash memory.
Access This command is available only for the following platforms: DS1005,
DS1006, DS1103, DS1104, MicroAutoBox, and Multiprocessor
System. An application must be currently loaded. You can access the
command via:
Ribbon None
Context menu of n Project Manager platform
Access This command is available only for SCALEXIO and VEOS platforms,
and only if an experiment is active and no variable description has
been added to the selected platform yet. You can access this
command via:
Ribbon None
Context menu of Project Manager platform
Shortcut key None
Icon None
Result ControlDesk opens a standard Open dialog for you to add a realtime
application (RTA) file to the selected SCALEXIO platform or an offline
simulation application (OSA) file to the selected VEOS platform,
respectively.
The new application is inserted into the project tree under the
platform node and automatically activated.
Access This command is available only for the following platforms: DS1007,
DS1202 MicroLabBox, SCALEXIO, and VEOS. For DS1007,
MicroLabBox, and SCALEXIO platforms, the platform hardware must
be connected to the host PC. You can access the command via:
Ribbon None
Context menu of n Project Manager platform
n Platform/Device Manager platform
Note
Loading an application to a SCALEXIO system requires a valid
SCALEXIO_RTLIB license on the host PC. The version of the
license must match the version of the RTLib (real-time library)
used on the SCALEXIO processing unit. For details, refer to
Experimenting Using a SCALEXIO System ( SCALEXIO System
Overview).
Result A standard Open dialog is opened for you to select an application file
or the corresponding variable description file:
n DS1007, MicroLabBox, SCALEXIO: You can select an RTA or SDF
file.
n VEOS: You can select an OSA or SDF file.
Access This command is available only for the following platforms: DS1007,
DS1202 MicroLabBox, SCALEXIO, and VEOS. For DS1007,
MicroLabBox, and SCALEXIO platforms, the platform hardware must
be connected to the host PC. You can access the command via:
Ribbon None
Context menu of n Project Manager platform
n Platform/Device Manager platform
Note
Loading an application to a SCALEXIO system requires a valid
SCALEXIO_RTLIB license on the host PC. The version of the
license must match the version of the RTLib (real-time library)
used on the SCALEXIO processing unit. For details, refer to
Experimenting Using a SCALEXIO System ( SCALEXIO System
Overview).
Result A standard Open dialog opens for you to select an application file or
variable description file:
n DS1007, MicroLabBox, SCALEXIO: The selected file must be in the
RTA or SDF file format.
n VEOS: The selected file must be in the OSA or SDF file format.
The selected application is loaded to the RAM of the selected
hardware or to VEOS. After downloading, the application is started
automatically.
VEOS: The Platform/Device Manager displays the loaded offline
simulation application, the virtual ECU(s) and the (optional)
environment VPU contained in the OSA file.
Result n For the VEOS and the SCALEXIO platform, using the command
interrupts the connection to the platform temporarily.
n For all the other platforms, ControlDesk refreshes the interface
connections by resetting the device drivers of the platform
connections (via bus interface or Ethernet) and reinitializing the
Platform/Device Manager with the information from the recent
hardware configuration. The device drivers for bus connections are
always reset, but the device drivers for network connections are
reset only if at least one platform using the network connection is
registered.
Note
For bus devices, ControlDesk checks only if the corresponding
CAN, LIN or FlexRay interface is connected to the host PC.
Platform/Device State To get details on the configuration and connection state for
Overview dialog platforms/devices in the active experiment.
Symbol Description
The platform/device hardware or VEOS is connected
and configured correctly. Starting online calibration
for the platform/device is possible. 1)
The platform/device hardware or VEOS is either not
connected or not configured correctly. Starting
online calibration for the platform/device will fail. 2)
1)
For an ECU Diagnostics device containing more than one logical link selected for use
this means that at least one of the logical links is connected and configured
correctly, and that online calibration is possible for these logical links. The Project
Manager displays status information individually for each logical link.
2) For an ECU Diagnostics device this means that none of the contained logical links
selected for use is connected or configured correctly, and that starting online
calibration will fail for each logical link.
Register Platforms
Tip
You do not need to register boards that support the plug & play
feature. The Platform/Device Manager automatically registers
them. This applies to:
n DS1104
Register Platforms dialog To specify the register settings for a single processor or controller
board, a multiprocessor system, MicroAutoBox, MicroLabBox, or a
SCALEXIO system, and to get information on the platforms registered
so far.
Platforms Lets you select the platform type being registered.
Platform properties Lets you view and specify the register settings
for the platform. The available properties depend on the selected
platform type.
Property Description / Refer to
Common Properties
Multiprocessor type Common Properties on page 301
Platform name Lets you specify a unique name for the selected platform. After
registration, the name is displayed in ControlDesk Next Generation's
Platform/Device Manager.
The valid characters are 'a ... z', 'A ... Z', '0 ... 9', '_', '-' and ' '. The
name must not start or end with an underline, hyphen or blank.
If you do not specify a platform name, ControlDesk displays a default
name in the Platform/Device Manager.
Note
You cannot subsequently add processor boards to a DS1007
system that is already registered.
Note
You cannot subsequently add processing units to a SCALEXIO
system that is already registered.
Each processing unit has an edit field to specify its connection parameter
value and an edit field to specify a unique name for it. After registration,
the name is displayed in ControlDesk Next Generation's Platform/Device
Manager.
The valid characters are 'a ... z', 'A ... Z', '0 ... 9', '_', '-' and ' '. The
name must not start or end with an underline, hyphen or blank. If you
do not specify a custom name for a processing unit, ControlDesk
displays a default name for it in the Platform/Device Manager.
Scan for available Lets you scan the local network for connected platform hardware.
processor boards/ Depending on the platform type to be registered, ControlDesk opens
processing units/ the Scan Local Network for Processor Boards, the Scan Local Network for
platforms Processing Units or the Scan Local Network for Platforms dialog and
displays all the platform hardware found in the network. Refer to Scan
Local Network for Processor Boards/ Processing Units /Platforms dialog
on page 518.
Model Access Port Properties
Implementation Lets you select the MAPort implementation for the XIL API MAPort
platform.
The list displays all the supported XIL API MAPort implementations. The
XIL API MAPort platform analyzes the IMF files in the standard XIL API
folder (ProgramData\ASAM\XIL\Implementation) to determine the installed
XIL API MAPort implementations.
Product name Model Access Port Properties on page 337
Product version Model Access Port Properties on page 337
Vendor name Model Access Port Properties on page 337
XIL API version Model Access Port Properties on page 337
Multiprocessor Configuration Properties
Network client Assignment Properties on page 281
Processors Lets you specify the number of processors belonging to the
Note
You cannot subsequently add members to a multiprocessor system
that is already registered.
Note
If you register a multiprocessor system based on DS1005 or
DS1006 boards, the connection type is specified for the
multiprocessor system, so this setting is valid for all the
DS1005/DS1006 processor boards belonging to the
multiprocessor system. The network client is specified individually
for each processor board belonging to the multiprocessor
system.
Register DS230X Platform To specify the port address of a DS230x board connected to the
dialog processor board to be registered. When you register a DS1005,
DS1006 or DS1007 processor board connected to a DS230x board,
Note
Unlike the DS1005 or DS1006, the jumper on a DS230x board
connected to a DS1007 processor board must be closed. This
ensures that the PHSbus connection functions correctly. Refer to
Board Overview (as of Revision DS2302-04) ( PHS Bus System
Hardware Reference)
Tip
You need not register I/O boards which support the plug & play
feature. These boards are registered by ControlDesk
automatically.
Scan Local Network for To scan the local network for connected platform hardware and
Processor Boards/ select one or more platforms to register.
Processing Units /Platforms Type Lets you select the filter item type you want to use to filter the
dialog results list. If you select 'None', no filtering is applied.
Value Lets you enter a filter string.
Match whole word Lets you specify to search only for a matching
pattern substring.
(Re)scan Lets you start a new scan process. ControlDesk scans the
subnetwork your host PC is connected to for connected processor
boards/processing units/platforms matching the specified filter
settings, and refreshes the results list.
List of available processor boards/processing units/platforms
Displays all the processor boards, processing units and platforms that
the specified filter found in the network during the scan process. The
results list contains the IP address, MAC address, board name, system
name and serial number for each processor board, processing unit or
platform that was found.
To select a processor board, processing unit or platform for
registration, click its entry and then press the button. The
selected element is moved to the list of selected processor
boards/processing units/platforms, where you can transfer its
connection parameter value to the Register Platforms dialog.
Tip
You can multiselect processing units and processor boards.
Reload
Access This command is available only for the following platforms: DS1007,
DS1202 MicroLabBox, SCALEXIO, and VEOS. An application must be
currently loaded. You can access the command via:
Ribbon None
Context menu of Platform/Device Manager platform
application
Shortcut key None
Icon None
Note
Loading an application to a SCALEXIO system requires a valid
SCALEXIO_RTLIB license on the host PC. The version of the
license must match the version of the RTLib (real-time library)
used on the SCALEXIO processing unit. For details, refer to
Experimenting Using a SCALEXIO System ( SCALEXIO System
Overview).
Access This command is available only for the following platforms: DS1007,
DS1202 MicroLabBox, SCALEXIO, and VEOS. An application must be
currently loaded. You can access the command via:
Ribbon None
Context menu of Platform/Device Manager platform
application
Shortcut key None
Icon None
Note
Loading an application to a SCALEXIO system requires a valid
SCALEXIO_RTLIB license on the host PC. The version of the
license must match the version of the RTLib (real-time library)
used on the SCALEXIO processing unit. For details, refer to
Experimenting Using a SCALEXIO System ( SCALEXIO System
Overview).
Reload Application
Access This command is available only for SCALEXIO and VEOS platforms,
and if an experiment is active and an active application is selected.
You can access it via:
Ribbon None
Context menu of Project Manager platform application
Shortcut key None
Icon None
Description ControlDesk reimports the active application, using the path of the
initially imported application file.
Tip
If you know that the application has a new path, use Replace
Application on page 525 to reach your destination faster.
Reload System
Reload Multiple Reload Lets you specify whether to reload the specified file for the
Platforms/Devices dialog selected platform or device in the currently active experiment. A
selected checkbox indicates that the platform or device will be
reloaded.
A warning icon is displayed next to the checkbox if the configuration
is not valid (e.g., if the specified file does not exist).
Platform name in experiment Displays the name of the platform
or device in the currently active experiment.
Platform type Displays the type of the selected platform or device.
File path Displays the name and path of the simulation application
or variable description file that is currently loaded to the platform or
device. Click the Browse button to select another file to reload.
If there is a problem with the file currently loaded to the platform or
device, a warning icon is displayed next to the file path entry. Its tool
tip provides information on the reason.
Remove Application
Access This command is available only for SCALEXIO and VEOS platforms,
and only in combination with an inactive application. You can access
it via:
Ribbon None
Context menu of Project Manager platform inactive
application
Shortcut key None
Icon None
Access This command is available only for the ECU Diagnostics device, and
only in combination with an inactive diagnostics database. You can
access it via:
Ribbon None
Context menu of Project Manager ECU Diagnostics device
inactive diagnostics database
Shortcut key None
Icon None
Rename Platform/Device
Access This command is available only if online calibration has not been
started. It is not available for global platforms/devices. You can access
it via:
Ribbon None
Context menu of Platform/Device Manager platform/device
Shortcut key F2
Icon None
Note
This command is not available in the operator mode.
Result The Rename Platform/Device dialog opens for you to rename the
selected platform/device.
Rename Platform/Device To specify another name for the selected platform or device in the
dialog experiment.
Enter a platform name Lets you enter a new name for the selected
platform/device. After you click OK to confirm the new
platform/device name, the platform/device name is updated wherever
it is used in the experiment.
Since platform/device names must be unique within an experiment,
the OK button is enabled only if the new platform/device name is
valid.
Note
Global platforms/devices cannot be renamed.
Replace Application
Access This command is available only for SCALEXIO and VEOS platforms,
and if an experiment is active and an active application is selected.
You can access it via:
Ribbon None
Context menu of Project Manager platform application
Shortcut key None
Icon None
Result The selected application is replaced with a new one. The new
application is activated.
Access This command is available only for the MicroAutoBox platform. You
can access it via:
Ribbon None
Context menu of Platform/Device Manager MicroAutoBox
platform
Shortcut key None
Icon None
Purpose To display the system times of MicroAutoBox and the host PC, and to
set the system time on MicroAutoBox to the system time of the
host PC.
Synchronizing the system times of your MicroAutoBox and your
host PC is useful if you want to use flight recording.
Result The Set MicroAutoBox System Time dialog opens for you to display
the current system times on MicroAutoBox and the host PC and to
synchronize the system times.
Set MicroAutoBox System To display the current system times of MicroAutoBox and the host PC,
Time dialog and to set the system time on MicroAutoBox to the system time on
the host PC.
Host PC date and time Displays the date and system time of the
host PC.
MicroAutoBox date and time Displays the date and system time
of the MicroAutoBox.
Set Time Lets you set the system time on MicroAutoBox to the
system time of the host PC.
Note
This command is not available in the operator mode.
Result You can specify whether the Supported platform/device types list
contains all the installed platform/device types or only those you have
a valid license for. If the option is selected, only the licensed
platform/devices types are available for selection.
Single Step
Access This command is available only for the VEOS platform, and if an
application is currently pausing or stopped. You can access this
command via:
Ribbon None
Context menu of Platform/Device Manager VEOS platform -
application
Shortcut key None
Icon None
Result The next step of an offline simulation is executed. You can run all the
steps separately in consecutive order.
Description You can use this command to inspect an offline simulation in detail.
Each time you use the command, the next simulation step is
executed.
Start
Access This command is available only for the following platforms: DS1007,
DS1202 MicroLabBox, SCALEXIO, and VEOS, and if an application is
loaded. You can access this command via:
Ribbon None
Context menu of Platform/Device Manager - platform
application
Access This command is available only for the XIL API MAPort platform, and
if an MAPort configuration is loaded. You can access this command
via:
Ribbon None
Context menu of Platform/Device Manager - platform
application
Shortcut key None
Icon None
Stop
Access This command is available only for the following platforms: DS1007,
DS1202 MicroLabBox, SCALEXIO, and VEOS, and if an application is
currently running. You can access this command via:
Ribbon None
Context menu of Platform/Device Manager - platform
application
Shortcut key None
Icon None
Access This command is available only for the XIL API MAPort platform, and
if an application is currently running. You can access this command
via:
Ribbon None
Context menu of Platform/Device Manager - platform
application
Shortcut key None
Icon None
Stop RTP
Access This command is available only for the following platforms: DS1005
PPC Board, DS1006 Processor Board, DS1103 PPC Controller Board,
DS1104 R&D Controller Board, and MicroAutoBox, and only if online
calibration has not been started. You can access this command via:
Ribbon None
Context menu of n Project Manager platform
n Platform/Device Manager - platform
Stop RTPs
Unload
Access This command is available only for the following platforms: DS1007,
DS1202 MicroLabBox, SCALEXIO, and VEOS. An application must be
loaded, but online calibration must not have been started. You can
access this command via:
Ribbon None
Context menu of Platform/Device Manager platform
application
Shortcut key None
Icon None
Description ControlDesk unloads the application from the memory of the selected
platform.
Update Firmware
Access This command is available only for dSPACE real-time platforms and
only if online calibration has not been started. You can access this
command via:
Ribbon None
Context menu of n Project Manager platform
Note
n It is recommended to perform the Refresh Interface
Connections command after updating the firmware.
n After updating the MicroAutoBox firmware, you have to turn
off MicroAutoBox. The firmware changes take effect after
restart.
For the other platforms the dialog settings vary or you have to use
another tool.
n RapidPro system:
How to Update RapidPro Firmware ( RapidPro System Hardware
Installation Guide)
n DS1552 MultiI/O Module of a MicroAutoBox:
DS1401UpdateExtIO
The Update Firmware Wizard provides the following dialogs to
configure and start a firmware update.
Specifics for SCALEXIO platforms To ensure real-time applications
are downloaded without restrictions or side effects, and with proper
functionality, the following conditions must be fulfilled:
n All the processing units of a SCALEXIO platform contain the
firmware version that is available in the current RCP and HIL
software installation.
n All the components of a SCALEXIO system (for example, real-time
PC and I/O boards) contain the same firmware version.
Firmware version deviations for a SCALEXIO platform are indicated in
the Platform/Device Manager. The affected hardware components
are marked by the symbol. You can find associated warning
messages in the Log Viewer.
Note
Note the following restrictions when you use a SCALEXIO
system:
n The Update Firmware Wizard supports SCALEXIO systems as
of dSPACE Release 2015B. If you want to update the
firmware version on a SCALEXIO system to an earlier version,
you have to use ControlDesk Next Generation from an earlier
dSPACE Release.
n If your SCALEXIO system contains a DS2655M2 Digital I/O
Module, a firmware update from firmware version 3.2 or
earlier to a firmware version 3.3 or later, might lead to an
error and the update process is then stopped.
To finish the firmware update you have to do the following
steps:
n Reboot the SCALEXIO system.
n Call the Refresh Interface Connections command in the
Platform Manager.
n Repeat the firmware update process.
n If your SCALEXIO system contains one or more new hardware
components that are not already supported by the currently
active firmware on the SCALEXIO RealTime PC, a firmware
update might lead to an error and the update process is then
aborted.
To finish the firmware update, perform the following steps:
n Restart the SCALEXIO system.
n Call the Refresh Interface Connections command in the
Platform Manager.
n Repeat the firmware update process.
Select Mode dialog Lets you select the firmware update mode.
n Firmware update mode
The firmware handling process is configured for updating all
firmware components of the realtime hardware to a later version.
n Firmware repair mode
The firmware handling process is configured for repairing the
selected firmware components of the realtime hardware by
reloading the same firmware versions.
Update/Repair
n In firmware update mode, the Update button is enabled to start a
firmware update process if later firmware versions are available in
the firmware archive than those currently loaded to the hardware.
n In firmware repair mode, the Repair button is enabled to start a
firmware repair process, if the firmware versions of the loaded
firmware components and the versions of the specified firmware
archive are identical, and if you have selected at least one
firmware component in the Update column to be repaired.
< Back Opens the previous dialog to change the selected firmware
archive.
OK Closes the Update Firmware Wizard without starting a firmware
update.
Result If the flash memory contains flight recorder data, the data is uploaded
and saved to a measurement data file.
Registering a platform The following listing shows you how to register a platform.
Note
To use the listing below in a script to register a platform:
n You must specify the platform type and further information
in the section Define constants used to register a
platform. The platform must not have been registered yet.
n Platform automation API version 2.0 must be selected. For
details on the platform automation API versions, refer to
Platform Management Automation API Versions
on page 545.
#--------------------------------------------------------------------------------------------------
# Define constants used to register a platform.
#--------------------------------------------------------------------------------------------------
# Platform type to register. Uncomment the line with the platform you want to register.
PlatformTypeString = None
#PlatformTypeString = "DS1005"
#PlatformTypeString = "DS1006"
#PlatformTypeString = "DS1007"
#PlatformTypeString = "DS1103"
#PlatformTypeString = "MABX"
#PlatformTypeString = "SCALEXIO"
(...)
def RegisterPlatform(self):
if None != PlatformTypeString:
# Show platform window.
if self.ControlDeskApplication.MainWindow.Windows.Contains(Resources.PlatformTab):
self.ControlDeskApplication.MainWindow.Windows.Item(Resources.PlatformTab).Show()
# Add UniqueName.
PlatformInformation['name'] = self.RegisteredPlatform.UniqueName
# Add ConnectionState.
PlatformInformation['displayname'] = self.RegisteredPlatform.DisplayName
Adding a registered The following listing shows you how to add a registered platform to
platform to an experiment an experiment.
class MainDemoController(object):
def __init__(self):
(...)
# The registered platform.
self.RegisteredPlatform = None
Adding a platform/device The following listing shows you how to add an XCP on CAN device
and configure some of its properties.
class MainDemoController(object):
def __init__(self):
# The ControlDesk Application object.
self.ControlDeskApplication = None
# The enums object.
self.Enums = None
(...)
# The platform used in this demo.
self.DemoPlatform = None
def Initialize(self):
(...)
# Start ControlDesk.
self.ControlDeskApplication = Dispatch("ControlDeskNG.Application")
# Create the enums object.
self.Enums = Enums(self.ControlDeskApplication)
(...)
def CreateAndEditPlatform(self):
(...)
# Add XCPonCAN platform.
self.DemoPlatform = self.ControlDeskApplication.ActiveExperiment.Platforms.Add(
self.Enums.PlatformType.XCPonCAN)
(...)
# Change the baud rate.
self.DemoPlatform.CANSettings.BaudRate = 100000
# Select virtual CAN interface (needed to start the online calibration with the CalDemo device).
self.DemoPlatform.InterfaceSelection.AvailableChannels.Item(0).Select()
self.DemoPlatform.GeneralSettings.StartOnlineCalibrationBehavior = self.Enums./
OnlineCalibrationBehavior.UploadConnectedVariables
Editing the processor names The following listing shows you how to edit the names of the
in a DS1007-based processors in a DS1007-based multiprocessor system. The listing is
multiprocessor system not part of the PlatformHandling.py demo script.
It is presupposed that a DS1007-based multiprocessor system with
two DS1007 boards, each of which provides two cores, is registered.
class MainDemoController(object):
(...)
def EditDS1007ProcessorNames(self):
DS1007Platform = self.ControlDeskApplication.PlatformManagement.Platforms[0]
ProcessorNames = DS1007Platform.GetProcessorNames()
ProcessorNames[0][0].Name = "Master"
ProcessorNames[0][1].Name = "Slave_B"
ProcessorNames[1][0].Name = "Slave"
ProcessorNames[1][1].Name = "Slave_C"
DS1007Platform.ApplyProcessorNames(ProcessorNames)
Adding a global The following listing shows you how to add a CCP device as a global
platform/device device to a project.
class MainDemoController(object):
(...)
def AddAndRemoveGlobalPlatform(self):
(...)
# Add a global CCP platform.
GlobalPlatform = self.ControlDeskApplication.ActiveProject.Platforms.Add(self.Enums.PlatformType.CCP)
(...)
# Remove global platform
GlobalPlatformName = GlobalPlatform.Name
GlobalPlatform = None
self.ControlDeskApplication.PlatformManagement.Platforms.Remove(GlobalPlatform.Name)
self.ControlDeskApplication.ActiveExperiment.Platforms.Remove(GlobalPlatformName)
self.ControlDeskApplication.ActiveProject.Platforms.Remove(GlobalPlatformName)
Adding a variable The following listing shows how to add three variable descriptions
description and ECU image files to an XCP on CAN device and activate the
second one.
Connecting and online The following listing shows how to connect to the XCP on CAN
calibration device of the CalDemo ECU and then start and stop online
calibration.
# Import: The os module is used to start the CalDemo process.
import os
(...)
# Path of the CalDemo exe.
CalDemoPath = os.path.abspath(os.path.join(ScriptPath, "..\..\..\CalDemo\CalDemo.exe"))
(...)
class MainDemoController(object):
(...)
def ConnectAndStartOnlineCalibration(self):
# Access the XCPonCAN platform by the item method.
XCPonCANPlatform = self.ControlDeskApplication.ActiveExperiment.Platforms.Item(self.DemoPlatform.Name)
(...)
# Start CalDemo platform.
os.startfile(CalDemoPath)
# Connect device.
XCPonCANPlatform.Connect()
(...)
# Start online calibration.
self.ControlDeskApplication.CalibrationManagement.StartOnlineCalibration()
# Stop online calibration.
self.ControlDeskApplication.CalibrationManagement.StopOnlineCalibration()
# Disconnect platform.
XCPonCANPlatform.Disconnect()
Two platform management There are two platform management automation API versions in
automation API versions ControlDesk.
Platform management automation API version 1.0 API
version 1.0 is compatible with the platform management automation
version of ControlDesk 5.1 and earlier.
Note
n API version 1.0 does not support the DS1007, MicroLabBox,
and SCALEXIO systems with multiple processing units. Use
version 2.0 instead.
n API version 1.0 is provided for compatibility reasons only. It is
being supported for the last time with dSPACE Release
2016A.
Tip
API version 2.0 lets you access platform properties from the
ControlDesk experiment context via the AssignedPlatform
property, which is available only in ControlDesk. Do not use this
property without the ControlDesk experiment context.
As an example, the following Python listing shows how to use
the AssignedPlatform property to count the number of
application parts in an application running on a
SCALEXIO system. It is presupposed that the SCALEXIO system is
assigned to a SCALEXIO platform in the experiment.
SCLXExp = Application.ActiveExperiment.Platforms.Item(0)
SCLXProcessingUnit = SCLXExp.AssignedPlatform.ProcessingUnits.Item(0)
SCLXProcessingUnit.ApplicationParts.Count
Selecting the platform Via ControlDesk NG Options dialog You can select the platform
management automation management automation API version on the Platform Management
API version Page in the ControlDesk NG Options dialog, as shown in the
following illustration:
Migrating platform Platform automation API versions 1.0 and 2.0 are incompatible. To
management automation migrate to API version 2.0 and reuse automation scripts originally
developed according to API version 1.0, you might have to perform
some migration steps.
Migrating Python scripts If you use Python and want to migrate
to platform management automation API version 2.0, you do not
have to perform any migration steps unless you access a
SCALEXIO system and/or VEOS in the Platform/Device Manager
context via automation.
To access a SCALEXIO system and/or VEOS via automation from the
context of the Platform/Device Manager, you have to adapt your
automation scripts.
This table shows the SCALEXIO access via API Version 2.0:
API Version 2.0
Registering a SCALEXIO Platform with One Processing Unit
SCLX_Reg_Info = Application.PlatformManagement.CreatePlatformRegistrationInfo(Enums.PlatformType.SCALEXIO)
SCLX_PU_Info = SCLX_Reg_Info.RegistrationInfos.Add()
SCLX_PU_Info.IPAddress = "192.168.2.10"
SCLX_Platform = Application.PlatformManagement.RegisterPlatform(SCLX_Reg_Info)
Accessing a Processing Unit
# Access a registered SCALEXIO processing unit via API version 2.0
SCALEXIOPlatform = Application.PlatformManagement.Platforms.Item(0)
SCALEXIOProcessingUnit = SCALEXIOPlatform.ProcessingUnits.Item(0)
SCALEXIOProcessingUnit.BoardHardware.CPU
u'Intel(R) Core(TM) i7 CPU 920'
Accessing an Application Loaded to a Platform
# Access a loaded SCALEXIO real-time application via API version 2.0
SCALEXIOPlatform = Application.PlatformManagement.Platforms.Item(0)
RTA = SCALEXIOPlatform.RealTimeApplications.Item(0)
RTA.Name
u'Scalexio_Demo'
Tip
The C# listing below shows how to avoid using a version-specific
platform interface by accessing the platform dynamically:
Platform Handling
Platform-Related Interfaces
Related interfaces
Interface Description
PlatformManagement / IPmPlatformManagement IPmPlatformManagement Interface
<<Interface>> ( ControlDesk Next Generation
Automation)
Platforms / IPmPlatforms <<Collection>> Interface to access the platforms.
( ControlDesk Next Generation Automation)
SeekedPlatforms / IPmSeekedPlatforms This interface is to access the sought platforms.
<<Collection>> ( ControlDesk Next Generation
Automation)
Related documentation
Topic Description
Automating Platform Management and Variable The main tasks of ControlDesks platform
Management on page 540 management are to add platforms and/or devices
to an experiment, to configure their
communication settings, and to add variable
descriptions to platforms/devices.
Platform Management Automation API Versions There are two platform management automation
on page 545 API versions in ControlDesk.
Reason The process of the dSPACE software has used more than 2 GB, or
allocated memory in an area above 2 GB. This leads to a problem
with certain Windows network functions, and might make the
dSPACE system inaccessible.
Problem An application for the DS2201 slave DSP is not started automatically.
Description The real-time application was built with RTLib of dSPACE Release 7.1
or earlier. As a result, an application for the DS2201 slave DSP cannot
be started automatically.
Solution Rebuild the real-time application for the modular system including the
DS2201 with RTLib of dSPACE Release 7.2 or later.
Automatic reconnect aborts When a platform/device that supports the automatic reconnect
when interrupted functionality is in the unplugged platform/device state, ControlDesk
periodically tries to reestablish the logical connection between the
ControlDesk PC and the platform/device hardware.
If the platform/device hardware is plugged and unplugged again
while ControlDesk is trying to reestablish the logical connection
(starting from when ControlDesk checks whether a new detected
platform/device is the unplugged one and whether online calibration
or measurement has to be resumed), the automatic reconnect process
is canceled and the platform/device is set to the disconnected state.
ControlDesk does not start a new automatic reconnect process.
Information in this topic Warning when accessing dSPACE hardware by several dSPACE products
on page 559
Limitations for managing the firmware of dSPACE systems on page 559
Limited number of host services on page 559
Access to mask parameters and workspace parameters on page 559
Limitation for rebuild detection on page 560
DS1103, DS1104: Downloading a slave DSP application on page 560
DS1007: Loading an application to the flash memory on page 560
DS230x limitations on page 560
Multiprocessor System platform: automation via MCD 3 on page 561
VEOS platform: limitations on page 561
XIL API MAPort platform limitations on page 561
Limited number of host The number of host services in an application running on dSPACE
services real-time hardware is limited to 32.
Access to mask parameters ControlDesk 3.x versions up to and including ControlDesk 3.7.1
and workspace parameters supported mask parameters and workspace parameters in dSPACE
real-time applications via RTIs Include mask and workspace
parameters TRC file option. ControlDesk Next Generation does not
support mask parameters and workspace parameters in this way.
Tip
The access is the same for all dSPACE tools and requires no
MATLAB installation during real-time simulation since it is
calculated directly in the real-time application.
DS1103, DS1104: You cannot download a slave DSP application directly to a DS1103 or
Downloading a slave DSP DS1104. Instead, you have to download the main application
application containing the slave DSP application to the DS1103 or DS1104. For
details, refer to Basics on Handling Simulation Applications
on page 116.
DS1007: Loading an You cannot load an application to the flash memory of a DS1007 if
application to the flash the DS1007 is part of a multiprocessor system.
memory
Multiprocessor System When you perform automation via ControlDesk's MCD 3-compatible
platform: automation via interface, you have access to the individual boards belonging to a
MCD 3 Multiprocessor System platform.
However, you do not have access to the Multiprocessor System
platform itself.
VEOS platform: limitations n Only one VEOS platform in an experiment can be assigned to
VEOS at a time.
n When an operating system process related to VEOS, e.g.,
VEOSDaqManager.exe, is stopped, the connection between the
offline simulation application and the related VEOS platform in
ControlDesk is interrupted. Reconnecting to the VEOS Simulator,
e.g., by refreshing the interface connection or reregistering the
VEOS platform, will fail.
To reconnect to the VEOS core, you have to stop the
VEOSKernel.exe manually.
XIL API MAPort platform Unsupported data types The following XIL API data types are not
limitations supported by the XIL API MAPort platform:
n Curve
n Map
n String vector
n String matrix
n Write-only vector
n Write-only matrix
No measurement support for measurement arrays and value
blocks Due to a limitation of the XIL API standard, you cannot
measure measurement arrays and value blocks by using the XIL API
MAPort platform.
Tip
Measuring the individual elements of measurement arrays and
value blocks with ControlDesk is possible in connection with the
dSPACE XIL API implementation delivered with
dSPACE Release 2015A, and in connection with other XIL API
implementations that offer features exceeding the standard
XIL API functionality.
Note
Do not download these default values to the XIL API MAPort
platform hardware when you start online calibration.
Variable types and their limits Due to a limitation of the XIL API
standard:
n The data type of variables available in ControlDesk's Variable
Browser is Int64, UInt64, or Double data type, independent of the
variable's data type in the realtime application.
n The variable limits available in ControlDesk's Variable Browser are
the limits of the Int64, UInt64, or Double data type, independent
of the variable's limits in the realtime application.
Memory consumption in long-term measurements Due to a
limitation of the XIL API standard, the available memory might not be
sufficient in long-term measurements.
Tip
This limitation does not apply in connection with the dSPACE
XIL API implementation delivered with dSPACE Release 2015A.
XCP and CCP limitations XCP: No support for ADDRESS_MAPPING The ADDRESS_MAPPING
keyword is not supported for XCP devices (XCP on CAN and XCP on
Ethernet). This keyword is used to map the addresses of the
parameters in the ECU flash memory to the corresponding addresses
in the ECU RAM.
XCP: No consistency check for MAX_CTO/ MAX_DTO For XCP
devices (XCP on CAN and XCP on Ethernet), ControlDesk does not
check whether the MAX_CTO value you specify during device
configuration is equal to the value internally used by the ECU. You
must ensure consistency yourself. The same applies to the MAX_DTO
value.
For details on the MAX_CTO and MAX_DTO settings, refer to XCP/GSI2
Settings Advanced Properties on page 353 dialog.
XCP on CAN and CCP: Downloading invalid data to the ECU if
"Confirm Automatic Page Switch" is enabled The following
limitation applies to XCP on CAN devices and CCP devices if the
following conditions are met:
n The related ECU has two memory pages.
n The related ECU has memory segments.
n You did not specify an ECU Image file during the configuration of
the XCP on CAN or CCP device.
n You enabled the "Confirm Automatic Page Switch" option for
that device. This lets ControlDesk perform the page switch
necessary to start online calibration with a prompt for
confirmation.
If you select "Upload WP upload RP" the first time online calibration
is started and if you then do not confirm the subsequent page switch,
ControlDesk creates only one data set for both memory pages.
Depending on the page currently active on the ECU, a working or a
reference data set is created.
If you select "Download WP download RP" the next time online
calibration is started, invalid data is downloaded to the ECU memory
page that was inactive during the first online transition.
Limitations for devices that ECUs with one readonly memory page: no offline calibration
access specific ECUs in some cases Suppose you have an ECU with one readonly
memory page and without an initial data set. If you select "Upload
connected variables" in the Calibration Memory Dialog the first time
you start online calibration, parameter values are displayed as
readonly in calibration instruments even if online calibration mode is
stopped.
To perform offline calibration, you have to select "Upload" in the
Calibration Memory Dialog when you start online calibration. This
allows ControlDesk to upload the parameter values from the
hardware to the host PC and create an initial data set.
For details, refer to Basics on Starting Online Calibration
( ControlDesk Next Generation Calibration and Data Set
Management).
ECUs with one readwrite memory page: no download of
connected variables in some cases Suppose you have an ECU
with one readwrite memory page and without an ECU Image file,
and you select "Upload connected variables" in the Calibration
Memory Dialog the first time you start online calibration.
When you start online calibration again ControlDesk does not let you
download the values of connected variables. You can select only
"Upload" or "Upload connected variables".
For details, refer to Basics on Starting Online Calibration
( ControlDesk Next Generation Calibration and Data Set
Management).
Limitation for devices using Problems with automatic reconnect Problems with the automatic
PCbased CAN interfaces reconnect functionality can occur if you are using a Kvaser CAN
interface simultaneously with a DCI-CAN1, DCICAN2, or a
Calibration Hub and you disconnect the Kvaser CAN interface from
Video Capturing device IDS cameras: Supported driver software version The driver
limitations software version for cameras from IDS (http://www.ids-imaging.com/)
must be lower than 4.50.
Pretriggered recording only in the "integrated" capture mode
The following limitation applies only when you use the Video
Capturing device in the separate capture mode:
When you specify a negative trigger delay (pretrigger) for triggered
recording, data recording for a Video Capturing device does not start
until the trigger condition is met. Data of the pretrigger time is not
recorded.
To perform pretriggered recording, you can use the integrated
capture mode instead.
Low frame rates only in the "integrated" capture mode The
following limitation applies only when you use the Video Capturing
device in the separate capture mode:
When you specify a frame rate that is below the minimum frame rate
supported by the camera hardware, this does not reduce the rate of
frames actually used.
To work with low frame rates, you can use the integrated capture
mode instead.
ControlDesk Glossary
image from a data set. The updated application image then contains
a real-time application with an additional set of parameter values.
Artificial Horizon An instrument displaying the rotation on both
the lateral and the longitudinal axis to indicate the angle of pitch and
roll of a simulated aircraft. The Artificial Horizon has a pitch scale and
a roll scale.
Automatic Reconnect Feature for automatically reconnecting to
platform/device hardware, for example, when the ignition is turned
off and on, or when the physical connection between the
ControlDesk PC and the ECU is temporarily interrupted.
If the feature is enabled for a platform/device and if the
platform/device is in the 'unplugged' ( Unplugged on page 605)
state, ControlDesk tries to reestablish the logical connection to the
platform/device hardware. After the logical connection is
reestablished, the platform/device has the same state as before the
unplugged state was detected. A measurement started before the
unplugged state was detected is resumed.
Automation A communication mechanism that can be used by
various programming languages. A client can use it to control a server
by calling methods and properties of the server's automation
interface.
Automation script A script that uses automation to control an
automation server.
Axis point object Common axis on page 573
Tip
If communication is established via XCP on Ethernet, the
CalDemo ECU can also run on a PC different from the PC on
which ControlDesk Next Generation is running.
L Label list A list of user-defined variables that can be used for taking
snapshots, etc.
Layout A window with instruments connected to variables of one
or more simulation models ( Instrument on page 585).
Layout Navigator A controlbar ( Controlbar on page 574) that
displays all opened layouts ( Layout on page 587). It can be used
for switching between layouts.
Leading raster The measurement raster ( Measurement raster
on page 589) that specifies the trigger ( Trigger on page 605)
settings for the Plotter ( Plotter on page 596) display. The leading
raster determines the time range that is visible in the Plotter if a start
and stop trigger is used for displaying the signals.
LIN Bus Monitoring device A device that monitors the data stream
on a LIN bus connected to the ControlDesk PC.
The LIN Bus Monitoring device works, for example, with PC-based LIN
interfaces.
The device supports the following variable description file types:
n LDF
n FIBEX
n AUTOSAR system description
Load type The load type specifies the option to disturb a signal with
or without load rejection.
Local Program Data folder A standard folder for application-
specific configuration data that is used by the current, non-roaming
user.
%USERPROFILE%\AppData\Local\dSPACE\<InstallationGUID>\
<ProductName>
Log Viewer A controlbar ( Controlbar on page 574) displaying a
history of all error and warning messages that occur during work with
ControlDesk.
Logical link A representation of an ECU specified in the diagnostics
database. A logical link contains information on the ECU itself, and all
the information required for accessing it, such as the diagnostic
protocol ( Diagnostic protocol on page 577) used for
communication between the ECU and ControlDesk. Each logical link
is represented by a unique short name in the ODX database ( ODX
database on page 593).
Look-up table A look-up table maps one or two input values to
one output value.
Generic term for curves and maps.
n A 1dimensional array containing the axis points for the yaxis. This
array can also be specified by a reference to a common axis (
Common axis on page 573).
n A 2dimensional array containing data points. The map assigns
one data point of the array to each pair of xaxis and yaxis points
Maps are represented by the symbol.
Map file A file that contains symbols (symbolic names) and their
physical addresses. It is generated during a build process of an ECU
application.
MCD3 Automation Module An optional software module for
ControlDesk Next Generation that enables users to automate
ControlDesk Next Generation according to the ASAM MCD3
standard.
Measurement Viewing and analyzing the time traces of variables
( Variable on page 606), for example, to observe the effects of
ECU parameter changes.
ControlDesk provides various instruments ( Instrument
on page 585) for measuring variables.
Measurement (variable type) A scalar variable that can be
measured, including individual elements of a measurement array.
Measurement variables are represented by the symbol.
Measurement array A 1, 2, or 3dimensional array of
measurement variables. In variable lists, ControlDesk displays entries
for the measurement array itself and for each array element.
Measurement arrays are represented by the symbol.
Measurement Configuration A controlbar ( Controlbar
on page 574) that allows you to configure measurement and
recording.
Measurement data API Application programming interface (API)
for accessing measurement data (stand alone: access is possible
without ControlDesk).
Measurement Data Pool A controlbar ( Controlbar on page 574)
that provides access to measurement data recorded in measurement
data files.
Measurement raster Specification of how often a value of a
variable ( Variable on page 606) is updated during a
measurement ( Measurement on page 589). A measurement raster
is derived from a measurement service ( Measurement service
on page 590).
Note
Some platforms/devices provide only a working page. You
cannot switch to a reference page in this case.
Only the pin failures of one failure pattern can be activated at the
same time for any specific failure simulation system ( Failure
simulation system on page 583).
Pitch variable A variable connected to the pitch scale of an
Artificial Horizon ( Artificial Horizon on page 568).
Platform A software component representing a simulator where a
simulation application is computed in real-time (on dSPACE real-time
hardware) or in non-real-time (on VEOS). ControlDesk provides the
following platforms:
n DS1005 PPC Board platform on page 578
n DS1006 Processor Board platform on page 579
n DS1007 PPC Processor Board platform on page 579
n DS1103 PPC Controller Board platform on page 579
n DS1104 R&D Controller Board platform on page 579
n DS1202 MicroLabBox platform on page 579
n MicroAutoBox platform on page 591
n Multiprocessor System platform on page 592
n SCALEXIO platform on page 600
n VEOS platform on page 608
n XIL API MAPort platform on page 610
Each platform usually has a variable description ( Variable
description on page 607) that specifies its variables.
The platforms in ControlDesk can be experiment-specific or project-
global. A project-global platform can be reused in multiple
experiments of a project and has an identical configuration in all of
them.
Platform trigger A trigger ( Trigger on page 605) that is
available for a platform ( Platform on page 596) and that is
evaluated on the related dSPACE real-time hardware or VEOS.
Platform/Device Manager A software component represented by
a controlbar ( Controlbar on page 574). It provides functions to
handle devices, platforms, and the applications assigned to the
platforms.
Plotter An instrument for displaying and postprocessing both
analog and binary variable values.
S Sandbox The folder where your project files are stored locally when
you work with a database ( Database on page 575).
SCALEXIO Multicore Module An optional software module for
ControlDesk Next Generation that provides access to real-time
applications that are computed on multiple cores of a single-
processor SCALEXIO system.
Using the SCALEXIO Multicore Module requires that you also have a
valid license for the SCALEXIO Platform Module.
SCALEXIO Multiprocessor Module An optional software module
for ControlDesk Next Generation that provides access to real-time
applications that are computed on multiple cores of a multiprocessor
SCALEXIO system.
Using the SCALEXIO Multiprocessor Module requires that you also
have a valid license for the SCALEXIO Platform Module.
n DS1104
n DS1202 MicroLabBox
n MicroAutoBox
No platform module is required to access VEOS.
Start trigger A trigger ( Trigger on page 605) that is used, for
example, to start a measurement raster ( Measurement raster
on page 589). A platform trigger ( Platform trigger on page 596)
can be used as a start trigger.
Static Text An instrument for displaying explanations or inscriptions
on the layout.
Steering Controller An instrument for changing variable values
using a game controller device such as a joystick or a steering wheel.
Stimulation Writing signals to variables in real-time models during
a simulation run.
Stop trigger A trigger ( Trigger on page 605) that is used, for
example, to stop a measurement raster ( Measurement raster
on page 589).
String A text variable in ASCII format.
Strings are represented by the symbol.
Struct A variable with the struct data type. A struct contains a
structured list of variables that can have various data types. In
ControlDesk, a struct variable can contain either parameters and
value blocks or measurement variables and measurement arrays.
ControlDesk supports nested structs, i.e., structs that contain further
structs and struct arrays as elements.
Structs are represented by the symbol.
Struct array An array of homogeneous struct variables.
Struct arrays are represented by the symbol.
STZ file A ZIP file containing signal descriptions in the STI format.
The STZ file can also contain additional MAT files to describe
numerical signal data.
Sub data set A data set that does not contain the complete set of
the parameters of a platform/device.
Symbol A symbolic name of a physical address in a map file. A
symbol can be associated to a variable in the Variable Editor, for
example, to support an address updates.
SYNECT server Server that provides the database ( Database
on page 575) that you can connect to.
Tip
A device for which the connection between ControlDesk and
the device hardware currently is interrupted is also set to the
"unplugged" state when you start online calibration if both
the following conditions are fulfilled:
n The device's Start unplugged property is enabled.
n The Start online calibration behavior property is set to
"Ignore differences".
This is possible for CCP and XCP devices. For details on the
two properties listed above, refer to General Settings
Properties on page 313.
W Working data set The data set currently residing in the memory of
a platform/device hardware or VPU. There can be only one working
data set for each calibration platform/device. The working data set is
read/write.
Working page Memory area containing the parameters of an ECU,
VPU, or prototyping hardware ( Memory page on page 590). The
working page contains the read/write working data set ( Data set
on page 575).
Workspace A set of projects in the database ( Database
on page 575).
Writable measurement A scalar variable that can be measured
and calibrated.
C D H
Calibration Memory dialog 398 DBC file handling platforms 58
Camera Selection page 448 CAN signal formats 143 handling real-time applications
CAN Bus Monitoring device 159, 231 DCIGSI1 device 172, 234 via command line 132
CAN signal formats 143 DCIGSI2 device 174 HCN boot firmware 73
Intel 143 default factory firmware 80 HCN firmware 73
CAN Slave firmware 73 device handling 137 Host IF firmware 73
CAN Type 1 firmware 73 Device Properties dialog Host IF PLD firmware 73
CAN-based devices Calibration Memory page 489
CAN interface 44 devices I
virtual devices 45 specifics 137
CCP device 168, 233 I/O clock buffer configuration 73
DIO Type 3 PLD firmware 73 I/O CPLD firmware 73
Clear Flash dialog 403 DIO Type 4 PLD firmware 73
cmdloader 132 I/O FPGA firmware 73
Documents folder 15, 578 Instrument Selector 587
CN boot firmware 73 DocumentsFolder 15, 578
CN CPU configuration 73 Intel format 143
DS1005 PPC Board platform 238 Intel Sequential 144
CN firmware 73 DS1005FwArchive 76
command line tool Intel Standard 144
DS1006 Processor Board platform 240 IoFpga 73
cmdloader 132 DS1006FwArchive 76
Common Program Data folder 14, 573 DS1007 PPC Processor Board platform
CommonProgramDataFolder 14, 573 242 K
configuring DS1007 PPC Processor Board platforms
bus devices 158 KL15 handling 33
basics 85 K-Line interface 47
CCP devices 168 DS1007FwArchive 77
communication settings DS1103 PPC Controller Board platform
CAN Bus Monitoring device 159 245 L
CCP device 168 DS1103FwArchive 77 LIN Bus Monitoring device 164, 254
LIN Slave firmware 73 communication settings DCIGSI2 Select Logical Links page 379, 413,
LIN-based devices device 174 454
LIN interface 46 communication settings for ECU Select ODX Files page 373, 407, 461
loading an application from the flash Diagnostics device 184 Select Variable Description dialog 481
memory of a platform 130 communication settings XCP on Select Vehicle page 379, 413, 467
loading an application to the flash CAN device 211 starting the dSPACE ECU Flash
memory of a platform 127 communication settings XCP on Programming Tool 221
Local Program Data folder 15, 588 Ethernet device 215 VEOS platform 262
LocalProgramDataFolder 15, 588 communication settings XCP on XCP on CAN device 266
Log Viewer 588 FlexRay device 217 XCP on Ethernet device 268
configuring a CAN Bus Monitoring XCP on FlexRay device 271
M device 159 XIL API MAPort platform 273
configuring a CCP device 168 platform/device configuration
MABXFwArchive 77 configuring a FlexRay Bus Monitoring refreshing 42
Measurement Data Pool 589 device 162 platform/device management
measurement modules configuring a LIN Bus Monitoring Camera Selection page 448
XCP on Ethernet-based 215 device 164 General Configuration page 449
Member Configuration page 454 configuring an ECU Diagnostics device Member Configuration page 454
MicroAutoBox platform 255 184 Platform/Device Manager 494, 596
Motorola format 143 configuring an XCP on CAN device platforms
Motorola Backward 144 211 basics 59
Motorola Forward LSB 144 configuring an XCP on Ethernet platforms/devices
Motorola Forward MSB 144 device 215 bus devices 25
Motorola Sequential 144 configuring an XCP on FlexRay device CAN Bus Monitoring device 159
Multiprocessor System platform 258 217 CCP device 168
optional processors 98 consistency checks 138 connected state 28
Multiprocessor System platforms customizing calibration memory consistency checks 138
basics 96 segments 139 DCIGSI1 device 172
DCIGSI1 device 234 DCIGSI2 device 174
O DCI-GSI2 device 236 disconnected state 28
DS1005 PPC Board platform 238 ECU Diagnostics device 26
optional processors DS1006 Processor Board platform 240 EPK checks 138
Multiprocessor System platform 98 DS1007 PPC Processor Board platform experimentspecific platform/device
242 27
P DS1103 PPC Controller Board FlexRay Bus Monitoring device 162
platform 245 global platform/device 27
platform DS1104 R&D Controller Board LIN Bus Monitoring device 164
configuring 66 platform 246 measurement and calibration devices
platform handling 58 DS1202 MicroLabBox platform 248 26
platform management ECU Diagnostics device 251 measuring state 28
accessing ECUs 154 ECU Flash Programming dialog 477 offline state 28
Add Platform/Device to Experiment EPK checks 138 online state 28
dialog 480 flashing via diagnostic protocols 223 platforms 26, 59
adding platforms/devices to an FlexRay Bus Monitoring device 252 states of a platform/device 28
experiment 49 getting status information on ECU and status information on ECU and ECU
Advanced Settings page 443 ECU interface 177 interface 177
assigning a DCIGSI1 to a DCIGSI1 handling devices 137 system variables
device 172 handling platforms 58 data acquisition raster 177
assigning a DCIGSI2 to a DCIGSI2 LIN Bus Monitoring device 254 unplugged state 28
device 174 loading an application from the flash Video Capturing device 26
assigning dSPACE real-time hardware memory of a platform 130 XCP on CAN device 211
to a platform 66 loading an application to the flash XCP on Ethernet device 215
assigning VEOS to a platform 66 memory of a platform 127 XCP on FlexRay device 217
Assignment page 445 MicroAutoBox platform 255 programming the ECU flash memory via
batch operation 132 Multiprocessor System platform 258 diagnostic protocols 223
Calibration Memory dialog 398 programming the ECU flash memory programming the ECU flash memory via
CAN Bus Monitoring device 231 via diagnostic protocols 223 ECU interfaces 221
CCP device 233 programming the ECU flash memory project and experiment management
Clear Flash dialog 403 via ECU interfaces 221 Add platform/device dialog 480
cmdloader 132 refreshing platform/device Select ECU Image file 483
configuring configurations 42 Select Variable Description dialog 481
communication settings CCP device registering Project Manager 597
168 platform 60 Properties controlbar 597
communication settings DCIGSI1 SCALEXIO platform 260
device 172 Select ECU Image File dialog 483
S
SCALEXIO platform 260
SCALEXIO platforms
basics 104
SCALEXIOFwArchive 78
Select ECU Image file 483
Select ECU Image File dialog 483
Select Logical Links page 379, 413, 454
Select ODX Files page 373, 407, 461
Select Variable Description dialog 481
Select Vehicle page 379, 413, 467
simState variable 117
simulation applications
basics 116
simulation platform
switching 38
Slave DSP firmware 73
starting the dSPACE ECU Flash
Programming Tool 221
states of a platform/device 28
switching
simulation platform 38
System FPGA firmware 73
System PLD firmware 73
system variables
data acquisition raster 177
U
user firmware 79
UserFirmware 73
UserFpga 73
UserIplFirmware 73
V
Variable Browser 607
variable management
Select ECU Image File dialog 483
Select Variable Description dialog 481
VEOS platform 262
Video Capturing 26
Video Capturing device 265
X
XCP on CAN device 211, 266
XCP on Ethernet device 215, 268
XCP on Ethernet-based measurement
modules 215
XCP on FlexRay device 217, 271
XIL API MAPort platform 273